https://x402.twit.sh/lists/by/idGET /lists/by/id · x402 API by x402
Retrieve details of a specific Twitter/X List by its numeric ID. Returns name, description, mode, member count, subscriber count, creation date, banner image, and owner profile. Query param: id (string, required) - numeric List ID, e.g. GET /lists/by/id?id=84839422. Returns X v2 API-compatible JSON.
What does this x402 API do?
https://x402.twit.sh/lists/by/id. This is an x402-gated GET API resource from x402. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-07-21
- Resource ID
- c4d718361ba735f81b93a09e
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402.twit.sh/lists/by/id", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://x402.twit.sh/ returned 402.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: degraded.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.