Read as Markdown · Use with an AI agent
Credits and account limits
Understand account allowances, connection caps and request receipts before budgeting a workflow. Current plan prices and endpoint quotes are published separately.
Account funds and monthly allowances
Subscriptions include a monthly credit allowance. Unused credits expire at the allowance reset, including on annual plans. Requests pause at the limit by default. Eligible paid accounts can enable optional overage with a monthly extra-spend cap; extra usage is billed monthly. There are no credit packs or rollover.
Billing’s calendar-month activity and your allowance reset period are different views. Check the displayed reset date and available balance rather than deriving spend from one balance subtraction. A concurrent job, refund or allowance reset can change that balance.
Three spending controls
| Control | Scope |
|---|---|
| Account allowance and optional overage cap | Shared funds and enabled extra usage across the account. |
| API key / MCP connection credit limit | Cumulative spending through that credential. Reaching the cap does not establish that the account has no funds. |
| MCP max_credits | Maximum reservation for one call_endpoint retrieval. Apply it again on each new page; it is not a task-wide budget. |
Use a dedicated capped key for a hard workflow ceiling. A local estimated budget is useful for planning but cannot coordinate other clients using the same account or prevent a stale price quote. Free balance and discovery calls remain available when funds are exhausted.
Read charges without guessing
| Outcome | Accounting rule |
|---|---|
| Successful fresh retrieval | Read actual credits_used; each continuation request has its own charge. |
| Eligible cache hit | Normally zero credits. Read the receipt; cache presence is not guaranteed. |
| Confirmed failed or empty normalized collection | Uncharged or refunded. A ledger can show the original debit and a matching refund. |
| credits_used: null / pending_reconciliation | Unresolved accounting. Stop dependent paid work and retain the original request context. |
| Stored idempotent replay | No new debit. The body repeats the original charge and historical balance, so account for the logical request once. |
| Batch | Read every item. The wrapper total can omit unresolved item amounts. |
Trace usage and refunds
curl 'https://www.monocrawl.com/v1/credits/balance' -H 'x-api-key: YOUR_API_KEY' curl 'https://www.monocrawl.com/v1/credits/transactions?limit=20' -H 'x-api-key: YOUR_API_KEY'
Use the returned cursor to continue the ledger and request_id to correlate entries when available. Keep reservation/debit and refund records together. The ledger and request receipt answer different questions: use the current balance endpoint for available funds, and usage history for individual requests.