CEDX API · Developer & low-code
The API console is where the estate's surface area is governed: 96 published routes, 120 issued keys, per-consumer quota risk, and a blast-radius score that says what breaks before you rotate, throttle or retire anything.
The sharpest alert on the overview is not an outage. It is a key: pk_live_harbor_checkout, 270 days old, 18 consumers still on single material. Rotation lag is an incident that has not happened yet — treated like one.
Runs on demo data — Northline Systems is the demo workspace, not a customer.
What it is
120 issued keys with environment, status, plan, requests per minute, dependents and blast score. pk_live_quartz_edge_18 serves 6,000 rpm with 19 dependents at blast 95; 30 keys have sat unused for 30 days and are still issued. Rotation risk is a sortable column, not a guess.
96 routes with method, path, stage, requests per day, p99, error %, agent share, blast and dependents. POST /v2/orders carries 1.12M requests a day at blast 91; a third of PATCH /v1/customers/{id} traffic is agents. Hot paths, deprecated paths and agent-heavy paths each get their own count.
72 deployed functions with runtime, region, invocations, cold %, p99, errors and status. fn-shipment-track runs 703K invocations with 1,690 errors; fn-payments-capture errors on the edge at a 0.2% cold rate. Route and function tell the same story from two sides.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/api.
01 — Overview
Requests at 31.3M a day, a 16.3% error sample, p99 at 412ms — and then the risk boards: 177 targets at high blast, 12 consumers past 80% of quota. Caller mix splits the sample into 210 human, 74 automation and 36 assistant callers, because the API's users are no longer all people.
02 — Keys
Every key with its plan, rpm budget, dependents and last use. The expiring chip catches pk_part_orbit_auth_32 before its Growth-plan consumers feel it; the rotated chip shows what good hygiene looks like.
03 — Routes
Routes publish per stage — prod, sandbox, staging — with requests per day, p99 and error rate. /v1/catalog/search runs a 706ms p99; /v1/customers errors at 3.2%. The method chips cut the table to exactly the verbs you are auditing.
04 — Functions
Each route resolves to the functions serving it, with invocations, cold %, p99 and errors per function. fn-orders-update is healthy at 34K invokes and 1,129 errors; fn-webhook-retry is erroring with 8. Both are one click from the route they back.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Own the route table: what publishes, what deprecates, and which of the 14 deprecated paths still has dependents worth migrating.
96 routes · 31.3M req/day
Rotate before the alert fires: 29 high-blast keys and 12 consumers at quota risk are this week's list, not next quarter's audit finding.
120 keys · 29 high blast
Build against sandbox and staging routes with their own keys, and see their own agent share before production does.
11.3% assistant callersThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
A route ships per stage — 96 published across prod, sandbox and staging — with traffic, p99 and error rate accruing from the first request.
Consumers get keys with plans and rpm budgets: 6,000 rpm on internal keys, 300 on a Growth partner key, every one with a blast score and a last-used date.
The overview tracks the error sample, p99 drift and quota burn — a partner sync at 6.4K 429s with 98% of quota burned is an alert with a name.
Deprecation is managed, not silent: 14 deprecated routes are still counted, and the legacy v1 mobile key sits unused for 30 days with 14 dependents still wired.
One record
This is not a gateway in front of somebody else's software. The routes, functions and events it governs are the estate's own.
Routes resolve to the fn-* functions in the runtime — the same functions whose cold starts are priced by the day.
CEDX IntegrationsInbound connectors resolve to keys and routes here, which is why a throttle storm names both the consumer and the path.
CEDX AgentsThe Agent surface tab exists because 11.3% of sampled traffic is already assistant callers — governed like any other consumer.
CEDX SandboxSandbox-stage routes and keys let a consumer prove an integration before a production key is ever issued.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your first consumers
API with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/api. It runs on demo data from the Northline Systems demo workspace.
An impact score per key, route and function — the count of dependents and traffic that would feel a change. 177 targets score ≥55 in the demo workspace, and the rotation-lag alert on the harbor checkout key is the blast score doing its job.
Through the same routes and keys as everyone else, and counted separately: the caller mix splits human, automation and assistant traffic, and each route carries an agent share — 33% on PATCH /v1/customers/{id} in the demo data.
You see it coming. Consumers past 80% of plan are listed — 12 today — and the throttle-storm alert names the consumer, the 429 count and the burn: 6.4K throttles at 98% of quota.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then look up the blast radius of the one key your estate could not survive losing.