Skavio Agent Tools: Read the OCR quote without mistaking it for a preview

[Skavio Agent Tools](https://getskavio.com/agent-tools/) provides company-scoped document processing with asynchronous jobs and a shared prepaid credit wallet. But an OCR quote needs careful interpretation: the reviewed documentation returns it alongside a submitted job, not through a verified quote-only preview. Before building a confirmation screen, establish whether the action behind it merely retrieves a price—or already reserves credits and queues processing.

1. Establish exactly what you want processed

Start with the document and the operation, rather than the price. The reviewed catalogue identifies document_ocr as OCR for scanned documents, billed per page. It distinguishes that operation from pdf_to_text, which extracts selectable PDF text. Choosing between them is a scope decision: reading an existing text layer is not the same task as recognizing text in a scan. For your own approval record, identify the source file, check its page count and specify the intended output using the currently documented options. These are recommended checks, not a claim that every item appears as a dedicated field in Skavio’s quote response.

• Confirm the document reference and version, so approval applies to the intended file.
• Check whether the request needs OCR or extraction of existing selectable text.
• Record the expected page count and requested output before authorizing submission.

2. Put submission approval before POST—not after its response

The documented POST /agent-tools/api/jobs response includes both a job state and a quote. Its example returns queued. The pricing documentation says quoted credits are reserved on submission, consumed on success and released on failure. Calling this endpoint just to discover the exact price must therefore not be presented as a harmless preview. The reviewed OpenAPI lists no separate quote or confirmation route. If your company requires approval of the exact server quote before any reservation or execution, pause the integration until a supported quote-only mechanism has been verified. The reviewed contract does not establish that workflow. The pricing page also advertises a request-level credit cap, but the reviewed contract does not specify its parameter or rejection behavior. Do not invent a cap field or assume that a confirmation screen enforces a server-side spending limit. A client-side estimate can inform a decision; it is not a substitute for a verified backend control.

3. Read the returned quote in its actual context

After an authorized submission, inspect the returned quote alongside the job state. The documentation’s illustrative quote includes credits, amount_micro_usd and price_usd. Its example values are not a verified price for your document, and this guide does not quote a numerical OCR rate. Compare the returned credit amount with the budget approved for that request. Keep the response associated with the original document and operation. This helps identify a discrepancy, but it is a post-submission check—not protection against the initial reservation. A changed file, page count, operation or requested output should trigger a fresh approval decision in your integration. Do not treat approval for one request as permission for a different workload.

• Read credits as the quoted processing-credit amount, not as proof that work has finished.
• Treat the monetary fields as quote information, not evidence of a new payment.
• Preserve the original response so later job and credit checks refer to the same request.

4. Follow the job through completion and credit settlement

A queued response does not establish that OCR output is ready. Track the job using the documented status mechanism before retrieving its result. Use the documented idempotency_key support for retry-safe submission. If a connection drops, retrieve status by that key rather than immediately submitting the work again with a new identity. Keep the company-scoped Bearer key server-side, including when handling authenticated result downloads. Reconcile the final outcome with the documented credit lifecycle: reservation on submission, consumption on success and release on permanent failure. Then check the downloaded OCR content against the source before relying on important names, dates or amounts. Successful processing and correct business data are separate checks.

Open Skavio Agent Tools and review the current API documentation →