x4PayAPI Market

Email and identity verification APIs for AI agents

Email and identity verification APIs let an agent check an address, a phone number or an identity claim before it sends, pays or creates a record. The rule looks at Verification, Data, Tools and Intelligence. The name has to say email, phone, identity or KYC, or the text has to use a phrase such as email verification, email validation, phone validation, identity verification or disposable email. A passing mention of a contact form is not enough. Discovery is free. The check itself is a paid call to the provider over x402, in USDC on Base, Solana or Algorand, with no API key. Settlement-verified means a paid route with an on-chain receipt, and that is what the examples are. Unclaimed (bazaar) imports are shown with their label and are not the examples. If you operate one of these checks, listing is free and you keep 100% of each settled call. The counts are the live number of APIs and endpoints that match the rule.

30 APIs and 521 endpoints match this page. 30 are settlement-verified: a paid route with an on-chain receipt.

Settlement-verified examples

Unclaimed (bazaar) imports

These rows were imported and the provider has not claimed them. They are not the examples above.

Related pages

Questions

Which verification APIs are on this page?

Those in Verification, Data, Tools or Intelligence whose name says email, phone, identity or KYC, or whose text says email verification, email validation, phone validation, phone verification, identity verification or disposable email.

How does the agent pay for an email or phone check?

It calls the provider, receives HTTP 402, and pays in USDC on Base, Solana or Algorand over x402. There is no API key. The PayAPI Market catalogue does not charge for the lookup.

What does the receipt prove?

That PayAPI Market paid that route and recorded the on-chain USDC transfer. Settlement-verified means a paid route with an on-chain receipt. It does not verify every other route on the listing.