# SNTL DePIN Oracle – RF Telemetry & Yield Loss (Hivemapper)

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

Provides pay-per-record access to SNTL DePIN RF telemetry and yield loss oracle data sourced from the Hivemapper network, settling payments in USDC on Solana.

## Facts

- Endpoint: GET https://sntl-router.vercel.app/api/v2/rf/hivemapper
- Price: $1/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-hivemapper-5a6035ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XHnDuX9mSnKXRYaF9B1m-

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-hivemapper-5a6035ff
```

Example prompt: Pull the latest Hivemapper RF telemetry and yield loss records from the SNTL DePIN oracle — I need the coverage data for my current area of interest.

## When to prefer this

Choose this endpoint when you need decentralized, oracle-verified RF telemetry or yield loss data specifically from the Hivemapper DePIN network, and are willing to pay per record in USDC on Solana via x402 protocol. Prefer this over centralized RF data sources when provenance, decentralization, and on-chain settlement auditability matter.

## Known failure modes

- Payment not settled — USDC balance insufficient on Solana wallet returns 402 Payment Required
- Invalid or missing properties filter returns 400 Bad Request
- Hivemapper data unavailable for requested parameters returns empty result set
- Network timeout on Solana settlement causes delayed response
- Rate limiting if too many concurrent requests are made

## 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

Returns pay-per-record oracle data from the SNTL DePIN datalake, including RF telemetry measurements and yield loss figures sourced from the Hivemapper network, with payment settled in USDC on Solana.

## 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-hivemapper-5a6035ff/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)