llms.txt
+29 −4
https://datoka-agent.bhazarstudio.workers.dev/llms.txt
− - POST /v1/operations/prepare_agent_event: free. Validate an agent execution declaration and compute its commitment. Does not create a receipt.− - POST /v1/operations/verify_agent_receipt: free. Verify the declaration against a trusted Datoka receipt. A valid signature does not independently prove the action occurred.− No account or API key is required for the three free tools. Call get_agent_public_keys with {} to test the connection.− Sending Accept: application/json alone returns 406; text/plain returns 415.+ - ARD discovery (v0.91 proposal): https://datoka-agent.bhazarstudio.workers.dev/.well-known/ard.json+ - Free common-proof verification page: https://datoka-agent.bhazarstudio.workers.dev/verify+ - POST /v1/operations/verify_proof_receipt: free. Free verification of a common Datoka proof against an independently obtained caller-supplied public trust registry and explicit issuer/scope/chain. Send only the proof, never raw documents. receiptVerified concerns signature, context and dates; status remains incomplete because the artifact is checked locally. No payment, factual accuracy or parent signatures are verified.+ - POST /v1/operations/prepare_agent_event: free. Free validation of a locally built execution declaration before issuance. Hash exact input and output bytes locally; supply identifiers and UTC timestamps with milliseconds. Returns the validated event, commitment and logical chain without creating or purchasing a receipt. Use issue_agent_receipt only if a portable signed declaration is needed.+ - POST /v1/operations/verify_agent_receipt: free. Free verification of an execution event and its unchanged receipt returned by issue_agent_receipt. Checks signature, scope and event commitment against this issuer. No wallet or new issuance required. Use verify_proof_receipt for the distinct common proof-envelope format. A valid signature does not independently prove execution; compare original bytes locally.+ ## MCP versions+ Supports MCP 2026-07-28 through the official SDK, including server/discover and per-request metadata. Legacy initialize clients remain supported. Use an official client to supply matching protocol headers and metadata; never mix the two envelopes.+ No account or API key is required for the four free tools in production. Call get_agent_public_keys with {} to test the connection.+ Connection check (free, no wallet): download https://datoka-agent.bhazarstudio.workers.dev/check-connection.mjs and run node check-connection.mjs with Node.js 24+.+ Accept: application/json alone is supported. Explicitly excluding JSON returns 406; Content-Type: text/plain returns 415. Public MCP needs no OAuth login; do not send unrelated credentials.+ ## Verify a common proof without uploading its document+ Open https://datoka-agent.bhazarstudio.workers.dev/verify and try the synthetic example. For your own proof, supply an independently obtained public trust registry and explicit issuer, scope and optional chain. The page sends only the proof and public trust policy; document hashing and comparison happen on your device.+ The free verify_proof_receipt operation is exposed in the same HTTP/MCP catalogue and A2A skills. Its input is {proof,trust,issuer,scope,chain?}. Unknown fields, raw artifacts and private keys are rejected. A valid report has receiptVerified=true and status=incomplete: the server has not received or verified the artifact. An invalid signature or expired proof has receiptVerified=false; HTTP 200 alone never means a valid proof.+ trustSource=caller_supplied means the report relies on your supplied keys; it is not an independent identity certification by Datoka. Sources, parent signatures, payment, authorization and anchoring are not verified by this operation.+ HTTP/MCP checks do not persist proof contents. A2A uses the existing private task storage model: its input and result are retained with the task. Never put raw prompts, outputs or secrets into a proof statement.+ ## Who this service is for+ Developers operating AI-agent workflows who need a verifiable receipt of a declared step or hand-off. Hash inputs and outputs locally, request a signed receipt, then keep it with your own audit record.+ You buy signature issuance and durable idempotent receipt recovery. You do not buy execution of your agent, factual validation, identity certification or blockchain anchoring. Evaluate the free preparation and verification steps before spending.+ ## Use your own workflow+ Three concrete uses and runnable commands: https://datoka-agent.bhazarstudio.workers.dev/use-cases.md.+ Download https://datoka-agent.bhazarstudio.workers.dev/workflow.mjs (Node 24+, no dependencies). Run:+ ```sh+ node workflow.mjs --input task.json --output result.pdf --metadata metadata.json --request receipt-request.json+ ```+ Metadata fields: agentId, runId, stepId, tool, outcome, startedAt, completedAt (UTC with milliseconds). The helper hashes exact file bytes locally and calls only free preparation. It never uploads documents or opens a wallet. It creates a new request file without overwriting an existing one. Keep source files unchanged while hashing; JSON whitespace affects byte hashes.+ Use neutral labels, never secrets. Preparation validates your declaration but does not independently observe execution or issue a receipt.+ Then run node example.mjs --request receipt-request.json for a free quote. Add --buy --approve-one-purchase only with the wallet and saved-state settings below. Retry with the same state; a different supplied request is refused. To resume without the request file, omit --request and reuse the original saved purchase state.+ ## Optional source attribution+ You may send X-Datoka-Source with smithery, glama, producthunt, mcpservers, mcpharbor, a2aregistry, x402scan, bazaar or 402ad. Only a fixed source label is counted; never put a person, token or customer ID in it. Public page links can use the same utm_source values. These are unverified aggregate hints, not unique visitors or proof of purchases.