# Onvexia Social Coverage Endpoint

> Onvexia Social Coverage 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).

Retrieves social media coverage data for blockchain assets, surfacing community sentiment, mentions, and social signals from Onvexia's analytics database.

## Facts

- Endpoint: GET https://onvexia.com/v1/coverage/social
- 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-social-coverage-endpoint-c5fb8fe2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rTw4VsV18-pGNYRz9Kt7_

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-coverage-endpoint-c5fb8fe2
```

Example prompt: Pull the social coverage data for Ethereum from Onvexia — I want to see how many documents have been analyzed and what the social signals look like across all tracked chains.

## When to prefer this

Choose this endpoint when you need social media coverage and community signal data for blockchain assets specifically from Onvexia's curated analytics database, which spans ten chains and half a million analyzed documents. Prefer it over generic social scraping tools when you want pre-processed, labeled, and historically contextualized social data tied to on-chain asset identifiers. It is particularly useful when combining social signals with Onvexia's other analytics endpoints for a fused on-chain and off-chain view of an asset.

## Known failure modes

- Empty data array returned if no assets match the query properties filter
- Malformed properties parameter may return an error or empty result
- Rate limiting or payment failure if USDC micropayment is not properly included via x402 protocol
- Schema is underspecified so exact filter syntax may require consulting the OpenAPI docs at onvexia.com/openapi.json
- Service may return stale or cached results if social data ingestion is delayed

## 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 social coverage records for matched blockchain assets, and a meta object with documentation links and the endpoint path. The data array may include social signal counts, document analysis summaries, coverage metrics, and asset identifiers depending on query parameters.

## 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/coverage/social"
  }
 }
}
```

## More

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