80trust / 100

Depin Rewards

by depin-rewards in Markets & finance

x402 APIPassing, checked 43 min ago

Reward economics and earnings trend for a DePIN entity or subnetwork. Give network (helium) with an entity key or a subnetwork (iot, mobile). This is a keyed enrichment: without the Relay key configured it returns available false with a note; the keyless network, hotspot and wallet routes do not need it.

GET https://api.agentstools.dev/depin/rewards

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
27 ms typical, 158 ms slowest 5%
Last check
43 min ago
Next check
any minute now

How to call it

GET https://api.agentstools.dev/depin/rewards

Each call costs $0.02 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://api.agentstools.dev/depin/rewards?network=helium&subnetwork=mobile

Parameters

ParameterTypeRequiredDescription
daysintegerNoLookback window in days (default 7, max 30)
keystringNoOptional hotspot entity or asset key (base58)
networkstringNoDePIN network id (default helium) One of: helium.
subnetworkstringNoOptional subnetwork (default mobile) One of: iot, mobile.

Example response

The provider's example. We can't check it without paying.

{
  "attribution": [
    "Source: Relay Wireless (relaywireless.com)"
  ],
  "available": true,
  "by_reward_type": {
    "service_provider_reward": {
      "count": 7,
      "total_amount": 315000000000
    }
  },
  "network": "helium",
  "sampled_records": 100,
  "subnetwork": "mobile",
  "total_reward_records": 28006,
  "window": {
    "days": 7,
    "from": "2026-07-07T00:00:00Z",
    "to": "2026-07-14T00:00:00Z"
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.agentstools.dev/depin/rewards?network=helium&subnetwork=mobile'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.agentstools.dev/depin/rewards?network=helium&subnetwork=mobile' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.agentstools.dev%2Fdepin%2Frewards
const res = await pay("https://api.agentstools.dev/depin/rewards?network=helium&subnetwork=mobile");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.agentstools.dev/depin/rewards?network=helium&subnetwork=mobile")
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
43 min agoPassed40225 ms$0.02
5 h agoPassed402158 ms$0.02
9 h agoPassed40225 ms$0.02
12 h agoPassed402125 ms$0.02
16 h agoPassed40227 ms$0.02
20 h agoPassed40227 ms$0.02
24 h agoPassed40272 ms$0.02
27 h agoPassed40227 ms$0.02
31 h agoPassed402123 ms$0.02
35 h agoPassed40222 ms$0.02
38 h agoPassed40228 ms$0.02
42 h agoPassed40227 ms$0.02
45 h agoPassed40225 ms$0.02
2 days agoPassed402173 ms$0.02
2 days agoPassed40230 ms$0.02