Environments. Sandbox first, production when you're ready.
Two environments with the same API shape, different keys, separate data and explicit promotion. Pick a region at sign-up; data stays there unless you move it.
Two environments
Same surface area, different blast radius.
- Keys prefixed
flx_sk_sb_. - 100 free pages/month, seeded with sample documents and templates.
- Webhooks deliver from a sandbox source IP range; signatures use a sandbox secret.
- Data is purged 90 days after last activity.
- Keys prefixed
flx_sk_pr_. - Pay-per-page on your plan; cost caps enforced per tenant guard.
- Audit trail retained per your contract (default 7 years for regulated tiers).
- Tenant region pinned at sign-up; data stays there.
Endpoints
The SDKs honour COGNERIS_BASE_URL — set it once per environment, leave the rest of your code alone.
Regions & residency
Choose where your tenant lives — data, prompts and audit trail stay in that region.
Region is set at tenant creation. Moving regions is an offline operation — open a ticket with support@cogneris.ai.
Rate limits
All surfaces emit Retry-After on 429. Production limits are tunable on Enterprise plans.
Seed data
- Sample documents — 12 representative PDFs across invoices, contracts, KYC and claims; downloadable from the sandbox dashboard.
- Shipped templates — every tenant gets all 40+ templates pre-installed and updated on the standard release cadence.
- Demo webhook receiver — sandbox tenants can route deliveries to
https://app.cogneris.ai/sandbox/echoto see them rendered in the dashboard.
Promote to production
Sandbox and production are separate tenants — you don't "promote" data, you promote the configuration that produced it. The pattern that works:
- Pin everything — templates, validation rule sets, agent pipelines, model tiers — to specific versions in sandbox.
- Export the config bundle —
GET /v1/tenant/config?format=bundleemits a signed manifest of every versioned object. - Import in production —
POST /v1/tenant/configwith the bundle; objects are created at the same version pin. - Swap keys — point your client at
api.cogneris.aiwith aflx_sk_pr_key. The code stays the same.
Health & status
- Health endpoint —
GET /v1/healthreturns{ status, region, version }with no auth required. - Status page — status.cogneris.ai publishes incidents per region and per surface.
- SLA — production aims at 99.9% monthly uptime per region; see your contract for the live commitment.
Now ship something
Jump into the Document AI agents — Extraction is the most common starting point.