x402 List

x402 Protocol Service Directory

Update listing: XRPL Microstructure

Owners can update the declarative metadata of their listing: name, description, website, category, contact email, new endpoint paths, base URL. Measured data (uptime, verification, pricing, status) always comes from our monitor and cannot be edited by anyone.

How it works: submit your changes below, publish the one-time token we give you at https://data.tg-lw.com/.well-known/x402list.txt, hit verify, then we review manually and email you the outcome. The token expires in 72 hours. Back to the listing.

To request delisting, email info@x402-list.com or update your listing at /services/xrpl-microstructure/update.

PROPOSED CHANGES

Fields are prefilled with the live listing. Only what you actually change is submitted.

Used for the review outcome notification. One update request per service per email every 7 days. If a request is rejected, a corrected one can be sent right away.

Changing the base URL is an identity change (slug and monitor history are tied to it) and gets extra scrutiny in review. The ownership proof is always checked on the CURRENT domain shown above.

The listing's owner contact, never displayed publicly (including here). Leave empty to keep it unchanged; it can never be cleared from here.

  • GET /v1/chains
  • GET /v1/depth
  • GET /v1/issuer
  • GET /v1/lookalikes
  • GET /v1/makers
  • GET /v1/preflight
  • GET /v1/trustlines
  • GET /v1/vitals
  • GET /v1/x402

NEW x402-protected endpoints only, one per line. Prefix the method when it is not GET, as in POST /v1/chat/completions; a line with no prefix is taken as GET. GET and POST are the accepted methods. The same path with a different method is a separate endpoint, so it can be added even if it is already listed under the other one. They are probed for HTTP 402 with the declared method after ownership verification. Existing endpoints can be removed or change method below, with review.

Currently monitored endpoints to take off the listing, one per line, written exactly as listed above, as in POST /v1/chat/completions; a line with no prefix is taken as GET. The listing must keep at least one endpoint. Removed endpoints stop being monitored after review; their price history is kept.

One per line, as GET /v1/resource -> POST: the current method and path of a monitored endpoint, then the new method (GET or POST). After ownership verification the endpoint is probed with the new method, and the change is applied only if it answers with a valid x402 HTTP 402 there.

HOW IT WORKS

  1. 1. Submit proposed changes
  2. →
  3. 2. Publish the token at /.well-known/x402list.txt
  4. →
  5. 3. Automatic verification (+ HTTP 402 probe when endpoints change)
  6. →
  7. 4. Manual review & email outcome