Developer hostdevelopers.paytocommit.com Companion surfaceOpen platform workspace

Developers

PAYTOCOMMIT DEVELOPER PLATFORM

Quickstarts, HRS API reference, webhook verification, workspace setup, dashboard usage, exports, billing, and enterprise setup in one developer hub.

ReferenceHRS API + webhooks

Quickstarts, scopes, signatures, billing, and troubleshooting stay readable before sign-in.

WorkspaceAccount first

Create a developer account, then open the platform workspace.

OperationsAudit + reports

Reporting, webhook health, organization usage, and customer drill-downs live in the platform workspace.

AccountsWorkspace access

Developers sign in, create workspaces, request sandbox access, and manage production credentials from the same place.

Portal search64 pages

Quickstarts, reference, dashboards, pricing, and troubleshooting update live as you type.

HRS APIConsent scoped

Legal-name-backed reliability access stays purpose-bound, auditable, and filterable by active scope.

Usage billingMetered, exportable

Billing tracks protected lookups, report jobs, exports, and heavier dashboard workflows.

Platform workspaceDashboard + reports

Customer drill-down, webhook health, organization usage, exports, and audit views live in one place.

WorkspaceDeveloper accounts

OrganizationsRoles and billing access

Bring in technical leads, security owners, and finance contacts without collapsing everything into one credential.

ProjectsSandbox and production shape

Mirror the way real API teams work by isolating environments, integrations, and usage by project.

KeysCreate the first API key

Name, scope, and store the first key correctly so audit history and billing stay understandable later.

PlaygroundTest a live request

Run the first protected HRS call, inspect the payload, and confirm the key and consent scope are wired correctly.

QuickstartsSandbox to first lookup

Set up sandbox access, run the first protected lookup, verify webhooks, and move to production review.

SandboxRequest sandbox access

Get the first approved key, test subjects, and webhook access before you ask for production.

ProductionPrepare for go-live

Clear consent review, billing setup, webhook verification, and audit readiness before live traffic starts.

Core APIHuman Reliability API

Consent-scoped HRS retrieval, trend history, and enterprise-safe customer detail access.

DashboardMaster platform workspace

Portfolio health, webhook delivery, export jobs, billing, and customer-level reliability drill-downs.

WorkforceInvite employees and launch company onboarding

Send company-email invites, attach employees to the right organization, and turn on enterprise markets without adding signup friction.

InvitesRun employee invite waves

Move from one-off company-email invites to CSV-backed roster uploads without losing role, team, or onboarding state.

StatesHandle pending, blocked, and continuity access

Keep employee-side access states explainable while preserving the admin-side policy and continuity controls behind them.

OnboardingRoute employees into the right workspace

Show role, visibility policy, and first organization programs before the company-managed account goes live.

AccessReview the employee approval queue

Search pending signups, approve in batches, and apply temporary restrictions without orphaning active commitments.

PayrollRoll out wallet-linked direct deposit

Review payroll-connected funding, employee wallet entry, and employer reporting without confusing payroll with normal wallet ownership.

CustomersConsent-scoped customer drill-downs

Open the customer portfolio, inspect trend history, and work from a real organization dashboard.

ReportsExports, cohorts, and audit packages

Queue reports, run exports, and keep compliance-ready packages close to the dashboard.

WebhooksSignatures and retries

Signed delivery, replay protection, retry handling, and endpoint health verification.

BillingUsage-based pricing

Protected lookup volume, exports, reports, and threshold-driven billing visibility.

AuditAccess history and scope review

Trace consent-backed lookups, exports, scope changes, and high-sensitivity admin actions without leaving the platform.

PartnersStrategic partner packages

Optional flagship launch pages, case studies, and co-branded rollout support for negotiated enterprise accounts.

EnterpriseSales and approvals

Enterprise application review, consent expectations, use-case intake, and integration readiness.

Access detail

First Workspace Run

The first signed-in platform path from account creation through organization attachment and workspace ownership.

Start Here

Viewer roleTechnical owner

The first workspace run should make the operator role explicit from the moment the account attaches to the workspace.

Attach stateComplete

The detail page should show whether organization attachment is done before the user reaches projects or keys.

First-hour pathProject → key → lookup

The workspace onboarding path should stay visible while the user moves through setup.

First hourKeep the setup path moving

Open organization detailMove directly into the workspace the account is now attached to.Create the first projectOnce the workspace is attached, the clean next move is a sandbox project.Open the first quickstartThe first-run lane should connect directly into the first protected lookup guide.

Account firstThe platform should make it clear that a developer starts with a normal PayToCommit account, then attaches that account to a real organization workspace with explicit owners and operating lanes.

That mirrors the way serious developer platforms work: identity first, workspace second, protected usage only after the workspace is real.

Workspace attachThe first workspace run should show who is becoming the technical owner, who is expected to handle billing, and which use case is driving the initial project request.

This avoids the common problem where a team creates a workspace but no one can later explain who owns the integration.

First-hour next stepsOnce the account is attached, the next steps should be obvious: create the first sandbox project, issue the first key, run a protected lookup, and move into production review only when the basics are proven.

A strong first-run page should feel like an operator checklist, not a generic welcome screen.

jsonFirst workspace run payload

{
  "workspace_id": "ws_northstar_platform",
  "viewer_role": "technical_owner",
  "organization_attach_state": "complete",
  "next_steps": ["create_project", "issue_key", "run_first_lookup"]
}

The first workspace run should connect account identity, organization ownership, and the next operational steps in one place.

Workspace attach stateAccess

•Viewer role: Technical owner
The first workspace run should make the operator role explicit from the moment the account attaches.

•Attach state: Complete
The user should know whether organization attachment is already done before reaching projects or keys.

•Next sequence: Project → key → lookup
The onboarding detail should keep the first-hour path visible at all times.

Account first

The platform should make it clear that a developer starts with a normal PayToCommit account, then attaches that account to a real organization workspace with explicit owners and operating lanes.

That mirrors the way serious developer platforms work: identity first, workspace second, protected usage only after the workspace is real.

Workspace attach

The first workspace run should show who is becoming the technical owner, who is expected to handle billing, and which use case is driving the initial project request.

This avoids the common problem where a team creates a workspace but no one can later explain who owns the integration.

First-hour next steps

Once the account is attached, the next steps should be obvious: create the first sandbox project, issue the first key, run a protected lookup, and move into production review only when the basics are proven.

A strong first-run page should feel like an operator checklist, not a generic welcome screen.

Start HereDeveloper Accounts and Workspaces

How teams sign in, create a workspace, request sandbox access, and move toward production.

Start HereDeveloper Platform Overview

Build against the Human Reliability API, monitor usage, review consent scope, and move from sandbox to production from one platform workspace.

Start HereQuickstarts

Go from empty account to the first successful HRS lookup, webhook signature check, and dashboard review with minimal setup friction.

Start HereFirst Protected Lookup

The end-to-end quickstart for organization setup, sandbox key issuance, first lookup, webhook check, and dashboard confirmation.

Stand up the workspace.

Organizations Projects API keys Playground

Start with sandbox and setup.

Quickstarts Sandbox access Production review Reference

Operate the enterprise workspace.

Platform dashboard Usage billing Customer portfolio Reports and exports

Keep integrations healthy.

Webhook delivery Troubleshooting Audit logs Strategic partners

Galactus

Galactus for enterprise

Funding, verification, Chains, Spark, API access, and Commitment Network questions route through the published docs corpus.

Galactus unlocks after one verified completed commitment in the last 30 days. Create your account first, then finish one verified commitment to open Enterprise sales.