Add DPX to x402 ecosystem partners#169
Open
untitledfinancial wants to merge 2 commits into
Open
Conversation
DPX is an AI intelligence oracle and cross-border settlement rail that is x402-native. Uses x402 pay-per-call for its 10-layer Stability Oracle API (climate, macro, FX, ESG, supply chain data). Also runs USDC/EURC settlement on Base at 1.385% all-in via x402. Category: Services/Endpoints
🟡 Heimdall Review Status
|
|
Ran a no-payment discovery pass against the public DPX site in this PR. I did not send Repro: npx --yes x402-surface-check@0.2.30 https://mcp.untitledfinancial.com --limit 8 --origin https://mcp.untitledfinancial.com
curl -si https://mcp.untitledfinancial.com/x402
curl -si -X POST https://mcp.untitledfinancial.com/mcp \
-H 'Content-Type: application/json' \
-H 'Origin: https://mcp.untitledfinancial.com' \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'What looks good:
Patch notes before merge:
Net: the MCP endpoint and pricing catalog are visible, but fixing the discovery URL and production/sandbox boundary would make this much easier for agents and reviewers to validate. |
Author
|
All four issues resolved and deployed:
Discovery URL fixed — https://mcp.untitledfinancial.com/x402 (was https:/.untitledfinancial.com/mcp/x402)
Well-known paths — /.well-known/x402, /.well-known/x402.json, and /.well-known/agent.json all return 200
Sandbox flag clarified — root descriptor now has "sandbox": false + "settlement_sandbox": true (oracle/intelligence tools are live; only settlement execution is sandboxed pending USDC)
402 example — documented curl command in the descriptor
Do I need to resubmit?
… On May 16, 2026, at 6:26 PM, TateLyman ***@***.***> wrote:
TateLyman
left a comment
(coinbase/x402#169)
<#169 (comment)>
Ran a no-payment discovery pass against the public DPX site in this PR. I did not send X-PAYMENT, did not sign anything, and did not call the priced tools.
Repro:
npx --yes ***@***.*** https://mcp.untitledfinancial.com --limit 8 --origin https://mcp.untitledfinancial.com
curl -si https://mcp.untitledfinancial.com/x402
curl -si -X POST https://mcp.untitledfinancial.com/mcp \
-H 'Content-Type: application/json' \
-H 'Origin: https://mcp.untitledfinancial.com' \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
What looks good:
https://mcp.untitledfinancial.com/ returns a machine-readable MCP/x402 descriptor rather than a marketing page.
POST /mcp responds to MCP tools/list, and the browser-facing headers include Access-Control-Allow-Origin: *, X-PAYMENT, and X-PAYMENT-RESPONSE.
https://mcp.untitledfinancial.com/x402 exposes a per-tool pricing catalog with Base mainnet USDC (eip155:8453), a payee, and $0.0010 pricing for sampled tools.
Patch notes before merge:
The root descriptor's x402.discovery value appears malformed: https:/.untitledfinancial.com/mcp/x402. The live catalog I found is https://mcp.untitledfinancial.com/x402.
Common discovery paths return 404: /.well-known/x402, /.well-known/x402.json, /.well-known/agent.json, /openapi.json, and /llms.txt. If the ecosystem page expects agent-discoverable x402 metadata, I would either expose /.well-known/x402.json or make the metadata/descriptor point directly at /x402.
The PR description positions DPX as a Base mainnet settlement rail, while the root descriptor also says sandbox: true. I would clarify which parts are sandbox, which parts are production/mainnet, and whether the x402 catalog is for quote/oracle tools only or also for settlement execution.
Since billing appears MCP-tool scoped, I would add one documented no-payment tools/call example that should return a 402 before work. I intentionally did not call priced tools in this public pass, so I only verified discovery/tool listing and the pricing catalog.
Net: the MCP endpoint and pricing catalog are visible, but fixing the discovery URL and production/sandbox boundary would make this much easier for agents and reviewers to validate.
—
Reply to this email directly, view it on GitHub <#169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIAKD2ODQLV67MUCKSY2RRT43DTJJAVCNFSM6AAAAACZAYTBGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRYGQYDMNRYGI>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.
|
|
Rechecked the live DPX surface after your update. I still did not send Confirmed fixed:
Repro from this re-check: curl -si https://mcp.untitledfinancial.com/.well-known/x402
curl -si https://mcp.untitledfinancial.com/.well-known/x402.json
curl -si https://mcp.untitledfinancial.com/.well-known/agent.json
curl -si -X OPTIONS https://mcp.untitledfinancial.com/mcp \
-H 'Origin: https://mcp.untitledfinancial.com' \
-H 'Access-Control-Request-Method: POST' \
-H 'Access-Control-Request-Headers: content-type,x-payment'
curl -si -X POST https://mcp.untitledfinancial.com/mcp \
-H 'Content-Type: application/json' \
-H 'Origin: https://mcp.untitledfinancial.com' \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_macro_briefing","arguments":{}}}'From my side, I would not close/reopen or resubmit unless the Coinbase x402 maintainers specifically ask for it. The live public surface now addresses the external review notes; if anything, update the PR description/comment thread with the corrected discovery URL and sandbox clarification so reviewers do not have to infer it from comments. |
Author
Live surface update — all review notes addressedFollowing @TateLyman's discovery pass, four issues were identified and are now deployed to production: 1. Discovery URL corrected 2. Well-known paths added 3. Sandbox flag clarified 4. Documented 402 example No PR files changed — all fixes are live on the Cloudflare Worker at |
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
3 participants
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.
DPX is an AI intelligence oracle and cross-border settlement rail that is x402-native. Uses x402 pay-per-call for its 10-layer Stability Oracle API (climate, macro, FX, ESG, supply chain data). Also runs USDC/EURC settlement on Base at 1.385% all-in via x402.
Category: Services/Endpoints
Description
Tests
Checklist