Enterprise Sales and HRS Setup
How enterprise and small-business teams request Human Reliability API access, what Galactus asks, and how billing and consent are reviewed.
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.
Application flow
The sales flow collects organization details, contact details, usage expectations, declared use case, and consent acknowledgement before protected enterprise access is reviewed.
Galactus leads the direct sales conversation after the account earns the active access window, but the enterprise request form and public docs stay available before that direct thread opens.
Billing and API setup
Approved enterprise accounts receive scoped keys, usage billing visibility, and a developer path for integration and audit review.
Usage billing is metered. The organization is charged for approved protected access volume, not for unrestricted seat counts.
Galactus sales eligibility
The same verified-completion rule that unlocks Galactus elsewhere also gates the direct sales conversation.
Public docs and the enterprise request form stay available before that direct AI sales thread opens, so evaluation and intake can still move forward cleanly.
What Galactus asks for
The application collects organization name, contact details, request band, use case, workflow impact, and whether consent-backed legal-name matching is required. That gives Galactus enough context to qualify the right billing lane and access scope.
Small businesses and enterprise teams follow the same application structure. The difference is the protected traffic level, review depth, and integration support needed after approval.