# minia2a x402 Transaction Decoder

> minia2a x402 Transaction Decoder is a paid API for AI agents from minia2a.uk, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Decodes and parses x402 payment protocol transaction data, returning structured information about transaction type, method, and parameters.

## Facts

- Endpoint: GET https://minia2a.uk/x402/tx-decode
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/minia2a-x402-transaction-decoder-12128c77
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IBVNv7_6KGxZQ1E3x-Pqy

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 minia2a-x402-transaction-decoder-12128c77
```

Example prompt: Can you decode this x402 transaction for me? It's a GET request with a JSON body type and I want to understand what the transaction type and method fields resolve to.

## When to prefer this

Use this endpoint when you need to inspect, debug, or audit x402 payment protocol transactions — especially when integrating x402 into agents or HTTP payment flows and needing to understand the decoded structure of a transaction. Prefer this over manual parsing when working with x402-specific field semantics.

## Known failure modes

- Missing required 'input' field returns a validation error
- Invalid or malformed transaction type string may return an unparseable result
- Unsupported x402 transaction formats may return null or partial output
- Network timeout or service unavailability returns HTTP 402 or 5xx error

## How this service works

minia2a service: x402-tx-decode

## Output

Returns a structured object containing the decoded x402 transaction details, including the resolved transaction type, method, body type, and any parsed query parameters, making the raw x402 protocol data human- and machine-readable.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "method": {
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/minia2a-x402-transaction-decoder-12128c77/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minia2a.uk](https://www.zero.xyz/host/minia2a.uk/llms.txt)