Skip to main content
Price the workflow you intend to run, not a generic query count. A filing monitor, a statement backfill, and a research agent can use different meter classes, units, retry patterns, and delivery paths.

​
Build a workload estimate

List each request path, expected units, and cadence. Include pagination, retry policy, issuer count, scheduled runs, and any webhook, stream, or monitor-email delivery. Then retrieve the current account context and quote each path with the credential that will run the work.
Repeat the quote for each route and unit-count combination in the planned loop. A quote reflects the current plan and budget gate; it is not a reservation or a guarantee for a later request.

​
Use the catalog to classify work

Use this table to plan what to quote, not to assign a price to a route. The current billing rates reference and the quote response determine the catalog amount and billing decision.

​
Keep an institutional record

For a decision to expand usage, save the catalog version, starterGrant, planKey, effectivePlanKey, billingState, recordedAt, quota snapshot, quoted meter class and family, units, amount, currency, budget-gate result, and request IDs. Record the assumptions behind the estimate so a reviewer can reproduce it.

​
Stop before the boundary

Do not treat a successful sample request as approval for a batch. A 402, quota response, or budget gate means narrow, fund, or reconfigure the workload before retrying. Redistribution, embedded output, white-labeling, resale, and Bulk Factor Export require commercial terms regardless of the estimate. For the full evaluation sequence, read pricing and limits. To enable metered internal usage, continue with Pay As You Go.