# DappDojo Semantic Transaction Decoder

> DappDojo Semantic Transaction Decoder is a paid API for AI agents from api.dappdojo.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Decodes a raw EVM blockchain transaction hash into structured, machine-readable intent describing what the transaction actually did

## Facts

- Endpoint: POST https://api.dappdojo.com/summary
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dappdojo-semantic-transaction-decoder-efa5aded
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_G5Zo_ZW5W53DBtGCngsY5

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 dappdojo-semantic-transaction-decoder-efa5aded -d '<json body>'
```

Example prompt: Can you decode transaction 0x4a3b...c9f2 on Ethereum mainnet (chain ID 1) and tell me what it actually did — like what contract was called and what the intent was?

## When to prefer this

Use this endpoint when you have a raw EVM transaction hash and need to understand its semantic meaning — what action was performed, by whom, and on which protocol — rather than just raw calldata. Ideal for AI agents that need to reason about on-chain activity without manually decoding ABI calldata.

## Known failure modes

- Invalid or malformed tx_hash returns an error (not 0x-prefixed or not 32 bytes)
- Unknown or unsupported network/chain ID returns an error
- Transaction not yet confirmed or not found on the specified network
- Rate limiting or payment failure via x402 protocol
- Transaction from an obscure or unrecognized contract may produce incomplete decoding

## How this service works

Semantic Transaction Decoder that turns raw blockchain transactions into structured, machine-readable intent for AI agents using x402.

## Output

A structured JSON object containing the decoded transaction intent, the original tx_hash, and a schema_version field — representing the machine-readable breakdown of what the on-chain transaction accomplished (e.g. swap, transfer, mint, approval).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "network",
  "tx_hash"
 ],
 "properties": {
  "network": {
   "enum": [
    "1",
    "8453",
    "84532"
   ],
   "type": "string",
   "description": "Numeric EVM chain id."
  },
  "tx_hash": {
   "type": "string",
   "description": "0x-prefixed 32-byte transaction hash."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object"
  },
  "tx_hash": {
   "type": "string"
  },
  "schema_version": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dappdojo-semantic-transaction-decoder-efa5aded/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.dappdojo.com](https://www.zero.xyz/host/api.dappdojo.com/llms.txt)