# Onvexia Alert Webhook Secret Retrieval

> Onvexia Alert Webhook Secret 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 webhook secret for a specific alert by its ID, used to verify incoming webhook payloads from Onvexia's blockchain analytics platform.

## Facts

- Endpoint: GET https://onvexia.com/v1/alerts/%7Bid%7D/webhook-secret
- 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-alert-webhook-secret-retrieval-dc8011bd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j6PDKF-eZSv14CSUrh32J

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-alert-webhook-secret-retrieval-dc8011bd
```

Example prompt: Can you fetch the webhook secret for my Onvexia alert with ID abc123 so I can set up signature verification on my server?

## When to prefer this

Use this endpoint when you need to retrieve or verify the webhook signing secret for a specific Onvexia blockchain alert, particularly when setting up server-side webhook signature verification, rotating secrets, or auditing your alert infrastructure. This is specifically for Onvexia's alert webhook security mechanism and should not be confused with general blockchain data or analytics endpoints.

## Known failure modes

- Alert ID not found — returns empty data array if the specified alert does not exist
- Unauthorized access — returns 401/402 if payment or authentication credentials are invalid or missing
- Malformed alert ID — returns error if the ID format is invalid
- Alert has been deleted — may return empty result for previously valid IDs

## 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 field containing the webhook secret associated with the specified alert ID, and a meta field with documentation links and the endpoint path. The secret is used to verify HMAC signatures on incoming webhook payloads sent by Onvexia when alert conditions are triggered.

## 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/alerts/{id}/webhook-secret"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-alert-webhook-secret-retrieval-dc8011bd/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)