Documentation
Implemented control-plane boundary
This page separates the APIs that exist today from the planned product surface. The route list under What exists today is the authoritative contract; product and integration pages do not extend it.
Implemented today
Implemented means the API answers these routes. Whether a product is available in full or in part is shown on its page and on the status page.
Dashboard identity and workspaces
OIDC authorization code flow with PKCE, server-side sessions, workspace membership, invitations, role changes and recoverable account closure.
Projects and environments
Tenant-scoped projects and environments registered in one atomic request, each with its own setup draft and dashboard reads backed by the control-plane API.
Customer identity per environment
An isolated sign-in service per environment with hosted sign-up and sign-in, user administration from the console or a server API key (add, edit, disable, reset, sign out, delete), user events and social sign-in providers.
Stripe and Paddle connections
Customer-owned provider credentials verified before storage, kept in encrypted secret storage by reference, rotated through a ledger, plus signed provider webhooks.
Catalog, usage and entitlements
Versioned products, plans, prices, features, meters and provider price mappings plus idempotent usage events and a single entitlement decision path.
Hosted checkout, portal and cancellation
Checkout, portal and cancellation sessions created on the customer's own Paddle or Stripe account; the signed webhook stays authoritative for the subscription.
Audit ledger
A hash-chained, append-only workspace ledger with filtered reads in the console and a JSON export that reports chain verification per scope.
Agent connections
A five-minute, single-activation token that binds a CLI or agent to one project's development environment and reads its integration contract.
Not a current contract
Roadmap and external release gates
- Products marked as available in part have the working half listed on their integration page; the rest of each page is labelled as planned.
- There is no Paycux SDK in any language today; integration is plain HTTPS and JSON.
- Workspace invitations return the accept link once and, when the platform mail scope is configured, the same link is also e-mailed to the invitee; end-user organisation invites are returned to the inviting application, which delivers them. Email provider connections and Lemon Squeezy are not implemented contracts.
- There is no hosted verification runner; verification evidence comes only from the local runner.
- Production deployment and live provider journeys require separate release evidence.
Product integration pages
Each product has one integration page. The label comes from the same availability record as the product menu.
- User Management — available in part
- Enterprise SSO — available in part
- Abuse Checks — available today
- Sign-in UI — available today
- Directory Provisioning — available in part
- Role-Based Access Control — available today
- Agent Access — available in part
- Organization Setup — available in part
- Secret Storage — available today
- Multi-Factor Authentication — available today
- Audit Logs — available today
- App Connections — available in part
How to read this library
Treat a capability as available only when it also appears in the canonical API contract. Treat production availability as unmeasured unless the status surface identifies an exact deployed release and runtime proof.