Skavio Agent Tools: check your trial balance before a document job
A controlled first document test starts with the credits your company can actually use—not the allowance advertised on a signup page. In Skavio Agent Tools, check the authenticated workspace, inspect available credits and active reservations, and understand the selected operation’s billing unit before submitting work.
1. Confirm the company workspace and actual trial eligibility
Skavio Agent Tools provides company-scoped authenticated processing, self-service API keys and asynchronous jobs. Start by confirming that you are viewing the intended company workspace and using a key associated with it. Public pages advertise 1,000 trial credits for new company workspaces. That is an advertised allowance, not proof that your account has received it or still has that amount available. Actual eligibility must be checked by the backend; creating another API key should not be treated as creating another trial grant.
- Read the balance after signing in; an unauthenticated placeholder is not an account balance.
- Check current trial terms rather than assuming promotional credits renew, replenish or remain available indefinitely.
2. Separate available credits from reserved credits
The dashboard labels “Available credits” separately from “Reserved for active jobs” and provides Jobs and Ledger views. Inspect those values alongside the work already submitted rather than treating the advertised trial allowance as your current balance. Under the published reservation model, a submitted job reserves its quoted credits. Successful processing consumes that reservation; permanent job failure releases it back to the balance. A reservation is therefore not yet settled consumption, and releasing it is not a cash refund. For a hypothetical accounting example, assume you have 200 uncommitted credits before submitting a job quoted at 120 credits. If nothing else changes, reserving 120 leaves 80 uncommitted. Success consumes the reserved 120; permanent failure releases them. These numbers illustrate reservation accounting only—they are not a published document price or a verified dashboard response.
3. Check the operation’s unit—not a universal document count
A credit balance does not translate into a fixed number of documents. Agent Tools uses operation-specific billing: its public pricing distinguishes, for example, PDF-page units from per-document invoice extraction. Before choosing a test file, identify the exact operation and its applicable billing unit. Do not assume that different operations applied to the same document have the same cost. Use the current product interface and documentation to establish the relevant price rather than inferring it from another operation’s rate or the headline trial allowance.
- Choose one small fictional document with a known page count.
- Decide whether the test needs text recognition or structured invoice extraction before submitting it.
4. Do not use submission as a quote-only experiment
The submission boundary matters. Published documentation describes job submission as creating a queued job and returning a quote and job state. Do not assume that submitting merely requests an estimate, or that a separate confirmation step will follow. The published OpenAPI does not document a standalone quote route. Before submitting, establish how the current interface presents pricing and controls spending. If that boundary is unclear, pause rather than testing it with a large batch. For the first run, use only the small fictional document you have prepared.
5. Reconcile the first job before submitting another
Agent Tools jobs are asynchronous: a queued or processing job is not a completed result. Follow the job’s status, then inspect its reservation and the Ledger view before expanding the test. Do not treat a client timeout as proof that processing permanently failed or that a reservation has been released. The documentation identifies HTTP 402 as insufficient credits. If you receive it, stop and inspect available credits and active reservations. Repeated submissions under fresh request identifiers do not resolve a balance shortfall and can make it harder to understand which requests were accepted. Once a job succeeds, compare the output with the fictional source document. Credit settlement does not establish that every extracted value is correct.