TxReport — Complete API Response Schema Reference

Every successful call to POST /analyze returns a TxReport. This page describes the top-level shape of that object and links to the full documentation for each section. Each top-level key represents a distinct analytical lens — from raw chain identity through economic summary and structural proof.

Top-Level Shape

{
  "schema_version": 1,
  "chain": {},
  "tx": {},
  "execution": {},
  "classification": {},
  "economics": {},
  "inventory_deltas": [],
  "position_effects": [],
  "motifs": [],
  "attribution": {},
  "pipeline_stats": {}
}

Fields

number

required

TxReport schema version. Currently 1. This value is bumped on any breaking change to the top-level shape or the semantics of a sub-object. Check this field if you maintain a long-lived integration.

object

required

Chain information identifying which network the transaction belongs to.

Show chain fields

number

required

EIP-155 chain ID (e.g. 1 for Ethereum mainnet, 137 for Polygon).

string

required

Human-readable chain name (e.g. "ethereum", "polygon").

object

required

Transaction identity — the minimal set of fields needed to locate and display the transaction.

Show tx fields

string

required

The 0x-prefixed transaction hash as submitted.

number

required

Block number in which the transaction was included.

string

required

Address of the EOA that signed and submitted the transaction.

string | null

required

Recipient or contract address. null for contract-creation transactions.

string

required

Fully-formed Etherscan (or equivalent block explorer) URL for this transaction.

object

required

Execution outcome and gas consumption for the transaction.

Show execution fields

string

required

Human-readable outcome string (e.g. "Success", "Reverted").

boolean

required

true if the transaction reverted on-chain. When true, most economic fields will be zeroed or unavailable.

number

required

Actual gas units consumed by execution.

number

required

Base fee per gas unit (in wei) for the block containing this transaction, as defined by EIP-1559.

number

required

Miner/validator tip per gas unit (in wei) paid above the base fee.

string

required

Total gas cost expressed in the chain’s native token (e.g. ETH), formatted as a decimal string.

DisplayMoney

required

Gas cost expressed in USD as a DisplayMoney object — { text, available, reason? }. Always check available before rendering. See the economics page for the full DisplayMoney shape.

object

required

Intent classification headline: what the transaction did, how certain the engine is, and who the economic actor was. See the full classification reference.

object

required

Economic summary for the elected actor — inflows, outflows, net USD, gas fee, realized PnL, and pricing coverage. See the full economics reference.

array

required

Per-subject, per-asset balance changes. Every token movement recorded for every address involved in the transaction. See the full inventory_deltas reference.

array

required

DeFi position changes derived from the transaction — liquidity adds/removes, borrows, repayments, and similar protocol-level effects. See the full position_effects reference.

array

required

Structural motifs detected in the transaction, together with the supporting proof data. Motifs are reusable building blocks (e.g. a single on-chain swap) that compose into higher-level intents. See the full motifs reference.

object

required

Signer-to-actor attribution — explains the relationship between the address that signed the transaction and the address that is the economic beneficiary. See the full attribution reference.

object

required

Analysis pipeline counts and timing data intended for advanced integrators and debugging. See the full pipeline_stats reference.

Reading Order

TxReport is designed with a curated-summary-first philosophy: the most actionable fields appear at the top, and raw evidence lives deeper in the object. The recommended reading order is:

Step	Field	Question answered
1	`classification`	What happened? — intent kind, label, proof status, and confidence
2	`economics`	What was the money story? — net value change, token in/out, and fees for the actor
3	`inventory_deltas`	Which assets moved where? — drill-down evidence behind the economics summary
4	`motifs`	What structural patterns were matched? — on-chain building blocks with proof
5	`position_effects`	Which DeFi positions changed? — protocol-level position changes
6	`attribution`	Who signed vs. who economically acted? — relevant when a bot or aggregator executed on behalf of a user
7	`pipeline_stats`	Advanced / debug only — internal analysis counts and timing

Start with classification.intent_label and economics.net_usd_after_gas for a two-field summary suitable for any consumer UI. Reach into the lower sections only when your integration needs drill-down detail.

Section Reference

classification

Intent kind, label, proof status, confidence, actor, and matched rule.

economics

Inflows, outflows, net USD, gas fee, realized PnL, and valuation coverage.

inventory_deltas

Per-subject, per-asset token balance changes behind the economics summary.

position_effects

DeFi position changes — liquidity, borrows, repayments, and more.

motifs

Structural motifs and their supporting proof data.

attribution

Signer-to-actor relationship and delegation context.

pipeline_stats

Analysis pipeline counts and timing for advanced integrators.

​Top-Level Shape

​Fields

​Reading Order

​Section Reference

classification

economics

inventory_deltas

position_effects

motifs

attribution

pipeline_stats

Top-Level Shape

Fields

Reading Order

Section Reference