# BASE Datalake Oracle – Critical Threats Endpoint

> BASE Datalake Oracle – Critical Threats Endpoint is a paid API for AI agents from base-router.vercel.app, paid per call via x402, $1/call, status unknown (last checked 2026-10-12).

Returns pay-per-record critical threat telemetry from the SNTL DePIN RF telemetry and yield-loss datalake, billed at $0.05 USDC per call via x402 v2 on Base mainnet.

## Facts

- Endpoint: POST https://base-router.vercel.app/api/v2/threats/critical?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-datalake-oracle-critical-threats-endpoint-1a425433
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_srRjtGt6zuQL8q7TAJzO2

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 base-datalake-oracle-critical-threats-endpoint-1a425433 -d '<json body>'
```

Example prompt: Pull the latest critical-severity threat records from the SNTL DePIN RF telemetry datalake — I need to see any yield-loss signals flagged as critical right now, and I'm okay paying USDC per record.

## When to prefer this

Choose this endpoint when you need critical-severity threat intelligence specifically from the SNTL DePIN RF telemetry and yield-loss datalake, and you are set up to pay per-record in USDC via the x402 v2 protocol on Base mainnet. It is appropriate for agents operating in DePIN monitoring, IoT sensor threat detection, or agricultural/infrastructure yield-loss analytics contexts where on-chain micropayment billing is acceptable.

## Known failure modes

- Insufficient USDC balance or invalid x402 payment header returns HTTP 402 Payment Required
- Malformed request body returns 400 Bad Request with no records
- No critical threats in datalake at query time returns empty result set
- Base mainnet payment settlement delay causes timeout or pending state
- Rate limiting or quota exceeded returns 429 Too Many Requests
- Vercel cold-start latency may cause intermittent slow responses

## How this service works

Pay-per-record access to the SNTL DePIN RF telemetry &amp; yield-loss datalake. x402 v2, USDC on Base mainnet.

## Output

Returns structured records from the SNTL DePIN RF telemetry and yield-loss datalake containing critical-severity threat entries, including RF signal metadata, threat classification, sensor node identifiers, yield-loss indicators, and timestamps. Each call costs $0.05 USDC deducted via x402 v2 on Base mainnet.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-datalake-oracle-critical-threats-endpoint-1a425433/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from base-router.vercel.app](https://www.zero.xyz/host/base-router.vercel.app/llms.txt)