Atlas Billing
Billing is staged, inspectable, and not yet production-proven
Atlas API exposes stable pricing semantics and billing diagnostics for agents and developers. Public charging claims stay staged until checkout, webhooks, ledger rollups, visible summaries, and Stripe invoice reconciliation are proven from a clean deploy.
Proven on staging
- Stable pricing payload at GET /atlas/v1/pricing
- Operation policies include free, staged, billable, and not-billable status
- Webhook registration is explicitly not billable
- Billing schema and developer usage reconciliation pass on staging
Staged
- Developer usage events and ledger rollups are available for diagnostics
- Billing headers expose remaining calls and budget state when enabled
- Stripe readiness checks fail deploys with invalid enabled billing config
- Stripe checkout and webhook harness is prepared but not yet live-proven
Not yet proven
- Normal GitHub Actions staging deploy from main
- Real staging Stripe test-mode checkout
- Signed Stripe webhook activation from a real checkout session
- Invoice reconciliation between raw usage, ledger, summary, and Stripe state
Price discovery
Agents should read GET /atlas/v1/pricing before committing spend. The response includes pricing_version, effective_from, numeric operation prices, and structured operation policies with claim status.
curl https://api.staging.usemirai.app/atlas/v1/pricingOperation policy summary
| Event type | Status | Meaning |
|---|---|---|
| atlas.webhook_registered | not_billable | Webhook setup should not create a customer charge. |
| atlas.mcp_call | staged_included | Discovery and control-plane calls are metered for diagnostics. |
| atlas.knowledge_fetched | staged_included | Evidence reads are metered but should not discourage safe inspection. |
| atlas.tool_message_sent | staged_billable | Outbox-safe accepted messages are candidate billable events. |
| atlas.action_executed | staged_billable | Committed tool-mediated writes are candidate billable events. |
| atlas.webhook_dispatched | staged_billable | Retry and dedupe policy must be proven before invoice claims. |
request ID
Tie the failed HTTP request to gateway and core-backend logs.
developer org ID
Identify the billing owner. Do not substitute a customer organization ID.
idempotency key
Confirm a replay used the same payload and did not create a duplicate charge.
usage event ID
Find the raw metered event behind a visible charge or budget warning.
ledger period
Compare raw usage for the month with atlas_api_spending_ledger totals.
checkout session ID
Trace upgrade attempts from Atlas to Stripe and back to audit rows.
Stripe event ID
Debug webhook delivery, signature verification, and activation state.
webhook delivery ID
Trace retries, exhausted deliveries, and replay safety.
Promotion rule
Treat billing as staged until the Stripe billing E2E passes with writes enabled from a clean staging deploy. A passing pricing endpoint or schema check is not enough to claim production billing.