CEDX 2026 Developer Release: Typed REST/GraphQL APIs, serverless functions, low-code builder, and isolated sandboxes Explore the CEDX API architecture ->
CEDXSystems
EnglishTalk to sales
DEVELOPER & LOW-CODE CEDX API
Overview Keys Routes Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
DEVELOPER & LOW-CODE CEDX API · Developer & low-code · api.cedxsystems.com

Routes, keys and quotas: each with a blast radius.

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.

Open live CEDX API -> Inspect 4-screen build tour
31.3M requests per day 16.3% error sample 82 active keys Zero-ETL Shared Postgres Record
CEDX API Enterprise Architecture Briefing
CEDX API · 31.3M requests per day

"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production dat..."

David Okafor · VP of Enterprise Systems · Harbor Holdings · 0.01s Canonical Sync
CEDX API reads and writes the exact same canonical Postgres record as CEDX Functions, CEDX Integrations, and CEDX Agents with zero third-party webhooks.
🔒 https://api.cedxsystems.com/workspace/live
CEDX API · Overview (The surface area, scored)
api.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/api ↗
REQUESTS PER DAY
31.3M
96 routes published
ERROR SAMPLE
16.3%
52 of 320 sampled log lines
ACTIVE KEYS
82
of 120 issued
CONSUMERS AT QUOTA RISK
12
≥80% of plan burned
Endpoint / Function / App Bound Estate Resource Owner & Deployment Env Request Rate & Latency Blast Radius & Quota Build Status
POST /v2/quotes/approve-rampCEDX API · Record #1040 Quotes + Books + Sign Transaction Core Commerce SDK · Prod 1,420 req/m · 14ms p99 ● Scoped Token · Tier-1 Passing 100%
fn_custom_rebate_accrual.tsCEDX API · Record #1041 Serverless Edge Function · Node 22 Finance Eng · Sandbox->Prod 840 exec/m · 9ms cold ● Read/Write: Books Subledger Deterministic
Internal Field RMA Builder AppCEDX API · Record #1042 CEDX Builder Low-Code Surface Ops Systems Team · 68 Users Zero Maintenance Debt ● Inherits Corporate SSO Live v2.4
CI/CD Canary Pipeline #8841CEDX API · Record #1043 Automated Flake-Scored Test Suite Release Engineering 412 Specs · 0 Flakes ● Auto-Rollback Armed Deployed 4m ago
✦ CEDX API Copilot · POST /v2/quotes/approve-ramp
Overview Verified
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.
CEDX API operator workspace in natural daylight
FIELD DOCUMENTARY · DEVELOPER & LOW-CODE

What breaks if this key rotates?

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.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/API
CORE CAPABILITIES · CEDX API

Three architectural jobs CEDX API gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · DEVELOPER & LOW-CODE FOUNDATION

What breaks if this key rotates?

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.

✓ High blast (≥55): 29 keys, flagged as rotation riskVerified
✓ Plans on every key: Internal, Sandbox, Growth, EnterpriseVerified
✓ Last-used dates, so unused keys cannot hideVerified
02 · LIVE EXECUTION

Which route is hot, and who is calling it?

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.

Which route is hot, and who is calling it?
CEDX API Live Telemetry ● 31.3M requests per day
03 · DETERMINISTIC GOVERNANCE

Which function is hurting?

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.

✓ Runtimes on every row: node, python, go, edgeActive
✓ 47 of 72 healthy; the rest erroring or degradedActive
✓ Cold-heavy chip isolates 37 functions at ≥5%Active
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX API build looks like when you open /app/api.

Every figure below is directly inspectable in the running CEDX API application workspace with zero synthetic projections.

REQUESTS PER DAY
31.3M
96 routes published
ERROR SAMPLE
16.3%
52 of 320 sampled log lines
ACTIVE KEYS
82
of 120 issued
CONSUMERS AT QUOTA RISK
12
≥80% of plan burned
4-SCREEN RUNNING BUILD TOUR

Four screens captured from api.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX API moves from initial intake to verified cross-estate completion.

01 OVERVIEW
The surface area, scored
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
A registry, not a drawer of secrets
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
Traffic, latency and error per path
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
The compute behind the routes
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.
01 OVERVIEW · API.CEDXSYSTEMS.COM

The surface area, scored

● Live Screen Capture

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.

✓ SLO 100% estimated availability against a 99.9% targetVerified in /app/api
✓ Assistant callers = 11.3% of sampled traffic, on screenVerified in /app/api
✓ Root-caused alerts from rotation lag to throttle stormsVerified in /app/api
The surface area, scored
OPERATING CADENCE · DEVELOPER & LOW-CODE

How CEDX API runs across the week, in the exact order work happens.

Every custom app in Builder, every Function, and every webhook runs inside the same identity, audit log, and transactional boundary as native CEDX apps.

STAGE 01

Capture & Ingest

Records land in CEDX API already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX API

Three roles open CEDX API every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

API platform owners using CEDX API

API platform owners

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
Key and quota stewards using CEDX API

Key and quota stewards

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
Consumer teams using CEDX API

Consumer teams

Build against sandbox and staging routes with their own keys, and see their own agent share before production does.

● 11.3% assistant callers
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Extend the 132-App Estate With Typed Code, Serverless Functions, and Zero Glue

CEDX API is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /functions/ ->

CEDX Functions

Routes resolve to the fn-* functions in the runtime, the same functions whose cold starts are priced by the day.
CONNECTED MODULE 02 Open /integrations/ ->

CEDX Integrations

Inbound connectors resolve to keys and routes here, which is why a throttle storm names both the consumer and the path.
CONNECTED MODULE 03 Open /agents/ ->

CEDX Agents

The Agent surface tab exists because 11.3% of sampled traffic is already assistant callers, governed like any other consumer.
CONNECTED MODULE 04 Open /sandbox/ ->

CEDX Sandbox

Sandbox-stage routes and keys let a consumer prove an integration before a production key is ever issued.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX API.

"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."

David Okafor
David Okafor
VP of Enterprise Systems · Harbor Holdings

"Having identity, least-privilege access, audit trails, and business applications on one kernel cut our security review and provisioning time by 82%."

Sarah Lindqvist
Sarah Lindqvist
Chief Information Security Officer · Atlas Corp

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."

Arjun Patel
Arjun Patel
SVP of Global Operations · Keystone Logistics
LIVE TCO & CONSOLIDATION MODEL · DEVELOPER & LOW-CODE

Stop paying five vendors to re-sync the same developer & low-code record.

Drag the seat slider to compare your current stitched stack (Retool Enterprise + Kong API Gateway + AWS Lambda + Postman + LaunchDarkly) against running CEDX API natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
Retool Enterprise + Kong API Gateway + AWS Lambda + Postman + LaunchDarkly
$1,380,000 / yr
CEDX API + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX API

Questions operators and architecture teams ask before piloting CEDX API.

01 Is the software on this page real? +
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.
02 What is a blast radius? +
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.
03 How do agents call the API? +
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.
04 What happens at the quota line? +
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.
05 Is the API audited or certified? +
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 SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX API is running right now. Open it and inspect the record.

Explore the live CEDX API workspace on canonical demo data at /app/api, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX API (/app/api) -> Book an estate architecture map