Name all three x402 facilitator options in the AI guide - #12
Merged
Merged
Conversation
The x402 section read as if the OpenZeppelin Relayer and the Coinbase facilitator were the only choices. x402 is permissionless: anyone can run a facilitator, and self-facilitating in your own process is a real option when you want no third-party dependency. Also drop the implication that the API key belongs to the protocol. It is the Relayer's requirement. The Coinbase facilitator needs none, and it serves testnet only, so point readers at /supported before mainnet.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the AI guide to present x402 facilitator selection accurately.
Changes:
- Describes the facilitator role generically.
- Lists hosted and self-hosted options with network, authentication, and fee details.
- Recommends checking
/supportedbefore deployment.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Contributor
Author
|
🤖 Automated message from Kaan's Automated Triage Bot. Thanks for the review. It's an overview with no change requests — no inline comments and no review threads on the diff — so there is nothing to fix here. I re-verified every claim the diff publishes against the x402 Facilitators section of the Stellar docs before merging:
Merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Automated message from Kaan's Automated Triage Bot.
The Stellar Dev Skill reworked its x402 guidance upstream. Its agentic-payments skill now treats the facilitator as a choice, not a fixed dependency, and says plainly that x402 is permissionless. See stellar/stellar-dev-skill commits 9562ecd, 1fa60ab and 8618973. This page still named only the two hosted facilitators, so I added the self-hosted option and moved the API key note onto the operator that requires it.
Changes in
building-with-ai/README.md:GET <facilitator-url>/supportedbefore mainnet.Verified against the x402 Facilitators section of the Stellar docs: the Relayer plugin serves testnet and mainnet with a Channels API key on both, and the Coinbase facilitator serves
stellar:testnetwith sponsored fees.Two other upstream changes landed but need nothing here. The smart-contracts skill moved
soroban-sdkoff a release candidate to stable 27 for mainnet protocol 27; this repo pins no SDK version. The MPP guide added that MPP is payment-method-agnostic; this repo only names MPP in feature lists and makes no claim that conflicts.