# SignalHarness Base Receipt Analyzer

> SignalHarness Base Receipt Analyzer is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.015/call, status unknown (last checked 2026-09-13).

Analyzes a Base blockchain transaction receipt JSON to extract gas usage, fees, execution status, and network context for OP Stack chains

## Facts

- Endpoint: POST https://signalharness.ai/api/agent/services/base_receipt_analyze/invoke
- Price: $0.015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signalharness-base-receipt-analyzer-dc7f9be0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MfgWg1M4v_Rrd4uN11CWW

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 signalharness-base-receipt-analyzer-dc7f9be0 -d '<json body>'
```

Example prompt: Can you analyze this Base transaction receipt JSON for me and tell me if the transaction succeeded, how much gas was used, what the execution fees were, and flag any warnings about finality or authenticity?

## When to prefer this

Use this endpoint when you need to programmatically parse and understand a Base (Coinbase L2, OP Stack) transaction receipt — particularly for fee breakdown, gas accounting, and status verification. Prefer this over generic blockchain explorers when you need structured JSON output suitable for agent pipelines, or when working within an x402 pay-per-call workflow already settled on Base USDC. Not suitable for fetching receipts from the chain (you must supply the receipt) or for non-Base/non-OP-Stack chains.

## Known failure modes

- Malformed or invalid receipt JSON input results in a parse error
- Receipt data may not confirm finality — warnings are returned indicating authenticity is not verified
- Missing required fields in the receipt JSON may cause incomplete analysis
- Chain ID not matching accepted Base chains (8453 or 84532) may produce unexpected results
- Large receipt JSON exceeding 65536 characters will be rejected

## How this service works

Explore 330 pay-per-call x402 API services and 27 agent-native digital products, with Base USDC pricing, secure Polar checkout, and free discovery.

## Output

Returns a structured JSON analysis including: transaction hash, gas used, effective gas price, execution fee, L1 fee, log count, transaction success status (true/false), contract address (if applicable), network context (accepted chain IDs, fee model, protocol family), and an array of warnings about receipt authenticity or finality limitations. Also includes the evidence scope and analyzed network identifier.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request_json": {
   "type": "string",
   "maxLength": 65536,
   "minLength": 2
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "replay": false,
  "result": {
   "warnings": [
    "Receipt data does not establish safe or finalized status."
   ],
   "service_id": "base_receipt_analyze",
   "analysis_json": "{\"contract_address\":null,\"effective_gas_price\":\"105\",\"execution_fee\":\"2205000\",\"gas_used\":\"21000\",\"l1_fee\":\"0\",\"log_count\":1,\"network_context\":{\"accepted_chain_ids\":[\"8453\",\"84532\"],\"deposit_transaction_type\":\"0x7e\",\"fee_model\":\"L2 execution plus caller-supplied L1 data/operator components\",\"protocol_family\":\"OP Stack\"},\"status\":\"0x1\",\"successful\":true,\"total_supplied_fee\":\"2205000\",\"transaction_hash\":\"0x1111111111111111111111111111111111111111111111111111111111111111\",\"warnings\":[\"receipt authenticity and finality are not verified\"]}",
   "evidence_scope": "caller_supplied_data",
   "analyzed_network": "base"
  },
  "status": "succeeded",
  "receipt": {
   "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "usage": [],
   "status": "succeeded",
   "network": "eip155:8453",
   "artifacts": [],
   "endedAtMs": 0,
   "latencyMs": 0,
   "paymentId": "example-payment",
   "receiptId": "example-receipt",
   "requestId": "example-request",
   "serviceId": "base_receipt_analyze",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "15000",
   "resultSha256": "d8e53ede7358910ee22179f8f1cbacda5991aa2c634f132f01f76b72610c029f",
   "serviceVersion": "1.0.0",
   "settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
  },
  "artifacts": [],
  "requestId": "example-request",
  "executionId": "example-execution"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signalharness-base-receipt-analyzer-dc7f9be0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from signalharness.ai](https://www.zero.xyz/host/signalharness.ai/llms.txt)