x402 on Paygentic — Paygentic.market

Where Paygentic stands with x402

Paygentic is a frontier platform built on the AIERC standard and the Chaingentic blockchain. AIERC is an intelligent constraint and reasoning layer for human and agentic value movement across all EVM networks. Before value moves, AIERC determines the reputation and ability of the wallets, and the suitability, intent, and security of the transaction.

x402 names a network by its chain id. Any EVM network is an x402 network the moment a facilitator settles payments on it and a USDC-style asset with a signed-transfer function exists there. Three things follow from that, and all three are live on the testnet.

1. Chaingentic is an x402 network

Our facilitator settles x402 payments on Chaingentic Testnet, in a USDC-faithful test asset that lives on our chain. The Chaingentic blockchain is the native settlement layer for transactions on its own network, where it records both the transaction and the related AIERC intelligence activity. On Chaingentic, AIERC sits in the block-assembly step: a transaction awaiting a determination is set aside on its own, the chain keeps building without it, and the answer comes back before the block is sealed. An x402 payment settled here gets that pause with nothing extra from anyone.

2. Our facilitator serves the other EVM networks

The same facilitator settles on Base Sepolia and can settle on any EVM network with a signed-transfer asset. For transactions on other EVM networks, settlement remains on the external chain, which produces its own transaction ID. The AIERC determination runs inside the facilitator, before the transfer is submitted, so a payment that does not qualify is never sent. The resulting AI activity is documented on the Chaingentic blockchain through an ITXID, or intelligence transaction ID, creating a verifiable intelligence record associated with the external transaction.

3. Anyone's server can carry the record

A service that sells over x402 through some other facilitator can still attach an AIERC determination record to its payment response. That extension is written and running on our own routes; it is what we bring to the x402 Foundation's process, after the two things above, which need nobody's permission.

What is live today

Piece	Where	What it does
Our facilitator	facilitator.aierc.tech	Verify, then an AIERC determination, then settle. Networks it settles on, Chaingentic first: /supported.
What Paygentic sells over x402	api.paygentic.online/.well-known/x402	The machine-readable list of every paid determination and its price. Each price is read from the same table the payment lane charges from.
The payment challenge	Any paid route on api.paygentic.online	A request without payment gets a 402 with one entry per network, Chaingentic first. Pay on whichever network your wallet holds funds on.
The record	testnet.chaingenticscan.com/ai-activity	Every settled payment leaves an AI-activity record on Chaingentic, whichever network the money moved on.

What one payment looks like

Ask. Your agent requests the resource. The answer is a 402 with the price, the asset and the recipient for each network we accept.
Sign. The agent's wallet signs a transfer authorisation off-chain. It pays no gas; the facilitator submits the transfer.
Verify. The facilitator checks the signature, the recipient, the amount, the window and the balance.
Determine. AIERC evaluates the payment: the wallets' reputation and ability, and the payment's suitability, intent and security. Grey signals go to AI CONSENSUS. The answer is CLEAN or FLAGGED, with the facts.
Settle. A CLEAN payment settles and the resource is delivered. The receipt carries the verdict, the transaction and the record.

Who decides on a FLAGGED payment, or when the evaluation is unavailable

Users can choose the level of oversight applied to their agents. In approval mode, the user retains the final decision, guided by AIERC's analysis. In autonomous mode, AIERC's settlement admissibility standards are enforced directly, allowing suitable transactions to proceed and blocking those that do not qualify.

The same two settings govern an x402 payment, and they are the payer's own, signed by the payer's wallet on the Transaction Dash:

FLAGGED. Your block setting decides. Block, the default, stops the payment. Communicate shows you the facts and lets you sign a short-lived decision to proceed; only your wallet can sign it, only for that exact payment and those exact facts, and it expires in five minutes.
Evaluation unavailable. If a required AI CONSENSUS evaluation could not be completed, nothing settles on its own. With sign-off on, you are shown the outage and may sign a separate short-lived decision to proceed. With sign-off off, the wallet runs autonomously, and an autonomous payment has no path through an outage: it waits until the evaluation is back.

Nothing a request carries can change which setting applies. A bare header is not authority.

What this page does not claim

Everything on this page runs on testnets: Chaingentic Testnet and Base Sepolia, in test assets. Nothing has been filed with the x402 Foundation yet. Nothing here is card compliance, tax compliance or legal advice. A determination tells you what was found; a signed record proves who said it and that it was not altered, not that a location claim or a tax classification is true.

Paygentic is a frontier platform built on the AIERC standard and the Chaingentic blockchain. Before value moves, AIERC determines the reputation and ability of the wallets, and the suitability, intent, and security of the transaction.