> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-api-and-mcp/api/credits.md). # Credits Each admitted request to an operation that publishes `x-credit-operation` reserves credits for that operation; the reservation is settled when the job completes and released when it fails, so a failed job is never billed. Balances, grants and the per-call ledger are in the console under **Billing** and **Developer → Logs**. Requests made with a test-mode key are the one exception: they reserve nothing, settle nothing and leave no line on the ledger — see **Test mode**. `GET /v1/pricing` returns the credits each use case is charged, read from the same price table every reservation is priced from: per request for a single or synchronous operation, and per item for a batch, which charges only the items that succeed. A repricing reaches reservations within about a minute and this list within about two. The operation itself is free and takes no credential — it publishes `x-credit-free: true` in place of `x-credit-operation`, reserves nothing and leaves no line on the ledger — and when the current table cannot be read it answers **503** with `Retry-After` rather than a partial list. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.delpha.io/delpha-api-and-mcp/api/credits.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.