Free
$0/month
For testing your first agent data workflows.
500 credits · one time
No overage
Start free- Read-only data API access
- One unified credit balance
- No payment setup for the free plan
Read-only data APIs for AI agents
Pricing for read-only data APIs.
Search the web, read public social and app data, and scrape pages through one fetcher gateway. Start free with 500 one-time credits, then scale with a monthly plan.
One subscriptionOne unified credit balance
Plans
Choose the plan that fits your agent workload
All plans cover read-only fetcher data. Provider availability follows the current fetcher deployment.
Developer
$19/month
For production agents and smaller workloads.
10,000 credits · every month
$20 per 10,000 additional credits · capped
Choose Developer- All enabled read-only provider surfaces
- Monthly credit grant with no rollover
- Optional overage with an explicit cap
ProMOST POPULAR
$99/month
For higher-volume agent workloads.
100,000 credits · every month
$10 per 10,000 additional credits · capped
Choose Pro- All enabled read-only provider surfaces
- Monthly credit grant with no rollover
- Optional overage with an explicit cap
Credits are for metered read-only fetcher requests. Failed requests cost zero. Monthly credits do not roll over, and paid-plan overage requires an explicit cap.
Usage model
How unified credits work
Credits are the shared usage unit for metered, read-only fetcher requests. Your plan and overage settings apply to fetcher data reads only. Publishing and other write actions are not part of this launch.
Free includes 500 one-time credits. Developer is $19/month with 10,000 credits per cycle; Pro is $99/month with 100,000 credits per cycle. Overage is opt-in and capped, and Free has no overage.
Annual billing is available and gives two months free — Developer is $190/year and Pro is $990/year.
The credit cost of an individual request depends on the provider and route being called. ReplyNodes does not publish a fixed per-action price list here because it changes with the live deployment.
The live source of truth for provider, route, and per-request credit costs is the public capabilities document: it reports the cost of every callable route in the billing.credit_cost field. This page does not restate those numbers, so it can never drift from the live deployment.
Usage controls
Stay in control of overage
Overage is optional. Set an explicit monthly overage cap in billing before additional credits can be used. Requests stop when the cap is reached.
- Developer$20 per 10,000 additional credits
- Pro$10 per 10,000 additional credits
- FreeNo overage
Developer access
Use one fetcher key everywhere.
Fetcher owns billing and key management. Each user has exactly one active, long-lived fetcher API key for the read-only data API.