Datoka API

dev.workers.bhazarstudio.datoka-apiPublished by datoka-api.bhazarstudio.workers.devOfficial publisherv0.3.12Updated Oct 24, 2026

Signed API declarations for agent handoffs. Free demo and verification; receipts cost 0.002 USDC.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Lets an assistant create, buy, and verify signed receipts for API exchanges that others can check independently.

What you can do
Provides four tools for signed commitments to API exchanges. prepare_api_exchange validates an event built locally with the SDK from real captured bytes and returns the commitment without issuing a receipt or charging; issue_api_receipt buys a portable signed receipt; verify_api_receipt checks signatures and declarations for free; get_api_public_keys returns issuer public keys for offline trust.
When to use it
Use when an assistant must hand an API response to another agent, archive decision inputs, or investigate changes later, and the recipient needs to verify integrity independently. A local log may suffice for private records.
Requirements
A remote HTTP endpoint; no package to install. Verification and public-key lookup are free and need no wallet. Issuing a receipt costs USDC, so a payable wallet and network access are required.
Before you install
Issuing a receipt spends 0.002 USDC per receipt, so confirm it is needed before paying. Events must be built with the SDK from real captured bytes; do not fabricate hashes. Establish issuer trust through the public-key tool before relying on verification.

Installation

In SourceWeft

  1. Open Datoka API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.bhazarstudio.datoka-api%2Fapi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "datoka-api": {
      "type": "http",
      "url": "https://datoka-api.bhazarstudio.workers.dev/mcp"
    }
  }
}

Tools

4

prepare_api_exchange

Prepare API Exchange

Free validation before buying a receipt. Supply an event built locally with the SDK from real captured bytes; never fabricate hashes. Returns the commitment without issuing a receipt or paying. Use when retaining verifiable evidence of an API response for a handoff or archive.

Parameterseventrequired

issue_api_receipt

Issue API Receipt

Buy a portable signed commitment to a declared API exchange when a recipient needs independently verifiable receipt integrity: response handoff, archived decision input, or change investigation. Costs 0.002 USDC per receipt via x402 when enabled; verification is free. A local log may suffice for disposable data. Requires caller-approved budget. Keep event, idempotency key and original payment unchanged on retry. Attests a client declaration, not provider origin, content truth or independent observation.

ParameterseventrequiredidempotencyKeyrequired

verify_api_receipt

Verify API Receipt

Free signature and declaration verification. To try before buying, read datoka-api://demo-receipt or /demo/receipt.json and pass the returned JSON here. No wallet needed for public verification. Verifies issuer, scope and event commitment; compare original response bytes locally with the SDK or /verify/.

Parameterseventrequiredreceiptrequired

get_api_public_keys

Get API Public Keys

Return issuer public keys. Establish issuer trust independently before offline verification.

Takes no parameters.

Version history

4
  1. v0.3.12LatestOct 4, 2026
  2. v0.3.10Oct 2, 2026
  3. v0.3.9Oct 1, 2026
  4. v0.3.0Sep 29, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.