CEDX Portal · Customer Service
A portal is a promise: the catalog is current, the keys are behaved, the docs match the software. Portal scores all three (abuse per key, lag per docs page, risk per consumer), so the promise has a dashboard.
The sharpest alert on the overview is four words long: “unused but privileged.” A key idle for thirty days that can still write orders is the kind of thing a portal exists to surface, and this one does, by name.
Runs on demo data. The demo workspace is a developer portal. The mechanics carry to any catalog you publish.
What it is
The catalog shows version, stage, endpoints, apps and requests per day next to the number nobody prints: docs lag in days. The Orders API runs v2.4 at 920K requests a day with 48 days of documentation debt, and a deprecated MFA API still takes 624K.
Every issued key carries environment, plan, RPM, app count, abuse score and last-used date. A live checkout key on the Enterprise plan tops the table at 91; seventy-three keys have been unused for thirty days and stay listed.
The docs screen treats staleness as a defect with a number: lag in days and a broken-example count per page. A canary-probe SDK note is 109 days behind; a legacy-mobile auth page is 120. The rewrite queue is simply everything at stale ≥95.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/portal.
01 Overview
Calls versus errors across the week, a health ring at 100% estimated availability, and alerts that arrive root-caused: a checkout key at abuse 91 with a geo spike and failed-auth burst; the Orders docs lagging v2.4 by 48 days; a partner key burning 86% of quota in a throttle storm.
02 APIs
Forty-eight published APIs sorted by traffic, each with version and stage. The deprecated MFA API at 624K requests a day is the row that argues for this column layout: sunsetting is a traffic decision, and the traffic is printed.
03 Docs
Two hundred twenty pages with API version, status, lag, broken examples and a stale score per row. The partner bulk-sync page disagrees with the changelog. The overview alert says so, with four broken examples attached.
04 Keys
Three hundred twenty issued keys, 225 active, sorted by abuse. The columns are the investigation: environment, plan, RPM ceiling, apps using it, and the last-used date that separates forgotten from hostile.
Who runs it
Roles, not references. We have no named customers yet, so nobody is quoted, credited or claimed as one, and this page ships without photography rather than with a synthetic frame.
Owns the 48-API catalog. The deprecated-but-busy rows, an MFA API at 624K requests a day, are their sunset plan.
deprecated · 624K req/dayWorks the docs rewrite queue: 102 pages at stale ≥95, 182 with broken examples, oldest lag 120 days.
stale ≥95 · 102Watches the 38 high-abuse keys and the 20 consumers leaning on their quota, before either becomes a pager.
abuse ≥55 · 38The 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
An API ships in the catalog with a version and stage: the Orders API is on v2.4, stable, production grade, at 920K requests a day.
Consumers register apps and draw keys with plans and RPM ceilings; 320 issued, 225 active, each one scored.
Abuse scoring flags the 38 keys behaving badly, geo spikes, failed-auth bursts and off-hours patterns, with the signal named per alert.
Docs staleness is measured in days per page, and the rewrite queue is the 102 pages at stale ≥95. Owned, like the catalog.
One record
A portal publishes what the rest of the estate builds and answers what it cannot. The screens share one workspace and one Ask AI button.
Two hundred twenty docs pages with staleness scored in days: the same discipline Knowledge Base applies to help articles, aimed at developers.
CEDX DeskA partner's throttle storm that becomes a support conversation lands in Desk's queue: scored, like the keys, before it is worked.
CEDX APIThe estate's own API surface. Portal is how a catalog like it gets published, keyed, documented and policed.
CEDX CopilotAsk AI (⌘J) sits on every Portal screen, versioned and traced by the Copilot console behind it.
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 catalog, your keys
Portal with the rest of it
Questions
Yes. Every screenshot is a capture of the running build, open at /app/portal. It runs on demo data. The workspace on the chrome is the demo tenant.
The signals are named in the alerts: geo spikes, failed-auth bursts, off-hours patterns, quota burn. The keys table shows the score next to environment, plan, RPM and last-used, so a reviewer sees behaviour and context together.
In days, per page, against the API version the page documents, with a broken-example count beside it. The Orders docs lag v2.4 by 48 days because the create-order page still documents the v2.1 request body; the alert says exactly that.
They stay visible with their traffic. The demo's deprecated MFA API still takes 624K requests a day, which is the argument for sunsetting being a traffic decision rather than a date decision.
No certification has been issued. What we can evidence about hosting, encryption and access is on the security page.
Live build, demo data, no card. Then ask how many of your keys are unused but privileged.