ParseAPI for your AI

Real-world checks.
Right in your AI.

Resolve a signup problem, investigate a customer issue, or build a feature around real API responses. Give your assistant the checks and reference data to take the next step.

Connect your AI See what you can do

Works through MCP. Uses your existing ParseAPI plan.

A lookup with a next stepExample

Why might this email address fail a signup check?

ParseAPI emailCore lookup

hello@example.com

valid: true Syntax passes
domain_valid: false No mail route

What it means

The address has valid syntax, but its domain does not accept email.

Illustrative core response. Mailbox checks are separate.

Why connect?

Good reasoning starts with the right inputs.

Your assistant brings the reasoning. ParseAPI supplies validation rules, maintained records and external lookups through one connection. Get consistent fields your assistant can explain and your application can use.

Start with a task

From a problem to a next step.

Choose a workflow. See the lookup, the explanation and what you can do with the result.

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

Resolve a signup problem

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 reference

02Investigate 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 a support issue

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 reference

03Build 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

Build the check into your app

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 guide

Illustrative examples. Connect below, then use a prompt to get your own result. These workflows use core lookups from your request allowance.

Bring it to the AI you use.

Choose your client. Connect your ParseAPI account.

Cursor
Open Cursor, add the server, and finish browser sign-in.
Add to Cursor
VS Code
Review the server in VS Code, then finish browser sign-in.
Add to VS Code
Claude
The app
Add the connector, then choose Connect to authorize it.
Add to Claude
Claude Code
The terminal
Run 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.
Other clients
Use the server URL with your preferred MCP client.
Manual setup

Add the server, then finish sign-in in your browser.

Manual setup and client guides

MCP server URL

https://mcp.parseapi.com

Cursor: add this to .cursor/mcp.json in your project. Merge it with any existing servers. Cursor guide.

Cursor · .cursor/mcp.json

{
  "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.

VS Code · .vscode/mcp.json

{
  "servers": {
    "parseAPI": {
      "type": "http",
      "url": "https://mcp.parseapi.com"
    }
  }
}

Claude Code · terminal command

claude mcp add --transport http parseAPI https://mcp.parseapi.com

Run this in your terminal. In Claude Code, use /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.

Remote HTTP · mcpServers config

{
  "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.

Local stdio · mcpServers config

{
  "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.

Same API. Same plan.

Tools return the API's JSON and look up data without editing your records. Calls use your existing plan, with no separate MCP subscription.

Metered lookups and metered deep checks use their own allowances. On-demand charges apply when enabled.

How usage works Core and deep

Start

1M requests / month

$20/mo

Compare plans

More ways to put it to work.

Compare timezones, complete an address, identify a vehicle, find industry codes and more. Explore a task when you need it.

Browse all 12 task prompts

Email & domains

Find out where mail should go.

Inspect the published mail records for a domain when you are investigating an email problem.

Try this task

Check a domain

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 reference

Money & planning

Keep 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 an amount

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 reference

Scheduling

Get everyone on the same clock.

Compare a meeting time across cities using timezone rules for that date, including daylight saving changes.

Try this task

Compare team times

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 reference

Scheduling

Spot 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 a launch date

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 reference

Customer records

Turn 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

Find address suggestions

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 reference

Customer records

Make phone fields consistent.

Turn local formatting into a consistent international number using the supplied country and numbering rules.

Try this task

Standardize a phone number

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 reference

Support & debugging

See where a domain points.

Bring published DNS records into a deployment or support investigation, with their record types and cache lifetimes.

Try this task

Inspect DNS records

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 reference

Support & debugging

Put 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

Explain an IP address

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 reference

Maps & locations

Give 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

Locate coordinates

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 reference

Business research

Find a business category that fits.

Search US NAICS titles and activities from a plain-language description, then compare the matching categories.

Try this task

Find industry candidates

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 reference

Inventory & records

Turn a VIN into a useful record.

Fill in the available year, make, model and body details for a vehicle record without manually decoding the VIN.

Try this task

Decode a vehicle VIN

Use the ParseAPI vehicle tool with vin 1HGCM82633A004352 and deep false. Summarize the returned validity, year, make, model, trim, body and vehicle type where available. Keep missing values unknown and flag a failed validation. Do not infer ownership, accident history, condition or outstanding repairs.

What you getDecoded vehicle details to review for an inventory or support record. This lookup is not a vehicle history report.

Vehicle response reference

Customer records

Catch bank-detail input mistakes.

Check an IBAN’s structure and checksums, and explain the available bank-directory match in plain language.

Try this task

Explain an IBAN check

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 reference

Prompts use example inputs. Replace them with yours. These tasks use core lookups from your request allowance; no metered Deep checks are requested.

Find the check your task needs.

67 tools. Search by name, input or task.

8 common tools · 67 available

postal
Reference
Resolve a postal code to its place, coordinates and timezone.
Inputs and details
Australian core localities lists suburb choices with city, state and state_name. Null or missing means unknown, and [] means no eligible choices in the reviewed reference. A single choice can coexist with city null, so do not infer a city or a user selection. These are geographic choices, not mailing-address verification. Deep adds area, population with its reporting period, tax references, neighbors and metro associations on paid plans. property_tax is a nullable area statistic with annual_median, currency and period: median annual tax payable on owner-occupied homes, adjusted to the final year of the period. It is not a rate or property bill. Unsupported, missing and censored estimates are null. Tax rates are percentages and alternative geographic references, not additive.
Inputs: code, country (optional), deep (optional), lang (optional)
phone
Reference
Parse 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), number
email
Reference
Check 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), email
ip
Reference
Look up an IPv4 or IPv6 address: country, continent, ASN and network.
Inputs and details
Paid deep adds location details when available, plus datacenter, relay, Tor and VPN flags.
Inputs: deep (optional), ip, lang (optional)
address
Reference
Look 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)
point
Reference
Find the country, state, district and timezone at coordinates.
Inputs and details
Deep adds terrain elevation and a compact nearest-city summary, included on every plan.
Inputs: deep (optional), lang (optional), lat, lon
currency_rate
Reference
Reference exchange rate between two currencies.
Inputs and details
Pass date for a past business day, amount to convert.
Inputs: amount (optional), base, date (optional), quote
time
Reference
Current local time, Unix seconds, exact offset and DST.
Inputs and details
Use an IANA zone, both coordinates, or one explicit IP, city, country, airport, port or address selector. Omit all for UTC. Ambiguous or missing locations return null clock fields with location candidates; never choose a candidate for the user. to or targets converts one instant. Deep adds rule edition, wall-time resolution, standard/seasonal offsets and actual DST-season transitions on every plan.
Inputs: address (optional), at (optional), city (optional), country (optional), deep (optional), disambiguation (optional), iata (optional), icao (optional), ip (optional), lang (optional), lat (optional), lon (optional), state (optional), targets (optional), timezone (optional), to (optional), unlocode (optional)

Get unstuck.

A few things worth knowing.

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.

I want to disconnect a client

Revoke its connection in AI setup. A revoked connection can take up to 10 minutes to stop working. For a setup using your own API key, revoke that key in Keys.

Building with an agent? Integration guide · SDKs

Source · Cursor directory · Email

Good reasoning starts with the right inputs.

From a problem to a next step.

Check the address with Email.

Give the customer a useful next step.

Inspect its DNS and mail routing together.

Narrow the investigation.

Inspect Email, then build around its response.

Put the explanation in the form.

Bring it to the AI you use.

Cursor

VS Code

Claude

Claude Code

ChatGPT

Other clients

Same API. Same plan.

More ways to put it to work.

Find out where mail should go.

Keep the rate with the result.

Get everyone on the same clock.

Spot a holiday before you pick a date.

Turn a partial address into choices.

Make phone fields consistent.

See where a domain points.

Put an IP address in context.

Give coordinates some context.

Find a business category that fits.

Turn a VIN into a useful record.

Catch bank-detail input mistakes.

Find the check your task needs.

postal

phone

email

ip

address

point

currency_rate

time

Get unstuck.