Platform · Developer Center
Build on the platform — with honest docs.
Developer Center is the platform’s programmable edge: API catalog, auth model, webhooks, and test environments, documented with the same candor as everything else — including where the answer is “not yet.”
Executive overview
The developer surface follows the same availability labels as the product catalog: what is live is marked live, and what is design-stage says so. The public API is design-stage today — the documentation describes the shape it is taking, not endpoints you can already call.
The design commitment is that the API inherits the platform rather than bypassing it: keys issued per organization, calls running under the same permission checks as any signed-in actor, and every effect landing in the same audit log. There will be no unauthenticated side door.
Core capabilities
API catalog
The full surface under design, documented endpoint family by endpoint family.
Auth model
Keys tied to your organization and permission-checked calls — the identity layer, extended to code.
Webhooks
Event delivery for the states the platform already tracks: licenses, deployments, inquiries.
Test environments
The same test environments Deployment Center sets up, used from code.
Changelog & compatibility
Version compatibility stated plainly, updated as the surface moves.
This page is deliberately a framing page, not the documentation. The real developer docs — API catalog, SDKs, auth, webhooks, changelog — live in the Developer section and carry their own honesty markers page by page.
Why enterprises care
No integration surprises
Candid docs let your engineers plan against what exists, not against a roadmap dressed as a reference.
Security review, pre-answered
Organization keys and the permission model are documented before the first endpoint ships.
Compatibility in writing
What works with what is a published page, not tribal knowledge in a support thread.
How it governs the workforce
Programmatic actors are actors. Anything built against the platform authenticates as someone, acts under granted permissions, and writes audit events — the same employment terms the AI workforce works under, extended to your code.
- Design-stage API
- Organization keys by design
- Docs-first
Everything on this page defers to the documentation for specifics. If this page and the docs ever disagree, the docs win.
Go to the developer docs →Across the ecosystem
See it govern real work.
A demo walks the module on live platform data — no slide deck.