# Onvexia Alert Test

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

Triggers a test execution of a configured blockchain analytics alert by its ID to verify it fires correctly.

## Facts

- Endpoint: POST https://onvexia.com/v1/alerts/%7Bid%7D/test
- 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-test-fdc223e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XrSaB9vV636w8-Ju3Bc6m

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-test-fdc223e8 -d '<json body>'
```

Example prompt: Can you run a test fire on my Onvexia alert with ID alert_abc123 to make sure it's set up correctly and will trigger when the conditions are met?

## When to prefer this

Use this endpoint when you need to validate that a specific configured alert on Onvexia is correctly set up and will fire under the right conditions, before relying on it for production monitoring. It is the right choice when debugging silent alerts, performing QA on new alert rules, or confirming alert logic after editing conditions — as opposed to querying asset analytics directly or listing alerts.

## Known failure modes

- Alert ID not found — returns empty data or 404-equivalent error
- Invalid or missing alert ID in path — malformed request
- Alert misconfigured upstream — test executes but returns no meaningful result
- Rate limiting or payment failure via x402 micro-payment — call rejected
- Network timeout if chain data lookup takes too long

## 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 the test result details and a 'meta' object with endpoint and documentation URL references. The data array may be empty if the alert did not match any current conditions, confirming the alert is reachable and operable.

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

## More

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