Enterprise Usage Billing and Request Bands
How protected API usage is billed, what request bands mean, and how organizations estimate cost before they go live.
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.
Request bands
The enterprise application asks for an expected request band so Galactus can qualify the right billing path and integration support level before protected access opens.
Request bands are meant for forecasting. Final billing follows actual protected usage, not a guessed seat count or a static annual package alone.
Metered usage
Usage billing follows the number of protected requests, the scope of those requests, and the audit coverage attached to them. Protected usage is tracked per key and per organization account.
That keeps the enterprise path fair for both high-volume organizations and smaller teams that still need the same consent-backed signal.
What is reviewed before approval
Before approval, Galactus reviews the declared use case, request band, legal-name matching requirement, workflow impact, and consent model so the right key scope and billing lane can be attached to the account.
This is meant to keep the Human Reliability API useful for real business decisions without drifting into an unscoped people-search product.
Enterprise and small-business fit
The same metered model works for larger enterprise teams and smaller businesses. Request bands are used to size onboarding and policy review, while final billing still follows actual protected traffic.
That keeps access fair for a smaller team that needs a precise consent-backed lookup without forcing it into an enterprise package built for a much larger volume profile.