Bring your AI agent, app, API or payment facilitator to X402blockchains. Projects on Base, Solana, BNB Chain and other networks can apply.
No command line is needed. You can prepare your proposal in your browser.
- Fill in your details. Click “Submit your project”. Change
YOUR-PROJECT.mdto your project name, for examplemy-agent.md, and complete the short template. - Send a pull request. Click GitHub’s green button to save your proposal. If GitHub offers to fork the repository, continue with that option. Then click Create pull request. Give it a title such as
List My Agent. - Wait for review. We check the project and reply on your pull request if anything is missing. You can edit the same proposal to provide updates.
Using the website application too? Copy your pull-request link and paste it into your website application. Both should describe the same project. A submitted form or pull request does not automatically publish a listing.
| Every project | Only when applicable |
|---|---|
| Project name and a short description | App contracts, program IDs or receiving wallets, with network names |
| Official website and a working logo | Public activity or analytics links |
| Documentation or a getting-started page | Paid API endpoints and a successful payment link |
| Supported networks and a public support channel | Facilitator details for products that use x402 payments |
| A public link showing you represent the project | A website application reference or related issue |
An agent does not need to accept payments to apply. Write Not applicable in the payment section if it does not. Missing activity data is not zero usage: transaction and wallet figures appear only after a reliable feed is connected.
Include your public facilitator URL, supported/verify/settle URLs, supported networks and chain identifiers, x402 versions/schemes, token contracts/mints and decimals, and signer/relayer or router addresses. Separate these from merchant receiving wallets. Provide successful settlement explorer links for each network and a public ownership reference. Deployment blocks/slots and the first settlement date help us review historical coverage.
You can also open a facilitator question. For the website’s pull-request listing flow, add the proposal PR link to your application.
Proposal → checks and any corrections → approval → integration and publication.
These are manual steps. Merging a proposal does not automatically deploy the website, start an indexer or verify every historical transaction. Approval is not a security audit, endorsement or a guarantee of listing or review time. Paid promotion does not replace listing review.
For corrections, update your open proposal or submit a new PR referencing the existing listing. Keep public facts and source links current. Never invent transaction counts or user numbers.
Keep credentials and private details out of GitHub. Do not publish passwords, API keys, private keys, signed payment authorizations or private contact details. The website’s private contact email and submission access key do not belong in a proposal.