# Onvexia Blockchain Address Labels

> Onvexia Blockchain Address Labels is a paid API for AI agents from onvexia.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-19).

Returns labels and identity metadata for a given blockchain address, drawing on Onvexia's curated database of labelled addresses across multiple chains.

## Facts

- Endpoint: GET https://onvexia.com/v1/labels/%7Baddress%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-blockchain-address-labels-72dcdacf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZNU-vuwlANiXO5ARL-JtW

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 onvexia-blockchain-address-labels-72dcdacf
```

Example prompt: Can you look up what entity or project is behind the blockchain address 0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE — I need to know if it's labelled as an exchange, protocol, or something else.

## When to prefer this

Choose this endpoint when you need to resolve a raw blockchain address to a human-readable label or known entity (exchange, protocol, contract, miner, etc.) and require coverage across multiple chains with data reaching back to 2008. Prefer it over generic block explorers when you need structured, machine-readable label data suitable for compliance, analytics pipelines, or agent workflows via REST, SQL, GraphQL, or MCP.

## Known failure modes

- Address not found in database — returns empty data array
- Malformed address format — returns 400 or empty result
- Payment not completed — returns 402 Payment Required
- Unsupported chain address format — no labels returned
- Rate limiting or authentication failure — returns 4xx error

## How this service works

Thousands of assets across ten chains, half a million analysed documents, labelled addresses and supply-age history reaching back to 2008 — fused into one reading per asset. REST, SQL, GraphQL and MCP.

## Output

A JSON response containing an array of label objects for the queried address, including entity name, classification type, and associated chain metadata, plus a meta object pointing to full API documentation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "meta": {
   "docs": "https://onvexia.com/openapi.json",
   "endpoint": "/v1/labels/{address}"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-blockchain-address-labels-72dcdacf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onvexia.com](https://www.zero.xyz/host/onvexia.com/llms.txt)