Datoka API
Signed commitments to caller-declared HTTP exchanges; no independent observation of the origin or response.
Keep a signed record of a declared HTTP exchange
Developers who need to retain integrity evidence about an API exchange.
- Hash the exchange locally according to the documented format.
- Prepare the request and review the price before authorizing payment.
- Retrieve and verify the receipt using the original operation identifier.
Datoka API does not independently observe the origin server and is not a universal API gateway.
Setup, price and recovery →Read the API contract ↗Listing completeness · 100/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 15/15 · Present
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 5/5 · Present
Evaluated 2026-11-22 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
MCP endpoint
https://datoka-api.bhazarstudio.workers.dev/mcp
Add this address to a client supporting the provider’s MCP transport. This is not a webpage.
Categories and declared capabilities
prepare_api_exchangeissue_api_receiptverify_api_receiptEvidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.