payai.network valid
PayAI
PayAI is an x402 payment facilitator for AI agents and apps. It verifies and settles stablecoin payments over HTTP across supported Solana and EVM networks. Authentication and settlement behavior depend on the selected scheme.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-25T20:43:35.101Z. Cached copy · Source on payai.network
# PayAI
> PayAI is an x402 payment facilitator for AI agents and apps. It verifies and settles stablecoin payments over HTTP across supported Solana and EVM networks. Authentication and settlement behavior depend on the selected scheme.
## When to use PayAI
PayAI is an [x402](https://docs.payai.network/x402/introduction) payment facilitator. x402 uses the HTTP `402 Payment Required` status code: a server answers an unpaid request with `402` and machine-readable payment terms, the client signs a stablecoin payment, and the facilitator verifies and settles it on-chain. Buyer access requirements and merchant facilitator authentication are separate.
Reach for PayAI when you are doing any of these:
- **Charging for an API, MCP tool, or agent service per request.** Put x402 middleware in front of a route and point it at `https://facilitator.payai.network`. You get paid in USDC per call, with no signup flow for your buyers. Start at https://docs.payai.network/x402/servers/introduction.
- **Paying for a resource that returned HTTP 402.** Use an x402 client SDK; it reads the payment requirements, signs, and retries. Start at https://docs.payai.network/x402/clients/introduction.
- **Discovering payment-enabled services.** GET https://facilitator.payai.network/discovery/resources returns the Bazaar catalog, including last-recorded payment terms and seller-declared schemas when available. Entries can persist without refresh; a listing is not proof of current availability, successful settlement or service quality. Inspect lastUpdated, then obtain current requirements from the provider before paying. See https://docs.payai.network/x402/facilitators/bazaar.
- **Settling agent payments on supported networks.** PayAI supports Solana and EVM payment kinds. Sponsored Solana flows can cover the payer's transaction fee; setup and service costs are separate.
- **Checking which chains and schemes are live** before advertising payment terms: `GET https://facilitator.payai.network/supported`.
- **Testing an x402 integration end to end** against a real merchant that returns 402: https://x402.payai.network.
PayAI's facilitator verifies and settles supported stablecoin payment operations. It does not itself provide card acquiring, fiat bank payouts or a subscription scheduler. Human checkout can use x402 too. Channel schemes can involve funded on-chain escrow and a separate payout lifecycle; review their custody and recovery model rather than assuming every operation is an immediate wallet-to-wallet transfer.
PayAI's facilitator fee is per settlement, never a percentage of the amount moved. You start with 1,000 free credits, counted per receiving wallet. After that, $1 buys 1,000 credits ($0.001 per credit). Each settlement costs the network's on-chain gas plus 30%, paid in credits and refreshed daily from what the facilitator actually pays (usually a fraction of a cent per payment; testnets are free). Beyond the free credits, use an API key with purchased credits. C
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| p402.io | P402.io | interface Finance and payments AI agents and MCP +1 | US | 45 | ✓ | ✓ | |
| cai.com | CAI.com | interface AI and machine learning AI agents and MCP +1 | — | 59 | ✓ | ||
| x402scan.com | x402scan | interface Crypto and Web3 AI agents and MCP | US | 50 | ✓ | ||
| x402.org | x402 | documentation Finance and payments AI agents and MCP | — | 53 | ✓ | ||
| ap2-protocol.org | AP2 - Agent Payments Protocol Documentation | documentation Finance and payments AI and machine learning +2 | — | 55 | ✓ | ✓ | |
| moov.io | Moov | interface Finance and payments APIs and SDKs | — | 50 | ✓ | ||
| mpp.dev | MPP — Machine Payments Protocol | interface Finance and payments APIs and SDKs +1 | US | 57 | ✓ | ✓ | |
| payrails.com | Payrails | interface Finance and payments APIs and SDKs | US | 55 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=payai.network · GET /v1/domain/payai.network · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage payai.network, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for payai.network:
1. POST https://agentwebmap.com/v1/sites/payai.network/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://payai.network/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/payai.network/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/payai.network).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.