# SNTL DePIN Oracle – RF Telemetry & Yield Loss Chronicle

> SNTL DePIN Oracle – RF Telemetry & Yield Loss Chronicle is a paid API for AI agents from sntl-router.vercel.app, paid per call via x402, $0.75/call, status unknown (last checked 2026-09-14).

Returns pay-per-record RF telemetry and crop yield-loss data from the SNTL decentralized physical infrastructure network (DePIN) oracle datalake, billed at $0.75 USDC per call via x402 on Solana.

## Facts

- Endpoint: GET https://sntl-router.vercel.app/api/v2/chronicle
- Price: $0.75/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sntl-depin-oracle-rf-telemetry-yield-loss-chronicle-b26f55f8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SnRvtDHwnqhidw6W1PtiG

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 sntl-depin-oracle-rf-telemetry-yield-loss-chronicle-b26f55f8
```

Example prompt: Pull the latest RF telemetry and yield loss records from the SNTL DePIN oracle chronicle — I need to see what the sensors have logged for the crop fields in the current data window.

## When to prefer this

Choose this endpoint when you need on-demand, pay-per-record access to SNTL's proprietary DePIN RF telemetry or crop yield loss oracle data and can settle payments in USDC on Solana via x402. Prefer this over traditional REST data APIs when working in a decentralized, micropayment-native agent workflow that already handles x402 payment flows.

## Known failure modes

- Payment failure: insufficient USDC balance or Solana transaction rejection results in 402 Payment Required with no data returned
- Invalid properties filter: malformed query parameter may return empty result set or 400 error
- No matching records: query returns zero records if filter criteria match nothing in the datalake
- Rate limiting or gateway errors from Vercel hosting layer causing 5xx responses
- Oracle datalake temporarily unavailable causing timeout or 503

## How this service works

Pay-per-record access to the SNTL DePIN RF Telemetry & Yield Loss Oracle datalake. Settles in USDC on Solana to the SNTL treasury.

## Output

A set of DePIN oracle records from the SNTL chronicle datalake, including RF telemetry readings and yield loss metrics. Payment of $0.75 USDC is settled on Solana to the SNTL treasury via the x402 protocol before data is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sntl-depin-oracle-rf-telemetry-yield-loss-chronicle-b26f55f8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sntl-router.vercel.app](https://www.zero.xyz/host/sntl-router.vercel.app/llms.txt)