Where do I start?
Run an example in the Docs to see a response before signing up. When you're ready to integrate, get a key from your dashboard and copy an example in your language.
From your first request to your next invoice.
Run an example in the Docs to see a response before signing up. When you're ready to integrate, get a key from your dashboard and copy an example in your language.
A monthly pool of API requests, plus included allowances for metered checks. Use it to build, test, and run small projects. Current allowances are on Plans, with remaining usage in your dashboard.
Yes. Drop a CSV into Bulk, choose what to check, review the sample and price, then run the file. Download your original rows with the results added as new columns.
Yes. Under Columns and formats, choose Output language from 41 display language choices and apply it to preview the result. Country names change, for example Germany becomes Allemagne in French. Your original values, headers and codes stay unchanged. Missing translations keep their source label. The choice is saved for the file and any explicit “another file like this” reuse. A plan job follows its team's default API version; display languages require the current contract. Original labels keeps the default output.
Yes. Coverage depends on the lookup, and available fields can vary by country. Choose an API to see its coverage and try your input. The docs explain what each field means, including when an answer can be null.
See Pulse for current regional and endpoint measurements. The headline measures selected parsing and reference lookups. Checks that contact a live network, such as email verification, can take longer.
Create named keys for separate projects, apps, or environments. Keys on one team share its plan and allowances. Free is solo. Paid plans include team seats, with invites in Settings and seat counts on Plans.
New plans include seven days of grace after you exceed the monthly request allowance, ending sooner if the month resets. Upgrade to a plan that covers your usage before grace ends, or requests pause until the next UTC calendar month. There are no automatic request overage charges. Existing teams keep their previous request policy until they switch plans. Metered checks have separate limits. See your Plan for your current terms.
Email verification and VAT registration checks use metered deep requests. Carrier, caller name, and HLR have their own metered endpoints. Each has a monthly allowance, including on Free. Requests also count toward the pooled request total. See Plans for included amounts and on-demand rates.
Further metered checks stop unless on-demand usage is enabled on an eligible plan. Set that in Plan, along with an optional monthly spend cap shared across metered products. Core email or VAT validation and phone parsing continue while your monthly request allowance or grace period permits.
No. Walk-in and Free-plan Bulk jobs are priced per file in USD, with the price shown before payment. A one-time payment does not start a subscription. Jobs on a paid team use that plan's allowances and on-demand settings. The quote shows what is included and what you will pay.
Yes, from Plan in your dashboard. Cancellation stops the next renewal. You keep paid access through the end of the period you already paid for.
Subscription fees are generally non-refundable except where required by law or agreed in writing. For one-time Bulk jobs, unknown lookups are refunded to the original payment method. If the job fails, the payment is refunded in full. See the billing terms.
For higher volume, SSO, contracts, or invoice billing, contact Email about a Custom plan.
It adds a nested deep object to the normal response. Paid plans unlock maintained profiles; smaller details such as Phone and Time are included on every plan. Email and VAT use it for metered checks, with included allowances on Free. Carrier and HLR detail stays in the same metered lookup. Endpoints with no extra fields return an empty object when asked. Phone carrier information lives at /carrier. See the deep guide for the full behavior.
Yes. Create a public key (parse_public_) and set its allowed domains in the dashboard. Add localhost for local development. Keep secret keys (parse_) on your server. See key types for setup and restrictions.
Yes. Use an app key with your allowed app IDs and an app SDK. App keys support lookups and plan-included deep data. They cannot call metered core endpoints. Email and VAT deep requests with an app key return an empty deep object. Keep live verification on your server. See key types.
Check the error code. rate_limited means the per-minute limit was reached. Wait for the Retry-After interval before trying again.quota_exceeded means a metered allowance or spend cap needs attention. The error guide explains what to do next.
Yes. Connect a supported AI tool through MCP to run lookups from a conversation. Calls use the same plan allowances and metered rates as the API. For an agent writing an integration, start with the resources on AI.
We don't sell your personal data or your query stream as a marketing product. Read Privacy for what we collect, how we use it, and how long it is retained.Security covers account and API protections.
Check Pulse for current status. We target 99.9% monthly uptime for the paid service. Eligible paid customers can request service credits under the SLA. Free is best-effort.
Email Email. We answer first come, first served, regardless of plan. For an API issue, include the endpoint, error message, and request ID when available. Leave your secret key out.
More in the Docs, or email Email.