# Onvexia Alerts Deliveries

> Onvexia Alerts Deliveries 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 paginated list of alert delivery records from the Onvexia blockchain analytics platform

## Facts

- Endpoint: GET https://onvexia.com/v1/alerts/deliveries
- 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-alerts-deliveries-5a4ce8eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H3HDFNL1ep27MOZBgrM0u

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-alerts-deliveries-5a4ce8eb
```

Example prompt: Pull the last 50 alert deliveries from Onvexia so I can see which blockchain monitoring alerts have recently fired and been sent.

## When to prefer this

Use this endpoint when you need to audit or monitor the delivery status of blockchain analytics alerts configured in Onvexia, particularly when tracking whether on-chain event notifications for crypto assets across its supported chains have been successfully dispatched. Prefer this over general analytics endpoints when your focus is specifically on alert pipeline health or delivery confirmation rather than raw on-chain data or asset metrics.

## Known failure modes

- Empty data array returned if no alert deliveries exist — this is not an error, it means no alerts were delivered
- Invalid limit parameter (must be a string integer ≤ 200) may result in a 400 error
- Payment not processed (x402 payment required at $0.001 USDC per call) results in 402 response
- Unauthenticated or failed payment leads to access denial
- Rate limiting may apply if the endpoint is called too frequently

## 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 alert delivery records (may be empty if no deliveries exist in range) and a `meta` object with coverage and provenance details including a link to the full OpenAPI spec at onvexia.com/openapi.json.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "string",
       "description": "Max 200"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "object",
     "properties": {
      "data": {
       "description": "The result — an array or object depending on the endpoint. An empty array means no rows in range, never that the metric is unsupported."
      },
      "meta": {
       "type": "object",
       "description": "Coverage and provenance: what was measured, and what is not held. A null label means no label is held, never that the subject is safe."
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "meta": {
   "docs": "https://onvexia.com/openapi.json",
   "endpoint": "/v1/alerts/deliveries"
  }
 }
}
```

## More

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