Skip to content

docs(ecosystem): add Status column to the x402 facilitator table - #30

Open
eltociear wants to merge 1 commit into
BlockRunAI:mainfrom
eltociear:docs/facilitator-discovery-status
Open

docs(ecosystem): add Status column to the x402 facilitator table#30
eltociear wants to merge 1 commit into
BlockRunAI:mainfrom
eltociear:docs/facilitator-discovery-status

Conversation

@eltociear

Copy link
Copy Markdown

Two of the six discovery endpoints in the facilitator table are currently down, so the list reads as all-working when it is not. This adds a Status column (using the same ✅ Live convention as the API Products table above) plus a short dated note.

Verified 2026-08-02 with a GET on each discovery endpoint:

Facilitator Discovery endpoint Result
Coinbase CDP …/x402/discovery/resources ✅ resources returned
PayAI facilitator.payai.network/discovery/resources ✅ resources returned
QuestFlow facilitator.questflow.ai/discovery/resources ⚠️ HTTP 500 — not authorized on x402-prod to execute command aggregate: "discoverable_resources"
AnySpend mainnet.anyspend.com/x402/discovery/resources ✅ resources returned
AurraCloud x402-facilitator.aurracloud.com/discovery/resources ❌ does not resolve (its apex aurracloud.com does)
thirdweb …/payments/x402/discovery/resources ✅ resources returned

Only the two failing rows are flagged; the note is dated so it's clearly a point-in-time check. Happy to drop the inline note and keep just the column, or vice-versa, whichever you prefer.

Two of the six discovery endpoints listed are currently down: QuestFlow returns
HTTP 500 and AurraCloud does not resolve. Added a Status column (matching the
API Products table's convention) plus a dated verification note, so the discovery
list reflects which endpoints actually respond.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant