# Utilia Solana Transaction Explainer

> Utilia Solana Transaction Explainer is a paid API for AI agents from api.utilia.ink, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-15).

Fetches and explains a confirmed Solana transaction by signature, returning balance deltas, program logs, compute unit usage, and a retry-safe error classification.

## Facts

- Endpoint: GET https://api.utilia.ink/base/v1/transaction/:signature
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/utilia-solana-transaction-explainer-930fa4fa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_47AHyVfKaZGbzF4QdZToK

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 utilia-solana-transaction-explainer-930fa4fa
```

Example prompt: Can you explain what happened in Solana transaction 5KtP...XYZ — specifically what balance changes occurred, what the program logs say, how much compute it used, and whether the error is safe to retry?

## When to prefer this

Use this endpoint when you need a human-readable or agent-readable breakdown of a specific confirmed Solana transaction — particularly when you need balance deltas, logs, and retry-safe error classification in one call rather than parsing raw RPC responses. Prefer this over raw Solana JSON-RPC getTransaction when you need structured error classification or summarized balance changes without manual parsing.

## Known failure modes

- Transaction signature not found or not yet confirmed — returns 404 or not-found error
- Invalid Base58 signature format — returns validation error
- Transaction is too old and no longer available from RPC history — returns not-found
- Network timeout or RPC node unavailability — returns 5xx error
- Signature belongs to a transaction that was not finalized — may return pending or null result

## How this service works

Explain a confirmed Solana transaction, including balance deltas, logs, compute usage, and a retry-safe error classification.

## Output

A structured explanation of the confirmed Solana transaction including: SOL and token balance deltas per account, program log output, compute units consumed, and a classified error code indicating whether the failure is safe to retry or not.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "signature"
     ],
     "properties": {
      "signature": {
       "type": "string",
       "description": "Base58 Solana transaction signature"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/utilia-solana-transaction-explainer-930fa4fa/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.utilia.ink](https://www.zero.xyz/host/api.utilia.ink/llms.txt)