Human Reliability API
Consent-scoped reliability access for protected integrations that need a user-authorized reliability signal.
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.
export async function getReliabilitySignal(consentToken: string) {
const response = await fetch("https://api.paytocommit.com/v1/reliability", {
method: "POST",
headers: {
Authorization: "Bearer <enterprise_api_key>",
"Content-Type": "application/json",
},
body: JSON.stringify({
consentToken,
scopes: ["hrs.current", "hrs.trend", "identity.match"],
}),
});
return response.json();
}Protected access requires a scoped enterprise key and an active user consent token. Identity-backed matching is available only when that scope is granted. The endpoint does not support open legal-name lookup.
Consent required
Every protected reliability lookup requires explicit user consent. PayToCommit does not allow open legal-name lookup, unrestricted public reliability search, or broad historical scraping of protected user records.
Consent is granted to a named integration, a declared purpose, and a defined scope. When identity scope is granted, the response can be tied to the consenting person's legal identity. Protected reliability access stays revocable and auditable.
Users stay in control of whether that protected record can be used to unlock outside opportunities. Granting consent makes the verified record usable for that approved purpose, but it does not inflate the score itself.
Response shape
The response returns a consent-scoped reliability signal, not a dump of a person's full platform history. The exact shape depends on the granted scope and the user's consent settings.
Approved scopes can return current HRS, recent trend direction, plateau or recovery markers, and identity-backed matching when the user explicitly granted that identity scope. Protected responses are designed to work as a reliability input for enterprise systems while preserving user control and auditability.
That lets approved teams review whether a consenting person has built a usable reliability record under their legal identity without turning the API into an unrestricted people-search surface.
Live history and trend review
Enterprise dashboards can review the live HRS curve instead of a flat snapshot. That includes rises, plateaus, recoveries, and the latest verified events that changed the protected record.
History visibility is still scope-bound. Integrations receive only the trend detail and event context covered by the granted consent.
Billing and audit
Enterprise usage is billed by protected request volume and audited access coverage. Each request is attributable to a key, a scope, a target account, and a timestamp.
Keys are scoped, auditable, and revocable. Protected use outside the granted scope should be treated as a policy violation.
Who uses it
The Human Reliability API is designed for banks, employers, underwriting teams, partner-review workflows, platforms, and smaller businesses that need the same consent-backed reliability signal for a real decision.
That is why the API supports both protected legal-name-backed review and lighter consent-scoped reliability access. Galactus qualifies the right path based on the use case, request band, and granted scopes.