# Onvexia Asset Contracts Endpoint

> Onvexia Asset Contracts Endpoint 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 contract addresses and on-chain deployment data for a specified crypto asset across multiple blockchains

## Facts

- Endpoint: POST https://onvexia.com/v1/assets/%7Bid%7D/contracts
- 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-asset-contracts-endpoint-b0d4c122
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DmXpz4mK8VJja-5CMidAr

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-asset-contracts-endpoint-b0d4c122 -d '<json body>'
```

Example prompt: Can you pull up all the smart contract addresses for Chainlink (LINK) across every chain Onvexia covers — I need the labelled, verified ones so I can avoid fakes.

## When to prefer this

Choose this endpoint when you need authoritative, labelled smart contract addresses for a specific crypto asset across multiple blockchains and want data fused from on-chain sources plus Onvexia's own analytical coverage — particularly when you need to distinguish legitimate contracts from counterfeits or need historical deployment context going back to 2008.

## Known failure modes

- Asset ID not found returns empty data array
- Invalid asset ID format returns error
- POST body with malformed properties field may return 400
- Rate limiting or payment failure (x402) if USDC payment not attached
- Unsupported chain or asset outside Onvexia's ten-chain coverage returns no results

## 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 object with a `data` array containing contract records for the specified asset — including contract addresses, chain identifiers, labelling metadata, and deployment details — plus a `meta` object with documentation links and the endpoint path.

## 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/assets/{id}/contracts"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-asset-contracts-endpoint-b0d4c122/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)