The facilitator endpoint is currently hardcoded to x402.org in the serverless and agentic flows. With the x402 ecosystem now listing 27+ facilitators on x402.org/ecosystem, it would be useful to make this configurable — e.g., via an env variable like FACILITATOR_URL in the .env files.
This would let users:
- Test against different facilitators without code changes
- Use mainnet-capable facilitators (x402.org is testnet-only)
- Choose facilitators optimized for their use case (latency, gas sponsorship, network support, etc.)
Happy to contribute a PR if there's interest.
The facilitator endpoint is currently hardcoded to
x402.orgin the serverless and agentic flows. With the x402 ecosystem now listing 27+ facilitators on x402.org/ecosystem, it would be useful to make this configurable — e.g., via an env variable likeFACILITATOR_URLin the.envfiles.This would let users:
Happy to contribute a PR if there's interest.