# Blockscout Address Metadata Submission

> Blockscout Address Metadata Submission 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-15).

Submit blockchain addresses to Blockscout's metadata extractors for enrichment and indexing across multichain data sources

## Facts

- Endpoint: POST https://api.blockscout.com/services/metadata/api/v1/addresses:submit?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-address-metadata-submission-9ed9bcd5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XWc3utVjaryD-Ci3W6zAf

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-address-metadata-submission-9ed9bcd5 -d '<json body>'
```

Example prompt: Submit the Ethereum address 0xAbC123... to Blockscout's metadata extractors so it gets indexed and enriched across their multichain explorer.

## When to prefer this

Choose this endpoint when you need to register, label, or enrich blockchain addresses in Blockscout's multichain index — particularly after deploying a new contract or onboarding addresses to make them discoverable in Blockscout's explorer. Prefer this over read/search endpoints when your goal is to write address metadata rather than query it.

## Known failure modes

- Missing or malformed required fields (type, method, bodyType, body) returns a 400 error
- Invalid address format in the body payload causes rejection
- Incorrect bodyType enum value (not json/form-data/text) results in a bad request
- Payment not included or insufficient USDC causes a 402 Payment Required response
- Rate limiting or quota exceeded returns 429
- Body does not conform to v1SubmitAddressesToExtractorsRequest schema causes validation failure

## 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

An HTTP JSON response confirming the address submission was received by Blockscout's metadata extractors. The response body structure is minimal (schema example is empty {}), likely returning a success status or submission ID indicating the addresses have been queued for enrichment and indexing.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "$ref": "#/definitions/v1SubmitAddressesToExtractorsRequest"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-address-metadata-submission-9ed9bcd5/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)