Reference Overview
EntryLayer reference docs are organized around the jobs an admin or build-seat user performs: creating projects, designing forms, managing access, configuring workflows, and inspecting app metadata.
Common admin jobs
Section titled “Common admin jobs”| Job | Start with | SQL API entry points |
|---|---|---|
| Discover the API | SQL Procedures | HELP(), HELP('CORTEX_CODE'), AGENT_MANIFEST() |
| Compose safe payloads | SQL API Contracts | HELP('CONTRACTS'), HELP('JSON_SCHEMAS') |
| Troubleshoot a failure | SQL API Errors & Troubleshooting | HELP('ERRORS'), HELP('TROUBLESHOOTING'), VALIDATE_SOURCE |
| Inspect app metadata | App Public Views | APP_PUBLIC.API_REFERENCE, APP_PUBLIC.PROJECTS, APP_PUBLIC.PROJECT_ACCESS |
| Manage access | Permission Model | LIST_ACCESS, UPSERT_ACCESS, UPDATE_ACCESS, DELETE_ACCESS |
| Design forms | Form Design Model | GET_PROJECT_DRAFT, CREATE_FIELD, SET_FIELD_VALIDATION, PUBLISH_PROJECT_DRAFT |
| Configure workflow | Workflow States | GET_WORKFLOW, UPDATE_WORKFLOW, LIST_WORKFLOW_TEMPLATES |
| Validate sources | Source Objects & Semantic Views | LIST_SOURCE_OBJECTS, DESCRIBE_SOURCE, VALIDATE_SOURCE |
| Review billing/ops | Billing & Operations | PREVIEW_BILLING, LIST_BILLING_LEDGER, SUSPEND_APP, RESUME_APP |
Human and Cortex paths
Section titled “Human and Cortex paths”Human admins usually start with the concept page that matches their task, then follow links into the SQL procedure catalog for exact calls.
Cortex and other SQL agents should use the SQL-discoverable docs first:
CALL ENTRYLAYER.API.HELP();CALL ENTRYLAYER.API.HELP('CONTRACTS');CALL ENTRYLAYER.API.HELP('SECURITY');CALL ENTRYLAYER.API.AGENT_MANIFEST();After every CALL, check status before reading data. On error, surface code and message instead of guessing.
Zero-access guardrails
Section titled “Zero-access guardrails”EntryLayer is designed to run inside the customer Snowflake account.
- Source discovery is metadata-only.
- SQL API source procedures do not sample source rows.
- SQL API docs do not introduce external access, provider-owned egress, or new Native App privileges.
- Cortex prompt examples must not include PII, secrets, source row values, or submission values.
- Submission mutation is only available where explicitly documented.