# Onvexia Asset Delete

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

Delete a specific asset record by ID from the Onvexia blockchain analytics platform

## Facts

- Endpoint: DELETE https://onvexia.com/v1/assets/%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-asset-delete-3f7a5387
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lTZs-tXy2Mgs_2ctc4swi

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-asset-delete-3f7a5387 -d '<json body>'
```

Example prompt: Delete the asset with ID 'eth-0xabc123' from Onvexia so it's no longer tracked in the blockchain analytics coverage.

## When to prefer this

Use this endpoint when you need to remove a specific asset record from Onvexia's blockchain analytics database by its unique ID. Prefer this when managing your own tracked asset list, cleaning up stale or deprecated entries, or deregistering tokens that are no longer relevant to your coverage. Not suitable for bulk deletion or querying asset data.

## Known failure modes

- Asset ID not found — returns empty data with 404 or equivalent
- Invalid asset ID format — malformed request rejected
- Insufficient payment — x402 payment of 0.001 USDC not provided or rejected
- Unauthorized deletion attempt — asset may be read-only or externally sourced
- Rate limiting — too many DELETE requests in a short window

## 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 response with an empty data array and meta object containing a link to the Onvexia OpenAPI docs and the endpoint path; confirms the deletion was processed.

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

## More

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