ParseAPI
Free plan · From $20/moActively maintained
≈ 73visits/mo
Little sign of use · estimate, read Oct 13, 2026
- For
- Developers and teams adding email, phone, postal and IP lookups to apps or spreadsheets
- Price
- Free plan · From $20/mopricing page, read Oct 19, 2026
- Activity
- Actively maintainedrelease 7 days ago · site updated 9 days ago
- Company
- Parse API LLC · Domain since 2015terms of service · domain registered
- Runs as
- API
- Used for
- check email addresses for validity and disposable domains
- verify phone numbers and look up their carrier type
- enrich a spreadsheet of emails, phones or postal codes
- On the web since 2015, older than 93% of its shelfINITE Atlas
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsparseapi.com ↗
Free plan · From $20/mo
- Run byParse API LLCterms of service ↗
- Data processing agreementpublishedDPA ↗
- Privacy policy updated2026-10-13privacy policy ↗
These are ParseAPI's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP servercom.parseapi/mcpverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-19
- Address to connectmcp.parseapi.com
- OpenAPI spec92 pathsthe spec ↗
- API docsparseapi.com/apisthe vendor's page ↗
- MCP docsparseapi.com/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1
quackrMCP · sign-in
Provides temporary and private phone numbers that receive SMS messages for account verification, with an API and an email option.
72.2kFrom $0.10 per use2018 - #2
MobileValidateMCP · sign-in
Checks whether phone numbers and email addresses are registered on messaging, social and consumer apps, plus line type and carrier, via one API.
66ActiveFrom $0.00 per use - #3
AgentCall
Provisions phone numbers and SMS for AI agents to make and receive calls, send messages, and extract verification codes.
9ActiveFrom $0.40 per use - #4
CallNode
Gives phone numbers to your software: calls and texts arrive as JSON webhooks or a websocket, with your replies spoken back.
1ActiveFrom $2.99/mo - #5
call4me
Enables AI agents to make phone calls to businesses and retrieve information via MCP integration.
294 installs/moActiveFrom $0.25 per use - #6
SnipgetMCP · sign-in
Runs address parsing, phone normalization, fuzzy dedup and identifier checks as MCP tools or REST calls, with no LLM in the loop.
26 installs/moActiveFrom $15/mo
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use ParseAPI for?
Sign in to leave a noteWhat is ParseAPI?
Checks email addresses and phone numbers, resolves postal codes, and geolocates IPs, returning structured JSON responses via a single API key. It is listed in the Atlas under Voice and made by Parse API LLC.
Who is ParseAPI for?
Developers and teams adding email, phone, postal and IP lookups to apps or spreadsheets
How much does ParseAPI cost?
ParseAPI has a free plan; paid plans start at $20/mo, per its pricing page on 2026-10-19.
Is ParseAPI free?
Yes, ParseAPI has a free plan, per its pricing page on 2026-10-19.
Do people use ParseAPI?
Little sign of use: ≈ 73 visits/mo · estimate, 2026-10.
Is ParseAPI still maintained?
Actively maintained: release 7 days ago · site updated 9 days ago.
Who owns ParseAPI?
ParseAPI is run by Parse API LLC, per its terms of service (2026-10-19).
Does ParseAPI give refunds?
In its own words (terms of service, 2026-10-19): “Fees are generally non-refundable except where required by law or where we say otherwise in writing.”
What are alternatives to ParseAPI?
In Voice, by use: quackr, MobileValidate, AgentCall, CallNode, call4me, Snipget.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk