# SNTL DePIN Oracle x402 Proxy – Wallet Records

> SNTL DePIN Oracle x402 Proxy – Wallet Records is a paid API for AI agents from sntl-router.vercel.app, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-22).

Provides pay-per-record access to SNTL DePIN RF telemetry and yield loss oracle data for a specific wallet, settling payment in USDC on Solana.

## Facts

- Endpoint: GET https://sntl-router.vercel.app/api/v2/wallets/paid?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sntl-depin-oracle-x402-proxy-wallet-records-599d9109
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wc-lv8vT8H1xTUu6gDrdu

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-x402-proxy-wallet-records-599d9109
```

Example prompt: Pull the SNTL DePIN RF telemetry and yield loss oracle records for my wallet — I need the latest data from the SNTL datalake for this Solana address.

## When to prefer this

Use this endpoint when you need raw RF telemetry or yield loss oracle data specifically associated with a wallet address on the SNTL DePIN network, and you are set up to pay $0.50 USDC per call via the x402 payment protocol on Solana. Prefer this over general IoT or sensor APIs when working within the SNTL DePIN ecosystem.

## Known failure modes

- Payment not settled — returns HTTP 402 if USDC payment on Solana is not confirmed
- Invalid wallet address — may return empty results or error if address is malformed
- No records found — wallet has no associated DePIN telemetry in the datalake
- Vercel cold start latency — occasional slow response on first call
- Schema mismatch — input properties parameter may be ambiguous due to sparse schema definition

## 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-gated oracle records from the SNTL DePIN datalake including RF telemetry readings and yield loss metrics associated with the queried wallet, after settling $0.50 USDC on Solana to the SNTL treasury.

## 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-x402-proxy-wallet-records-599d9109/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)