Skip to main content
You can point your resource server’s facilitatorClient at any facilitator that advertises the Hedera network you need. The options below support Hedera today.

​
Official x402 facilitator

The x402 project hosts a public facilitator at https://x402.org/facilitator for quickstart and testnet use. It requires no setup and no API key, and now advertises hedera:testnet alongside its other supported chains. You can confirm Hedera support live by querying its capabilities:
The response lists hedera:testnet among the supported kinds, along with the fee-payer account the facilitator will sponsor. This facilitator is aimed at quickstart and testnet; for Hedera mainnet, use a facilitator that advertises hedera:mainnet (such as Blocky402, below).
Point the facilitatorClient in your resource server at https://x402.org/facilitator to verify and settle Hedera testnet payments through the official x402 facilitator.

​
Blocky402

Blocky402 is an open x402 facilitator that supports Hedera on both testnet and mainnet, so you can wire up x402 payments on Hedera without standing up your own infrastructure first. Both facilitators are live with open access (no API key required). Both expose the standard endpoints (GET /supported, POST /verify, and POST /settle) and are documented at blocky402.com/docs (quickstart, API reference, networks). You can confirm Hedera support live by querying either facilitator’s capabilities:
The response lists the supported Hedera network among the kinds, along with the fee-payer account the facilitator will sponsor.
Point the facilitatorClient in your resource server at https://api.testnet.blocky402.com (testnet) or https://api.blocky402.com (mainnet) to verify and settle Hedera payments through Blocky402.

​
Run your own Hedera facilitator

x402 is permissionless: any team can operate a facilitator, and the more independent Hedera facilitators there are, the healthier the network. Below are the steps to follow to stand one up for yourself:
1

Implement the exact Hedera scheme

Use the @x402/hedera reference implementation and the scheme spec to handle verification and settlement.
2

Fund and configure a fee-payer account

Provision a Hedera account that will act as the feePayer, sponsoring network fees and submitting transactions on behalf of clients.
3

Expose the standard endpoints

Serve GET /supported, POST /verify, and POST /settle. Advertise hedera:mainnet and/or hedera:testnet (and your fee-payer account) from /supported so clients can discover you.
4

Enforce the safety checks

Validate transaction layout, asset and amount exactness, fee-payer safety, and replay protection exactly as the spec requires, and publish your alias-handling policy.

​
Get listed as a Hedera facilitator

Once your facilitator is live and supports Hedera:
  • Be discoverable across the ecosystem by listing in the broader x402 directories such as the x402 ecosystem directory and x402scan facilitators.
  • Be listed here as a Hedera facilitator by opening a pull request against the Hedera docs repository that adds your facilitator (base URL, supported Hedera networks, fee-payer account, and documentation link) to this page.