# Onvexia Constellation Graph

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

Retrieves a fused blockchain analytics reading for a crypto asset, combining labelled addresses, supply-age history, document analysis, and cross-chain data into a single structured response.

## Facts

- Endpoint: GET https://onvexia.com/v1/graph/constellation
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-constellation-graph-5da0af06
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YWGOgJ8fx6ug5Pon5izgW

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-constellation-graph-5da0af06
```

Example prompt: Pull the Onvexia constellation graph reading for Bitcoin — I want the fused analytics including labelled addresses, supply-age history, and cross-chain metrics.

## When to prefer this

Choose this endpoint when you need a single consolidated blockchain analytics reading that fuses on-chain data, labelled addresses, supply-age history, and document analysis across up to ten chains. It is especially valuable when you want historical depth back to 2008 and document-backed intelligence rather than raw on-chain data alone. Prefer it over single-chain block explorers or generic crypto data APIs when you need multi-chain fused intelligence in one call.

## Known failure modes

- Empty data array if the asset or properties filter matches nothing in the database
- 402 Payment Required if USDC micropayment is not attached or fails
- 400 Bad Request if the properties parameter is malformed
- Partial data if the asset has limited coverage across chains
- Timeout or slow response if querying broad property filters across many chains

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

Returns a JSON object with a data array containing the fused analytics reading for the queried asset, including labelled address data, supply-age history, cross-chain metrics, and document-backed signals. Also includes a meta object with documentation URL and 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/graph/constellation"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-constellation-graph-5da0af06/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)