Does the Agent Data API have a subscription?

No. You pay per request in USDC over x402 (from $0.002), buy a Pro pass for 1 hour, 1 day or 7 days that covers every slice, or call the same endpoints through RealtimeAPI.ai where a free key gives 1,000 calls a month across every feed.

How does pay per request work?

GET any data endpoint with no key. The response is HTTP 402 with the USDC amount, network and payTo address. Sign it with an x402 client (USDC on Base, no gas) and repeat the request with the x-payment header. One settled payment, one response.

What does a pass include?

A pass returns an adk_live_ key with the Pro tier for its duration: 60 requests a minute, 20,000 a day, every slice (energy, sensors, weather, news) and the history endpoints. Buying another pass while one is active extends it.

Pricing

Pay per call, buy a pass for a job, or go free through RealtimeAPI.

No subscriptions. One key covers energy, sensors, weather and news.

Free key

10 requests a minute, 5 a day, every slice. A taster.

Get a key

Per request

$0.002 to $0.02

USDC over x402. GET with no key, pay the 402, get the data. No account, gasless on Base.

Price table

Pass, every slice

$1 / $3 / $8

1 hour, 1 day or 7 days of Pro: 60/min, 20,000/day, history endpoints, all four slices. Returns a key.

POST agent-subscribe

RealtimeAPI

Through RealtimeAPI.ai

1,000 calls a month, free, with one key.

These four slices are feeds on RealtimeAPI.ai, the agent data gateway we run. A free RealtimeAPI key covers 1,000 calls a month across every feed there, including macro, crypto, stocks and prediction markets, served from the edge with honest data-age headers.

griddata sensordata weatherdata newssignals mcp.realtimeapi.ai

Set up with one prompt →Open RealtimeAPI.ai

no card, no subscription, key in one call

1,000

free calls a month, across every feed on RealtimeAPI

of our feeds there: griddata, sensordata, weatherdata, newssignals

key for these and every other RealtimeAPI feed, plus one MCP server

edge

regional copies for cadences of 15 s and up, data-age on every response

Per request, by slice

Grid and energy data

Endpoint	USDC	Cadence	Tier
`GET /energy/api/v1/regions`	$0.005	Refreshes every 24 hours.	Free
`GET /energy/api/v1/power/prices/{market}/{region}`	$0.010	Refreshes every 5 minutes.	Free
`GET /energy/api/v1/power/prices/{market}/{region}/day-ahead`	$0.010	Refreshes every 30 minutes.	Free
`GET /energy/api/v1/power/prices/{market}/{region}/history`	$0.020	Refreshes every 5 minutes.	Pro
`GET /energy/api/v1/power/load/{market}/{region}`	$0.010	Refreshes every 5 minutes.	Free
`GET /energy/api/v1/power/generation/{market}/{region}`	$0.010	Refreshes every 5 minutes.	Free
`GET /energy/api/v1/power/windows/{market}/{region}`	$0.015	Refreshes every 30 minutes.	Free
`GET /energy/api/v1/carbon/{region}`	$0.005	Refreshes every 30 minutes.	Free
`GET /energy/api/v1/petroleum/weekly`	$0.010	Refreshes every 7 days.	Free

Environmental sensors

Endpoint	USDC	Cadence	Tier
`GET /sensors/api/v1/stations/near`	$0.005	Refreshes every 24 hours.	Free
`GET /sensors/api/v1/air/{station_id}`	$0.005	Refreshes every 60 minutes.	Free
`GET /sensors/api/v1/air/near`	$0.010	Refreshes every 60 minutes.	Free
`GET /sensors/api/v1/water/gauge/{site}`	$0.005	Refreshes every 15 minutes.	Free
`GET /sensors/api/v1/water/gauge/{site}/history`	$0.020	Refreshes every 15 minutes.	Pro
`GET /sensors/api/v1/tides/{station}`	$0.005	Refreshes every 6 minutes.	Free
`GET /sensors/api/v1/tides/{station}/predictions`	$0.005	Refreshes every 24 hours.	Free
`GET /sensors/api/v1/quakes/recent`	$0.005	Refreshes every 60 seconds.	Free

Weather alerts and forecasts

Endpoint	USDC	Cadence	Tier
`GET /weather/api/v1/alerts`	$0.002	Refreshes every 60 seconds.	Free
`GET /weather/api/v1/alerts/{alert_id}`	$0.002	Refreshes every 60 seconds.	Free
`GET /weather/api/v1/current`	$0.003	Refreshes every 5 minutes.	Free
`GET /weather/api/v1/forecast/hourly`	$0.005	Refreshes every 60 minutes or on a new model cycle.	Free
`GET /weather/api/v1/forecast/daily`	$0.005	Refreshes every 60 minutes or on a new model cycle.	Free
`GET /weather/api/v1/stations/near`	$0.001	Refreshes every 24 hours.	Free

News signals and trends

Endpoint	USDC	Cadence	Tier
`GET /news/api/v1/entities`	$0.005	Refreshes every 24 hours.	Free
`GET /news/api/v1/sentiment/{entity}`	$0.010	Refreshes every 15 minutes.	Free
`GET /news/api/v1/tickers/{symbol}/news-score`	$0.010	Refreshes every 15 minutes.	Free
`GET /news/api/v1/entities/trending`	$0.015	Refreshes every 15 minutes.	Free
`GET /news/api/v1/events`	$0.010	Refreshes every 15 minutes.	Free
`GET /news/api/v1/sentiment/{entity}/history`	$0.020	Refreshes every 15 minutes.	Pro
`GET /news/api/v1/trending/people`	$0.015	Refreshes every 60 minutes.	Free
`GET /news/api/v1/trending/topics`	$0.015	Refreshes every 60 minutes.	Free
`GET /news/api/v1/top-stories`	$0.010	Refreshes every 15 minutes.	Free

Set up RealtimeAPI with one prompt

Set up RealtimeAPI.ai for me so I can use the AgentDataAPI feeds through it: griddata (power prices and grid data), sensordata (environmental sensors), weatherdata (weather alerts and forecasts), newssignals (news signals and trends). RealtimeAPI gives AI agents real-time data through one API and one key. A free key includes 1,000 calls a month across every feed, including wholesale power prices and carbon intensity, air quality and river gauges, weather alerts and forecasts, and news sentiment and trending signals.
If you can run commands or edit files yourself, do each step. Otherwise walk me through them one at a time and wait for me to confirm each one.

Step 1: Add the MCP server
Claude Code: run  claude mcp add --transport http realtimeapi https://mcp.realtimeapi.ai/mcp
Cursor, Windsurf or any JSON config: add {"mcpServers": {"realtimeapi": {"url": "https://mcp.realtimeapi.ai/mcp"}}}
Codex: add [mcp_servers.realtimeapi] with command = "npx" and args = ["-y", "mcp-remote", "https://mcp.realtimeapi.ai/mcp"] to ~/.codex/config.toml
No MCP support? Everything below also works over plain HTTP against https://api.realtimeapi.ai.

Step 2: Add the RealtimeAPI skill
Claude Code: run  mkdir -p ~/.claude/skills/realtimeapi && curl -fsSL https://realtimeapi.ai/skills/realtimeapi/SKILL.md -o ~/.claude/skills/realtimeapi/SKILL.md
Other agents: append the contents of https://realtimeapi.ai/skills/realtimeapi/SKILL.md to AGENTS.md or your project rules file.

Step 3: Get access
Ask me for my email, then call the create_free_key tool with it (or POST https://api.realtimeapi.ai/keys/free with {"email": "<my email>"}). It returns a free key worth 1,000 calls a month across every feed. Save it for me: set it as the RTAPI_KEY environment variable and re-add the MCP server with the header X-API-Key: <the key> (Claude Code: claude mcp remove realtimeapi, then claude mcp add --transport http realtimeapi https://mcp.realtimeapi.ai/mcp --header "X-API-Key: <the key>"). Never ask me to paste a key into this chat, and do not repeat the full key back to me.
If I already pay with an x402 wallet (USDC on Base), you can skip the key and pay per call instead: https://realtimeapi.ai/docs#x402

Step 4: Check it works
Call discover with "wholesale electricity price right now" and call_feed on the best match (feed griddata), then discover with "severe weather alerts active" and "air quality near me". Give me a short summary of each answer with its as_of time, status field and how old the cached copy is (the X-RTAPI-Data-Age header, seconds since the gateway fetched it).

Reference: https://realtimeapi.ai/llms.txt (every feed and price), https://agentdataapi.com/llms.txt (endpoints and the response envelope).