# BASE Datalake Oracle – SNTL DePIN RF Telemetry & Yield-Loss Data

> BASE Datalake Oracle – SNTL DePIN RF Telemetry & Yield-Loss Data 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).

Provides pay-per-record access to SNTL DePIN radio-frequency telemetry and agricultural yield-loss data via micropayment on Base mainnet.

## Facts

- Endpoint: POST https://base-router.vercel.app/api/v2/wallets/target?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-sntl-depin-rf-telemetry-yield-loss-data-26e881ae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4w64W1nXuqAt28IXhfyBB

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-sntl-depin-rf-telemetry-yield-loss-data-26e881ae -d '<json body>'
```

Example prompt: Pull the latest SNTL DePIN RF telemetry and yield-loss records for wallet target 0xABC123 from the BASE Datalake Oracle — I'm okay with paying the per-record USDC fee on Base mainnet.

## When to prefer this

Choose this endpoint when you need raw RF telemetry or agricultural yield-loss data sourced from the SNTL DePIN sensor network and are willing to pay per record in USDC on Base mainnet. Prefer this over centralized data providers when decentralized provenance and on-chain payment are required, or when the specific SNTL DePIN dataset is the authoritative source for the target location or device.

## Known failure modes

- Insufficient USDC balance on Base mainnet causes payment failure and no data returned
- Invalid or unrecognized target identifier returns empty or error response
- x402 payment protocol handshake failure results in 402 Payment Required with no data
- Network congestion on Base mainnet delays payment confirmation
- Target has no records in the datalake, returning empty result set
- Vercel cold-start latency may cause timeout on first request

## 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 datalake containing RF telemetry readings and yield-loss metrics for the specified target, delivered after a successful micropayment of $0.05 USDC on Base mainnet via x402 v2 protocol.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-datalake-oracle-sntl-depin-rf-telemetry-yield-loss-data-26e881ae/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)