# 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 into structured, machine-readable intent for AI agents

## Facts

- Endpoint: POST https://api.dappdojo.com/summary/%7Bnetwork%7D/%7Btx_hash%7D
- 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-20a00e34
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lHvk8BhEeOeDLkZX7XATM

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-20a00e34 -d '<json body>'
```

Example prompt: Can you decode transaction 0x4f3a2b1c... on Ethereum mainnet (chain ID 1) and tell me what intent or action it represents in structured form?

## When to prefer this

Use this endpoint when an AI agent needs to understand the semantic meaning or intent of a raw EVM transaction hash — especially when building DeFi analytics, transaction monitoring, wallet explainers, or any agent workflow that needs to reason about what an onchain action actually did rather than just raw hex data.

## Known failure modes

- Invalid or malformed tx_hash (not 0x-prefixed or wrong length) returns an error
- Unknown or unsupported chain ID returns an error
- Transaction not found on the specified network
- Network congestion or RPC unavailability causes timeout
- Payment of 0.001 USDC via x402 not provided returns 402 Payment Required

## How this service works

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

## Output

Returns a JSON object containing the transaction hash, a schema version string, and a structured 'data' object representing the machine-readable intent extracted from the raw transaction — including what the transaction did, which contracts or addresses were involved, and what actions were performed.

## 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-20a00e34/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)