Reconcile service credits
Read the relevant scoped service-credit balance and ledger without conflating customer credits with network payouts.
What you get
A scoped balance/ledger explanation with currency, timestamps and settlement limits.
Read workflow is supported; only the selected product corridor is required, and permission remains account-specific.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | authenticated read |
| Workflow state | available |
| Credential corridors (see workflow) | orders, evaluations, training |
Ask your assistant
Example task
Show the credit balance and ledger for my training or dataset order.Install this skill
Use an existing compatible MCP connection or the customer CLI. Skills provide instructions; installing them does not configure credentials, grant permissions or enable execution.
Install reliquary-credits
reliqua skills install --skill reliquary-credits --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.5.0.
Install the customer CLI — Verified release downloads, commands and troubleshooting.
Connect MCP — Keep writes disabled for discovery and planning.
Authentication and exact scopes — Corridor names identify key configuration; the API checks its actual read and write scopes.
Follow the workflow
- Choose the corridor matching the user's product: generation_balance uses orders credentials, evaluation_balance uses evaluations credentials, and training_balance uses training credentials. Do not call all three by default or assume they represent separate wallets.
- Read balance and returned ledger entries without reserving credits. Preserve currency, units, timestamps, debits, refunds and pending/finalized states as returned.
- Explain the ledger alongside an order/task only when the user requested reconciliation. Dataset delivery, accepted work and customer service-credit entries do not establish finalized miner/network payment.
- Do not purchase credits, change billing configuration or expose credentials as part of this read.
Tools and API routes
Call reliquary_connection first and use only tools registered in that connection. Route templates need the owned resource identifiers described by the existing API reference.
| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_generation_balance |
| MCP | reliquary_evaluation_balance |
| MCP | reliquary_training_balance |
| HTTP | GET /api/v1/balance |
Availability and authorization
A successful read does not grant execution access or establish qualified capacity. Preserve source clocks, missing values, account ownership and the limits of the returned evidence.
Back to the skills catalog — Find another workflow or connect an interface.