# Datoka API Receipt Issuer

> Datoka API Receipt Issuer is a paid API for AI agents from datoka-api.bhazarstudio.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-12).

Issues a signed, client-declared HTTP exchange receipt for a single API operation, providing an auditable proof of the transaction.

## Facts

- Endpoint: POST https://datoka-api.bhazarstudio.workers.dev/v1/operations/issue_api_receipt?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datoka-api-receipt-issuer-60e7e6cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0ch4dcrbgVZ-xxNCASDBz

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability datoka-api-receipt-issuer-60e7e6cf -d '<json body>'
```

Example prompt: Issue a signed API receipt for the event I just triggered — use idempotency key 'evt-abc-123' and include the payment I made so I have an auditable record of this operation.

## When to prefer this

Use this endpoint when you need a cryptographically signed, auditable receipt for a single paid API operation — especially in x402-based payment flows where idempotency and replay safety are required. Prefer this over generic logging when you need a client-declared, tamper-evident proof of an HTTP exchange tied to a specific payment.

## Known failure modes

- Duplicate idempotency key with mismatched payload returns conflict error
- Missing or invalid payment token results in payment verification failure
- Malformed event data causes receipt generation to fail
- Network timeout on Cloudflare Worker edge returns 5xx error
- Invalid or expired x402 payment header causes rejection

## How this service works

Datoka API: a portable signed commitment to a client-declared API exchange for response handoffs, archived decision inputs and change investigations. 0.002 USDC per receipt; offline verification is free. Keep original bytes locally. Does not prove provider origin or content truth. Retry with the same event, idempotency key and original payment authorization.

## Output

A signed receipt object attesting to a single HTTP exchange operation, including the event reference, idempotency key, and payment proof. The receipt can be used as an auditable record confirming the API transaction occurred.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/datoka-api-receipt-issuer-60e7e6cf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from datoka-api.bhazarstudio.workers.dev](https://www.zero.xyz/host/datoka-api.bhazarstudio.workers.dev/llms.txt)