Reference & Lookup Data · Integration
Xverify
Add Xverify to your product for your customers, and give your AI agents governed access to it.
Xverify checks contact details against the real world before you rely on them. An email address is tested at the receiving server rather than by pattern matching, a phone number is checked for validity and line type, a postal address is standardised and confirmed, and all three can be asked in a single call, which is what makes it useful on a signup form where somebody is typing all three at once. Everything here is a read. There is nothing to write back and nothing that will notify you later, so the design questions are whose account a check is billed to and how long an answer stays good. Checking is metered per record, which is precisely why each customer connects their own account rather than drawing on yours, and answers should be cached per tenant for a window matching how fast that kind of detail really changes. fastn keeps each account's key per tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer connect their own Xverify account so every check is metered against the tenant whose data is being cleaned.
Validate an email, phone number and postal address in one call while the person is still on the form to fix a typo.
Clean an imported list before it is used, rather than discovering the bad records when a send bounces.
Cache an answer per record, since the same address checked twice in a week does not need paying for twice.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks a batch of contact details and reports which would fail if used today.
An agent explains why a particular address was rejected rather than only reporting that it was.
An agent recommends which imported records are worth keeping and which should be dropped before anyone relies on them.
Example prompt
Check these signups in Xverify and tell me which emails and phone numbers are not real.
Set up Xverify in 4 steps
- 01Enable the Xverify connector in your fastn dashboard.
- 02Have each customer supply their own Xverify key, so verification volume is billed to them rather than to you.
- 03Decide which fields get checked and at what moment, and set a cache window per record type.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Xverify integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Xverify integration without building it. Your customers connect their own Xverify account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Xverify update is not your on-call problem.
- One integration serves your product and your agents. The same governed Xverify connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
NeverBounce
Validity
ClearbitOften used alongside
Tools the same teams tend to run next to Xverify, across other categories.
Salesforce
HubSpot
Notion
SnowflakeXverify integration FAQ
How do I add an Xverify integration to my product?
Enable the Xverify connector in your fastn dashboard, then let each customer authenticate their own Xverify account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Xverify client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Xverify account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Xverify account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Xverify integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks a batch of contact details and reports which would fail if used today.
Who maintains the Xverify integration?
fastn does. When Xverify changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does an Xverify lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Xverify results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Xverify is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Xverify integration?
A common starting point: have each customer connect their own Xverify account so every check is metered against the tenant whose data is being cleaned. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Xverify integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Xverify does not change your per-connector cost. You can start free with 3 connected accounts.
Add Xverify to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.