Confirm the account before enabling PAYG
Use the API key tied to the organization to read its current billing state and limits. The rate catalog is public and describes current rates rather than that account’s billing state:150 included calls and does not renew automatically. The response, not a copied example, shows the account’s current billing state and available context.
Enable the paid path
In the signed-in dashboard, choose Pay As You Go, save a card, make the initial credit top-up, and optionally configure auto top-up. The API endpoint for this control-plane action isPOST /v1/billing/payg/enable; it requires the authorized signed-in session rather than an API key.
Once payment is confirmed, the organization moves to payg_active. Until then, a billable request can return 402 billing_required with the account condition that needs attention.
Meter and monitor real usage
PAYG uses prepaid credits. Read billing rates for the current catalog, and retainSECAPI-Meter-Class and SECAPI-Estimated-Cost when a response supplies them. For a repeated path, use a billing quote before the loop; it estimates the current request but does not reserve credits.
Delivery work has its own meter families. Webhook and stream delivery use delivery_events; customer-configured monitor email recipients use email_notifications. If the account is budget-paused or lacks an active card or prepaid balance, paid delivery work is blocked rather than silently retried. Operational account emails do not use the monitor-email meter.

