# AWS Bedrock Agent API – Transaction Trace Agent

> AWS Bedrock Agent API – Transaction Trace Agent is a paid API for AI agents from aws-bedrock-agent-api.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-13).

Routes a natural language query to an Amazon Bedrock-powered AI agent that traces and explains blockchain transactions across Base, Ethereum, Tempo, or auto-detected chains.

## Facts

- Endpoint: POST https://aws-bedrock-agent-api.vercel.app/api/agents/tx-trace?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aws-bedrock-agent-api-transaction-trace-agent-6b6d89d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WPAfnUHQ8VjBcSejpusur

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 aws-bedrock-agent-api-transaction-trace-agent-6b6d89d9 -d '<json body>'
```

Example prompt: Can you trace this Base transaction and explain what happened — use the auto chain detection and tell me which contracts were involved and what token transfers took place?

## When to prefer this

Choose this endpoint when you need AI-powered natural language explanation of blockchain transaction traces on Base or Ethereum, especially when you want a conversational breakdown rather than raw RPC data. Ideal for agents that need to explain on-chain activity to non-technical users or investigate transaction outcomes without parsing raw blockchain data directly.

## Known failure modes

- Invalid or non-existent transaction hash returns an error or empty trace
- Unsupported chain causes routing failure
- Input text exceeding 50,000 characters is rejected
- Model override referencing a non-existent Azure deployment fails
- Payment failure via x402/MPP results in 402 response and no processing
- Network timeouts from Bedrock upstream may return 5xx errors

## How this service works

Pay-per-call Amazon Bedrock proxy on x402 and MPP.

## Output

An AI-generated natural language explanation of the traced blockchain transaction, including contract interactions, token transfers, addresses involved, and any errors or notable events detected on the specified chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "ethereum",
    "tempo",
    "auto"
   ],
   "type": "string",
   "description": "Chain hint for tx-trace"
  },
  "input": {
   "type": "string",
   "maxLength": 50000,
   "minLength": 1,
   "description": "Primary query or payload for the agent"
  },
  "model": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1,
   "description": "Azure deployment override"
  },
  "salary": {
   "type": "string",
   "maxLength": 80,
   "description": "Salary target or range, e.g. 120k or 80000-140000"
  },
  "context": {
   "type": "string",
   "maxLength": 50000,
   "description": "Optional extra notes"
  },
  "location": {
   "type": "string",
   "maxLength": 200,
   "description": "City, region, country, or remote"
  },
  "position": {
   "type": "string",
   "maxLength": 200,
   "description": "Job title or role"
  },
  "experience": {
   "type": "string",
   "maxLength": 80,
   "description": "Years or level, e.g. 5 years, staff"
  },
  "business_type": {
   "type": "string",
   "maxLength": 200,
   "description": "Industry or company type, e.g. fintech"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aws-bedrock-agent-api-transaction-trace-agent-6b6d89d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aws-bedrock-agent-api.vercel.app](https://www.zero.xyz/host/aws-bedrock-agent-api.vercel.app/llms.txt)