# Onvexia Delete Alert

> Onvexia Delete Alert 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).

Deletes a specific blockchain analytics alert by its ID from the Onvexia platform

## Facts

- Endpoint: DELETE https://onvexia.com/v1/alerts/%7Bid%7D
- 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-delete-alert-e90f73f4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GqGF3jOMqDI9ngiN-V-xp

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-delete-alert-e90f73f4 -d '<json body>'
```

Example prompt: Cancel alert ID 9f3a-1bc2 on Onvexia — I don't need to track that wallet movement anymore.

## When to prefer this

Use this endpoint when you need to programmatically remove a specific, previously created blockchain analytics alert from Onvexia, identified by its unique ID. Prefer this over manually managing alerts when automating alert lifecycle management in agent workflows that create and clean up alerts dynamically.

## Known failure modes

- Alert ID not found — returns empty data or 404-style error
- Invalid or malformed alert ID format — may return validation error
- Unauthorized access if payment or authentication is missing — 402 or 401 response
- Already-deleted alert — may return empty data or idempotency error
- Network timeout or service unavailability

## 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 an empty data array and a meta object containing the docs URL and the endpoint path, confirming the alert has been deleted.

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

## More

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