# Onvexia Social Graph Endpoint

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

Retrieves the social graph connections and relationships for a specified blockchain user or address

## Facts

- Endpoint: GET https://onvexia.com/v1/social/graph/%7Buser_id%7D
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-social-graph-endpoint-d57de570
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kx0jLtPN859n9Qiv4ns5R

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-social-graph-endpoint-d57de570
```

Example prompt: Pull the social graph for user ID 0x1a2b3c4d from Onvexia so I can see which other wallets and addresses this account is connected to across chains.

## When to prefer this

Choose this endpoint when you need to explore or map the social and transactional relationships of a specific blockchain user or wallet address, particularly when you want multi-chain coverage and access to labelled address data. Prefer this over generic blockchain explorers when you need structured, analytics-grade social graph data fused with Onvexia's proprietary coverage of labelled addresses and historical supply data.

## Known failure modes

- Invalid or malformed user_id returns empty data array
- Unknown user_id with no graph data returns empty data array
- Missing user_id path parameter causes 400 or 404 error
- Payment not completed results in 402 Payment Required response
- Rate limiting or quota exceeded returns 429 error
- Service unavailability returns 503 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

Returns a JSON object with a data array containing the user's social graph nodes and edges (connections to other addresses/users), along with meta information including documentation and endpoint references. The data array may include linked addresses, relationship types, and network topology details.

## 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/social/graph/{user_id}"
  }
 }
}
```

## More

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