APIs that feel native.
One key. One shape. Call it like you'd call your own code.
$ curl "https://api.parseapi.com/ip/8.8.8.8" \ -H "X-API-Key: YOUR_API_KEY" // 200 · ~21ms US · ~66ms worldwide { "ip": "8.8.8.8", "country": "US", "country_name": "United States", "continent": "NA", "asn": "AS15169", "asn_name": "Google LLC"}
Messy in. Clean out.
Whatever you have, one call turns it into an answer.
SPEED
21ms
US median
66ms
Worldwide
Fast enough to call inline, no spinner, no background job. Core lookups, measured every 30 minutes from 21 cities worldwide. Some deep checks take longer.
See live status →COVERAGE
One key. All of the things.
Measure · how high, how many, how hot?
DATA
Official sources. Worldwide scale.
Fields come from registries, postal authorities, and statistics agencies. Sources refresh on a schedule, so what comes back is current.
DEEP DATA
One endpoint. Two depths.
Every endpoint returns a full, real response, even on Free. Add one parameter on a paid plan and get the same response back, plus a nested deep object with the richer fields (datacenter flags, deliverability, DNS records). Nothing to re-integrate when you upgrade. Same route. Same fields. You opt in only when you need it.
GET /ip/8.8.8.8GET /ip/8.8.8.8?deep=trueBULK
Verify the whole file.
Drop a spreadsheet. It detects every column we have an API for (emails, phone numbers, IPs, postal codes) and writes the answers in new columns beside them. Priced per column. Junk is free.
Drop a file →DX
It just works.
Auth, errors, and docs. All exactly where you'd look for them.
X-API-Key: YOUR_API_KEYOne header
X-API-Key or Authorization: Bearer. Same key, either header. Copy it in and start calling.
{ code, message, docs, request_id }Errors you can act on
Every failure returns the same shape: a code, a message, a link to the exact fix, and a request ID to trace it.
/docs#not_foundDocs that answer it
Every field explained. Every error paired with the fix, so the next step is always obvious.
PLANS
Big quotas. One price per team.
Upgrade when you outgrow it. Start is $20/mo for 1M requests, Pro is $100/mo for 10M. No per-seat billing.
WHY
An API should feel native. Built into your stack, not bolted onto it.
That's worth arguing about a single field name for a week before we ship it. We use parseAPI every day ourselves, so it has to be good, not just correct, with docs that tell the truth.