Gateway Console
Manage API keys, browse models, test inference in the Playground, and configure team access from the ORGN Gateway console at gateway.orgn.com.
The Gateway console at gateway.orgn.com is the web interface for managing ORGN Gateway. Use it to create API keys, explore the model catalog, test inference interactively, and administer team access and billing.
Sign in with id-orgn SSO only — there is no email/password login. See Authentication for credential details.
Console vs API vs Scanner
ORGN Gateway splits responsibilities across three surfaces:
| Surface | URL | Purpose |
|---|---|---|
| Console | gateway.orgn.com | Key management, model browsing, playground testing, team admin |
| API | api.gateway.orgn.com/v1 | Production inference — OpenAI-compatible endpoints |
| Scanner | scanner.orgn.com | Attestation verification for TEE requests |
Attestation verification lives in Scanner, not the Gateway console. The console helps you configure access and test models; Scanner lets you independently verify that TEE inference ran inside a genuine Trust Domain.
Console sections
API Keys
Create, name, and revoke sk-ollm-* API keys for programmatic access. Keys are shown once at creation — store them in a secrets manager immediately.
Model List
Browse the full model catalog with execution-type indicators. Models are grouped by provider and tagged as TEE (hardware-isolated, attested) or ZDR (zero data retention via Vercel). Model IDs use underscores throughout.
Playground
Send test inference requests directly from the browser. Select a model, compose a prompt, and inspect the response without writing integration code. Useful for evaluating models before wiring them into an application.
Team
Create teams, invite collaborators, assign roles (Owner, Admin, Member, Viewer), and manage per-team billing balances.
Sandboxes
Provision isolated execution environments for development and testing workflows tied to your Gateway account.
Typical workflow
- Sign in at gateway.orgn.com via id-orgn.
- Create an API key under API Keys. Copy the
sk-ollm-*value to your secrets manager. - Browse models in the Model List. Note whether each model is TEE or ZDR based on your compliance requirements.
- Test in the Playground before integrating a model into your application.
- Send production requests to
https://api.gateway.orgn.com/v1withAuthorization: Bearer sk-ollm-.... - Verify TEE requests in scanner.orgn.com to inspect attestation status and cryptographic proof.
TEE vs ZDR in the console
Not every model runs in a Trusted Execution Environment. The console surfaces execution type so you can make informed selections:
| Type | Indicator | Attestation | Best for |
|---|---|---|---|
| TEE | near_*, phala_* prefixes; TEE badge | Yes — verify in Scanner | Regulated workloads, audit requirements |
| ZDR | vercel_* prefix; ZDR badge | No — policy-enforced retention | Broad frontier catalog, multimodal models |
Both types enforce zero data retention. The difference is how privacy is guaranteed: hardware attestation for TEE, provider agreements for ZDR.
What's next
- API Keys — create and manage keys
- Playground — interactive model testing
- Gateway Quickstart — first API request end to end
- Model catalog — TEE vs ZDR selection guide
Gateway Attestation Data Reference
Technical reference for the cryptographic attestation receipt returned with TEE inference requests through ORGN Gateway. Intel TDX quotes, NVIDIA GPU evidence, message signatures, and external trust anchors.
API Keys
Create, manage, and rotate sk-ollm-* API keys in the Gateway console. Keys authenticate Bearer requests to api.gateway.orgn.com.