Submissions

Request an owner update to a listed service (F10)

Service owners propose changes to the DECLARATIVE metadata of their listing: name, description, website_url, category, contact_email, new endpoints (endpoints_add, each optionally prefixed with its HTTP method), the removal (endpoints_remove) or the method change (endpoints_method) of listed endpoints, and base_url (an identity change, reviewed with extra scrutiny). Measured fields (verified, uptime, pricing, status, payTo) are read-only for everyone and cannot be updated through this channel. All fields are compared server-side against the live listing and only actual changes are recorded; submitting with no effective change returns HTTP 400. The response contains a ONE-TIME ownership token (returned only once, never stored in clear): publish it as a line of a plain-text file at {base_url origin}/.well-known/x402list.txt on the CURRENTLY listed domain, then call verify-ownership. The token expires after 72 hours. After verification the request goes to manual review ALWAYS; the requester is notified by email of the outcome. Nothing about a pending request is public. Cooldown: one update request per (email, service) pair every 7 days (HTTP 429 with Retry-After). Only a live or approved request counts: a rejected request does not, so a corrected one can be sent immediately. A request already verified and under review for the same service blocks new ones (HTTP 409).

post/services/{slug}/request-update

Request

  • Base URL: https://x402-list.com/api/v1
  • URL: https://x402-list.com/api/v1/services/{slug}/request-update
  • Auth: none declared

Path parameters

slugstring required

Request body

emailstring email required

Requester email: receives the review outcome. Subject to the per-(email, service) 7-day cooldown

namestring

Proposed service name (the slug NEVER changes: citations and monitor history hang off it)

base_urlstring uri

Proposed base URL. Changing it is an identity change and is reviewed with extra scrutiny; the ownership proof is always checked on the CURRENT domain

website_urlstring uri

Proposed website URL (dev-tunnel domains are rejected; free hosting is allowed)

categorystring
descriptionstring
contact_emailstring email

Proposed owner contact email; empty string = keep unchanged

endpoints_addstring[]

NEW x402-protected endpoints to add, one per entry, as "/v1/resource" or "POST /v1/resource". GET and POST are the accepted methods (case-insensitive) and an entry with no method prefix is taken as GET. Method and path together identify an endpoint, so "POST /x" is a new addition even when "GET /x" is already listed; an entry already listed with the same method is silently ignored. Listed endpoints are removed or change method through endpoints_remove and endpoints_method. The endpoint is probed for HTTP 402 with the declared method after ownership verification. Also accepted as one newline-separated string.

Example request

{
  "endpoints_add": [
    "/v1/summarize",
    "POST /v1/chat/completions"
  ],
  "endpoints_remove": [
    "GET /v1/old"
  ],
  "endpoints_method": [
    "GET /v1/resource -> POST"
  ]
}

Response

Update request created, awaiting ownership verification

Example response

{
  "provenance": {
    "attribution": "Data: x402-list.com (CC BY 4.0)",
    "cite_as": "https://x402-list.com/services/acme-generate",
    "source": "https://x402-list.com"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.