ParseAPI for agents
Better data.
For your agent.
Clean and enrich files. Validate customer details. Look up places, companies and more. One connection to the AI you already use.
Connect through MCP. Use your ParseAPI account.
Standardize the dates in orders.csv. Keep the originals.
| date | parse_date | parse_duplicate |
|---|---|---|
| 2026/10/01 | 2026-10-01 | false |
| 2026.10.02 | 2026-10-02 | false |
| 2026-10-03 | 2026-10-03 | false |
From file to finished
Your file. More useful.
Give your agent a task. ParseAPI handles the supported fields, and your agent brings back the result.
- 01
Start with your file.
Use a CSV, TSV or text file. An agent with file access can convert an Excel or Numbers sheet to CSV first.
- 02
Preview the work.
Review the detected fields, available checks and quote. Set a spending limit before the full file runs.
- 03
Get a better file back.
Download your original rows and columns with results added. Duplicates are flagged, so you decide what to keep.
More than one kind of data.
Work with email, phone, address, IP, domain and date fields in the same file. Results depend on the field and the check. Missing facts stay unknown.
See all 13 supported checks
Email · Phone · Carrier · Caller ID · HLR · IP · Domain · User agent · Country · Postal · Address · Name · Date
Use ParseAPI to clean and enrich contacts.csv. Preview the detected columns and available checks, then show me the quote before starting. Keep every original row and column. Flag duplicates without deleting them, and leave unknown results unknown. Give me the finished CSV to download.
Connect below, then attach your file in an agent that can upload and download files.
One question works, too
A lookup. A clearer next step.
Investigate a customer issue, explain a result, or build with real API responses. See how a lookup becomes useful.
01Resolve a signup problemAn email looks right, but a customer cannot sign up.
The lookup
Check the address with Email.
hello@example.com
Example response excerpt
- valid: true
- The syntax passes.
- domain_valid: false
- The domain has no mail route.
The next step
Give the customer a useful next step.
This address is formatted correctly, but its domain does not accept email. Check the domain or use another address.
Turn a failed check into an explanation someone can act on.
Try this workflow
Help me resolve a signup problem for hello@example.com. Use the ParseAPI email tool with deep false. Explain the returned syntax and mail-routing checks, then draft a short message telling the customer what to check next. Keep unknown values unknown and distinguish mail routing from mailbox existence.Core checks cover syntax and mail routing. They do not establish that an individual mailbox exists.
Email reference02Investigate a support issueA domain has a website. Why does its email bounce?
The lookup
Inspect its DNS and mail routing together.
example.com
Example lookup findings
- DNS · A records
- A website address can exist independently of mail routing.
- MX · 0 "."
- A null MX record explicitly declines email.
The next step
Narrow the investigation.
Website and email use separate records. This domain explicitly declines mail. Confirm the intended recipient domain before investigating a mailbox.
Bring related lookups into one explanation and identify the next thing to check.
Try this workflow
Investigate why email to example.com might bounce even if its website resolves. Use the ParseAPI dns tool with domain example.com and type A, then the mx tool for the same domain. Explain the returned records and suggest the next diagnostic step. A priority-0 MX host of . means the domain explicitly declines mail. An empty MX list alone does not rule out A/AAAA fallback. Keep missing values unknown and distinguish DNS records from website health and mailbox existence.Published records explain this routing result. They do not prove website health or mailbox existence.
DNS reference03Build the check into your appYour signup form needs more than a generic “invalid email” message.
The lookup
Inspect Email, then build around its response.
Add an email check to this signup flow.
Example application behavior
- Invalid syntax
- Ask for a correctly formatted address.
- Missing mail route
- Explain the domain problem.
- Request error
- Offer a retry without calling the address invalid.
The next step
Put the explanation in the form.
This domain does not accept email. Check the address and try again.
Your coding agent has a response to work with and clear behavior to implement.
Try this workflow
Add a ParseAPI email check to this project's signup flow. Follow https://parseapi.com/ai and https://parseapi.com/docs/email. First use the email tool with hello@example.com and deep false to inspect a core response. Implement API calls for submitted addresses, with distinct messages for invalid syntax and missing mail routing. Handle request errors separately, preserve unknown values, and keep secret API keys on the server. Core checks do not establish mailbox existence.The running app makes its own API calls. Secret keys stay on the server, and unknown results need their own handling.
Agent integration guideIllustrative examples. Connect below, then use a prompt to get your own result. These workflows use core lookups from your request allowance.
Compare timezones, complete an address, find industry codes and more. Explore a task when you need it.
Browse all 11 task prompts
Email & domainsFind out where mail should go.
Inspect the published mail records for a domain when you are investigating an email problem.
Try this task
Check the mail routing for example.com using the ParseAPI mx tool. Explain the returned priorities and hosts. A priority-0 host of . is null MX: the domain explicitly accepts no mail. An empty MX list alone does not rule out A/AAAA fallback. Do not infer that an individual mailbox exists.What you getAn explanation of the domain's published MX records, including whether it explicitly declines mail. This does not test a mailbox.
MX response referenceSchedulingGet everyone on the same clock.
Compare a meeting time across cities using timezone rules for that date, including daylight saving changes.
Try this task
Use the ParseAPI time tool with timezone America/New_York, at 2026-11-02T09:00, targets ["Europe/London", "Asia/Tokyo"], disambiguation reject and deep false. Make a table of the source and target local dates, times and UTC offsets. Flag any next-day result. If the source time is ambiguous or nonexistent, ask me to resolve it. Do not create a calendar event.What you getOne proposed time translated into each location, with the date and offset visible. You can compare working hours before sending an invitation.
Time response referenceSchedulingSpot a holiday before you pick a date.
Check a launch, appointment or campaign date against a country’s holiday calendar before you finalize the plan.
Try this task
Check November 26, 2026 in the United States using the ParseAPI holiday_date tool with country US and date 2026-11-26. Explain the returned holiday and its type, distinguishing a public holiday from an observance. A null holiday means none was returned for this date. Do not infer that a particular business is closed.What you getHoliday context for your chosen date. Individual opening hours and regional or company schedules still need their own check.
Holiday response referenceCustomer recordsTurn a partial address into choices.
Help someone finish a US address with matching suggestions and location context, without inventing the missing pieces.
Try this task
Use the ParseAPI address_search tool with query "1600 Pennsylvania", country US, city Washington and state DC. Show the returned address suggestions and ask me to choose if more than one matches. If none are returned, explain reason and ask for the missing context. Do not invent a house number, unit or match, or treat a record match as proof of postal deliverability.What you getAddress candidates someone can review, or a clear request for more information. Useful for intake forms and support conversations.
Address response referenceCustomer recordsMake phone fields consistent.
Turn local formatting into a consistent international number using the supplied country and numbering rules.
Try this task
Use the ParseAPI phone tool with number "(415) 555-2671", country US and deep false. Explain the returned validity and formatting fields, then show the international form only if supported by the result. Preserve any extension. Do not guess a missing country or claim the number is assigned, reachable or owned by a particular person.What you getA consistent phone value and an explanation of any format problem. Numbering-plan validity does not establish reachability.
Phone response referenceSupport & debuggingSee where a domain points.
Bring published DNS records into a deployment or support investigation, with their record types and cache lifetimes.
Try this task
Use the ParseAPI dns tool with domain example.com and type A. Explain the returned addresses, any CNAME chain and TTLs. Summarize what this lookup shows about DNS resolution. Do not treat a DNS result as proof that the website is healthy or that all resolvers have the same cached records.What you getA readable view of the returned DNS records to compare with your intended configuration. Website health remains a separate check.
DNS response referenceSupport & debuggingPut an IP address in context.
Add the available network, ASN and country information to an IP from a support ticket or application log.
Try this task
Use the ParseAPI ip tool with ip 8.8.8.8 and deep false. Summarize the returned network, ASN and country fields for a support note. Keep missing fields unknown. Explain that IP geography is approximate and does not identify a person, a precise location or malicious intent.What you getNetwork context you can use while investigating a request, with the limits of IP geography kept visible.
IP response referenceMaps & locationsGive coordinates some context.
Look up the country, administrative areas and timezone for a map pin, then use those fields in your records or app.
Try this task
Use the ParseAPI point tool with lat 40.7128, lon -74.006 and deep false. Summarize the returned country, state, district and IANA timezone. Keep missing values unknown. Do not infer a street address, a nearby business or a delivery area from these fields.What you getPlace and timezone fields for the supplied coordinates. Useful when a location starts as a pin instead of a written address.
Point response referenceBusiness researchFind a business category that fits.
Search US NAICS titles and activities from a plain-language description, then compare the matching categories.
Try this task
Use the ParseAPI industry_search tool with query "coffee shop", limit 5 and deep false. Compare the returned US NAICS 2022 codes, titles and match evidence. Explain why each candidate may fit and ask what the business primarily does before suggesting a final choice. Do not present a search match as an official classification.What you getA shortlist of categories grounded in the catalog, with differences to review before choosing one.
Industry response referenceCustomer recordsCatch bank-detail input mistakes.
Check an IBAN’s structure and checksums, and explain the available bank-directory match in plain language.
Try this task
Use the ParseAPI bank tool with the public example iban "DE89 3704 0044 0532 0130 00" and deep false. Preserve the original input. Explain valid, checks, issues and any returned bank name or BIC. Distinguish an unsupported national check from a failed one. Keep missing directory facts unknown. These checks do not establish account existence, ownership or payment reachability.What you getAn explanation of the format checks and any available bank identity. Account verification and payment approval remain separate steps.
Bank response referenceMoney & planningKeep the rate with the result.
Convert an amount using a reference rate, and keep the applicable date visible in the answer.
Try this task
Convert 100 USD to EUR using the ParseAPI currency_rate tool with base USD, quote EUR and amount 100. Show converted, rate and the returned date. Describe it as a reference conversion, not a bank or card payment quote. If a value is unavailable, leave it unknown.What you getThe converted amount alongside its reference rate and date. The latest available rate may be from an earlier business day.
Currency response referencePrompts use example inputs. Replace them with yours. These tasks use core lookups from your request allowance; no metered Deep checks are requested.
One connection
At home in your AI.
Add ParseAPI to your client, sign in, and ask for what you need. Your agent finds the tools for the task.
Claude Code
The terminalRun the command, then use /mcp in Claude Code to sign in.
ChatGPT
Create a custom app in developer mode. Choose OAuth and paste the URL.
Add the server, then finish sign-in in your browser.
Manual setup and client guides
https://mcp.parseapi.comCursor: add this to .cursor/mcp.json in your project. Merge it with any existing servers. Cursor guide.
{
"mcpServers": {
"parseAPI": { "url": "https://mcp.parseapi.com" }
}
}VS Code uses a different config shape. Add this to .vscode/mcp.json, merging existing servers. VS Code guide.
{
"servers": {
"parseAPI": {
"type": "http",
"url": "https://mcp.parseapi.com"
}
}
}claude mcp add --transport http parseAPI https://mcp.parseapi.com/mcp to finish sign-in. Claude Code guide.Claude app: add the server URL as a custom connector, choose Connect, then enable it in your chat. Claude guide.
ChatGPT: create a custom app in developer mode with this URL and OAuth, then enable the app in your conversation. Access depends on your account and workspace settings. ChatGPT guide.
CI, API keys, and local stdio
Headless clients can send a secret API key in X-API-Key. Replace the placeholder below with your key. AI setup has ready-to-copy configuration for your account.
{
"mcpServers": {
"parseAPI": {
"url": "https://mcp.parseapi.com",
"headers": { "X-API-Key": "parse_YOUR_SECRET_KEY" }
}
}
}For a client that runs a local stdio server, use npx parseapi-mcp with PARSEAPI_KEY set. This configuration requires Node.js and a client that accepts mcpServers.
{
"mcpServers": {
"parseAPI": {
"command": "npx",
"args": ["-y", "parseapi-mcp"],
"env": { "PARSEAPI_KEY": "parse_YOUR_SECRET_KEY" }
}
}
}Keep configurations containing a secret key out of shared repositories. Key guide.
Simple to account for
Your account.
Your existing plan.
No separate MCP subscription. Individual lookups use your plan; metered lookups and Deep checks use their respective allowances.
Files get a quote before processing. Work covered by your plan can run in the agent. If payment is needed, you complete it in the browser. A spending limit does not charge a saved card.
Under the hood
A tool for the task.
Explore the lookups and file tools your agent can use. Search by name, input or what you want to do.
File workflow and popular lookups
bulk_upload
ReferencePrepare a private file upload.
Inputs and details
Your agent transfers the CSV directly using the returned upload URL. This does not start processing.
Inputs:
country(optional),file_size,filename,lang(optional)bulk_preview
ReferencePreview a file and its quote.
Inputs and details
Review detected columns and select supported checks before starting the full file.
Inputs:
checks(optional),idbulk_start
ReferenceStart a file using its accepted quote and a spending limit.
Inputs and details
If payment is needed, complete checkout in the browser.
Inputs:
id,max_cost_cents,quote_idbulk_status
ReferenceCheck a file job’s progress.
Inputs and details
Recover the existing job before retrying work when an earlier result is uncertain.
Inputs:
idbulk_result
ReferenceGet an expiring download URL for the finished CSV.
Inputs and details
The agent downloads the file directly.
Inputs:
idemail
ReferenceCheck email syntax, mail routing, consumer mailbox, disposable and role flags, reserved domain type, and known domain typos.
Inputs and details
Deep checks mailbox deliverability and catchall behavior. Recent mailbox results can be reused.
Inputs:
deep(optional),emailphone
ReferenceParse and validate a phone number with national and international display formats.
Inputs and details
Deep adds numbering-plan state and timezone on every plan. These do not locate a handset.
Inputs:
country(optional),deep(optional),numberaddress
ReferenceLook up a US street address.
Inputs and details
Returns validation, an official-record match, standardized parts and coordinates where available. A record match does not establish postal deliverability.
Inputs:
address,country(optional),deep(optional)
A few useful details
Good to know.
Can any MCP client work with a file?
The agent also needs access to the file and the ability to upload and download it. ParseAPI supplies private, expiring transfer URLs; the agent transfers the bytes directly. File contents are not pasted into MCP tool arguments. A client with chat tools alone may need a file-capable runtime.
Does ParseAPI change my original file?
You get a new CSV with the original rows and columns plus the results. Duplicate rows are flagged, not removed. The agent can make further edits if you ask it to.
The app did not open, or I cannot add a connector
Use manual setup and the guide for your client. Desktop install links need the matching app installed. Custom connectors may need to be enabled by your workspace admin.
I connected, but my AI is not using the tools
Finish browser authorization, enable ParseAPI in the client, and try an example prompt. In Claude Code, use /mcp to check the connection. A typed answer alone does not confirm a tool call.
A tool returns an error
Read the returned code and message. invalid_api_key needs a reconnect or a valid key. quota_exceeded needs available allowance. For a rate limit, pause before retrying.
Error reference · Retry guidance. Unknown values can be null, and validation can return valid: false without an error. How to read responses.
Agent integration guide · SDKs
Source · Cursor directory · Email