# Blockscout Account Abstraction Indexing Status

> Blockscout Account Abstraction Indexing Status is a paid API for AI agents from api.blockscout.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-25).

Returns the indexing status of account abstraction (ERC-4337) data for a specified blockchain network on Blockscout

## Facts

- Endpoint: GET https://api.blockscout.com/%7Bchain_id%7D/api/v2/proxy/account-abstraction/status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-account-abstraction-indexing-status-32015c37
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qfEaQr2PcBWeiR8K6rFsV

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 blockscout-account-abstraction-indexing-status-32015c37
```

Example prompt: Check if Blockscout has finished indexing past account abstraction data on Ethereum mainnet — I want to know if historical UserOperation data is ready to query.

## When to prefer this

Use this endpoint when you need to verify whether Blockscout has completed indexing historical ERC-4337/account abstraction data for a specific blockchain before making downstream queries that depend on complete data. Prefer this over generic block indexing status endpoints when your use case specifically involves smart accounts, UserOperations, or ERC-4337 paymasters.

## Known failure modes

- Invalid or unsupported chain_id returns an error or empty response
- Chain not yet supported by Blockscout's account abstraction proxy returns 404
- Network timeouts if the Blockscout API is under load
- Missing chain_id path parameter causes a routing error

## How this service works

Explore crypto activities with Blockscout's multichain search. Find transactions, addresses, tokens, and dapps across top blockchain networks — your go-to explorer for cross-chain blockchain data

## Output

A JSON object indicating whether Blockscout has completed indexing past account abstraction (ERC-4337) data for the specified chain, with a boolean field 'finished_past_indexing' set to true when historical indexing is complete.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "properties": {
      "chain_id": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "finished_past_indexing": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-account-abstraction-indexing-status-32015c37/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockscout.com](https://www.zero.xyz/host/api.blockscout.com/llms.txt)