Developer Portal and Platform Workspace
How public developer docs, the signed-in platform workspace, projects, keys, customer drill-down, and reports fit together.
Each section is linked and available for Docs AI citations.
Keys stay tied to an app, a purpose, an approved consent scope, and a clear billing lane.
Galactus unlocks after one verified completed commitment in the last 30 days. Create your account first, then finish one verified commitment to open Docs AI.
Two connected surfaces
developers.paytocommit.com is the public developer hub. It covers quickstarts, reference, webhook guides, pricing, troubleshooting, sandbox access, production review, and strategic partner guidance before the team signs in.
platform.paytocommit.com is the signed-in operating workspace. That is where organizations, projects, API keys, customer drill-down, reports, exports, billing, and audit history live after the account opens a workspace.
What the workspace controls
The workspace keeps the real operating objects in one place: organizations, sandbox and production projects, named keys, webhook health, customer portfolios, reports, billing usage, and audit logs.
That split is deliberate. Public docs stay easy to evaluate, while the live operational surface stays tied to the right account, project, and access policy.
Where to start
Start in the developer hub if you are still evaluating the Human Reliability API, reading the quickstart, or checking consent and billing rules. Move into the platform workspace once your team is ready to create the first organization, sandbox project, and server-side key.
The sales and strategic partner path sits beside that normal rollout. Teams can choose the standard enterprise path or request a negotiated flagship package without changing the base developer workflow.