# Onvexia Story Posts Retrieval

> Onvexia Story Posts Retrieval 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 the list of analytical posts (coverage documents) published under a specific story on the Onvexia blockchain analytics platform

## Facts

- Endpoint: GET https://onvexia.com/v1/stories/%7Bid%7D/posts
- 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-story-posts-retrieval-9458c730
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BR7OdgG4ICzmq0oLefCRX

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-story-posts-retrieval-9458c730
```

Example prompt: Pull all the posts published under Onvexia story ID 'btc-2024-supply-analysis' so I can review their blockchain analytics coverage for that narrative.

## When to prefer this

Use this endpoint when you need to retrieve all published analytical posts associated with a specific Onvexia story thread — particularly when researching a specific blockchain asset narrative, gathering coverage documents across ten chains, or compiling labelled address and supply-age history documents published under a known story ID. Prefer this over generic news APIs when you need crypto-native, on-chain analytical content fused with document labelling going back to 2008.

## Known failure modes

- Invalid or non-existent story ID returns an empty data array
- Payment failure (402) if USDC micropayment of $0.001 is not included
- Malformed story ID in URL path causes 400 or 404 error
- Story exists but has no published posts, returning empty data array
- Rate limiting or API key errors if authentication is missing

## 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 posts associated with the specified story ID, along with meta information including a link to the OpenAPI documentation and the endpoint path. Each post likely includes analytical content, blockchain coverage, labelled address data, or supply-age history relevant to the parent story.

## 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/stories/{id}/posts"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-story-posts-retrieval-9458c730/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)