1. Connect your client
Add a remote MCP server in a client that supports Streamable HTTP. Use this exact endpoint:
https://datoqa.bhazarstudio.workers.dev/mcp
The endpoint is a protocol address, not a webpage. Opening it in a browser can return 405; connect through MCP instead. Let the client initialize, list the tools and read their schemas before calling them.
2. Complete the first operation
Ask your agent to call catalog, choose a supported source or operation, then call validate_table or a free data tool with the schema returned by tools/list.
Instructions you can give your agent
Use DatoQA to validate a small table. First read the tool schema. Do not authorize a payment. Explain the validation result and any rejected values.
3. Check the price before approval
Source data, table validation and currency batches: Free
Published sources and supported inputs; inspect freshness and gaps.
Country report: 0.002 USDC
One complete report, including its available exports.
Table reconciliation: 0.002 USDC
One complete result, JSON and CSV; free validation before payment.
Standard file conversion: 0.01 USDC
Supported tables, static images and standard PDF operations. One file per quote.
Document to PDF or OCR: 0.02 USDC
Supported Word/RTF/ODT documents or PDF/image OCR, 1–3 pages. Check the conversion guide for format limits.
4. Keep and verify your result
For a conversion, save the job identifier and recovery information before paying. Download the result within 24 hours. For reconciliation, save the preview ticket and retrieve the same paid result; JSON and CSV belong to the same purchase.
If something goes wrong
Missing, stale or incomplete source data must be resolved before a paid report. An ambiguous payment is recovered with the original operation and authorization; do not create another purchase.
For HTTP, use the status and structured error body. For MCP, inspect the tool result as well as the transport status. Do not retry a paid operation with a new identifier while the original payment is unresolved.