ORGN Gateway
ORGN Gateway is the confidential inference API and console — OpenAI-compatible routing to TEE models with attestation receipts or ZDR frontier models with policy zero retention.
ORGN Gateway is ORGN's OpenAI-compatible inference layer — one API and one console for confidential and frontier models.
Use it when you need programmatic LLM access with a clear choice: hardware-verifiable inference (TEE) or broad frontier access with contractual zero retention (ZDR).
New to Gateway? Start with the Quickstart — create an API key, send your first request, and inspect a TEE attestation receipt in Scanner.
What problem does Gateway solve?
Most AI gateways ask you to trust a vendor's policy. ORGN Gateway lets you choose your assurance level per model:
- TEE models (
near_*,phala_*) — prompts processed inside hardware-isolated Trust Domains. Requests produce attestation receipts you verify in ORGN Scanner, not trust statements. - ZDR models (
vercel_*) — frontier catalog via Vercel AI Gateway under zero data retention provider agreements. No hardware receipt; policy-enforced retention.
Gateway does not train on your data. It routes inference — you pick the model, you pick the tier.
What Gateway provides
One API, many providers
OpenAI-compatible `https://api.gateway.orgn.com/v1` — explicit model selection across NEAR, Phala, and Vercel-backed catalogs.
TEE or ZDR per request
TEE: hardware isolation + Scanner receipts. ZDR: policy retention + largest model catalog. Same API key, same wire format.
Verifiable when you need proof
TEE requests include cryptographic attestation metadata. Verify independently against Intel and NVIDIA public PKI — no trust in ORGN required.
Drop-in OpenAI compatibility
Swap base URL and API key — existing SDKs and tools work with minimal changes.
| Surface | URL | Auth |
|---|---|---|
| Gateway API | https://api.gateway.orgn.com/v1 | Bearer sk-ollm-* API key |
| Gateway console | gateway.orgn.com | id-orgn SSO |
| Scanner | scanner.orgn.com | Verify TEE receipts |
API keys use the sk-ollm- prefix — a legacy credential format from the OLLM v2 codebase. The product is ORGN Gateway; the prefix is technical, not the product name.
TEE vs ZDR at a glance
| TEE | ZDR | |
|---|---|---|
| Model IDs | near_*, phala_* | vercel_* |
| Guarantee | Hardware isolation in a Trust Domain | Contractual zero retention |
| Proof | Attestation receipt in Scanner | Policy + provider agreements |
| Best for | Regulated workloads, procurement proof | Frontier models, multimodal, embeddings |
See Models overview for selection guidance and Platform trust for the full stack context.
Where Gateway fits in ORGN
CDE / Studio → Origin Agent & project inference → ORGN Gateway → TEE or ZDR providers
↓
ORGN Scanner (verify TEE receipts)- CDE — Origin Agent routes inference through Gateway from the desktop IDE.
- Studio — Project model settings pick default TEE vs ZDR tiers.
- Scanner — Audit explorer for request metadata and attestation verification.
Documentation
Quickstart
API key, first chat completion, Scanner verification.
Authentication
API keys vs console SSO — separate credentials.
Models
TEE vs ZDR catalog and modality pages.
Security
Threat boundaries and data handling by execution type.
Console
API keys, playground, model list, team settings.
Integrations
OpenAI SDK, Vercel AI SDK, HTTP.
API reference
OpenAPI specification for `/v1` endpoints.
Related
- Choose your path — Integrator — persona routing
- Gateway architecture — control plane, execution environments, attestation flow