Plans
Start free. Scale infinitely.
No credit card. 200 credits on the house. Pay only for what you call.
Most popular
Developer
$100/mo
- +5,000 credits
- +100 req/min rate limit
- +Overage available beyond included quota
Team
$300/mo
- +20,000 credits
- +Workspace
- +300 req/min rate limit
- +Overage available beyond included quota
- +Slack support
Company
$1000/mo
- +100,000 credits
- +Workspace
- +500 req/min rate limit
- +Overage available beyond included quota
- +Slack support
- +SLA agreement
Enterprise
Custom- +Custom integrations & volume pricing
- +Dedicated support and SLA
- +Custom rate limits
Billing
How credits work.
What costs credits?
Calling an endpoint costs credits — the per-call cost varies by API. Building or revising a private (off-catalog) API costs 75 credits for a new build and 50 for a revision. Browsing, subscribing, and contributing back to the public catalog are always free.
How is the per-call cost calculated?
A call's cost reflects the real work behind it — proxy rotation and anti-bot handling, the bandwidth moved, and the internal requests Parse makes to the source site to fulfill your one request. Heavier sites and multi-step actions cost more; a simple read costs less. You always get the credit headers back on every response so the math is never a surprise.
How does that compare to browser-based scrapers?
Usually much cheaper. Browser-rendering tools that render a full headless browser per request pay to load, script, and tear down a whole page every time. Parse talks straight to the network layer underneath, so one typed call replaces a page-load — you pay for the data you asked for, not for a browser session to render it.
Can I add more credits if I run out?
Yes. Paid plans can top up credits anytime from the billing page — preset packs or a custom amount. Top-up credits don't expire at the end of your billing cycle.
Do I need a credit card to start?
No. The free plan comes with 200 credits and no card required. Upgrade only when you need more throughput or higher rate limits.