true402 LLM RouterGET /api/v1/chat/completions · x402 API by true402.dev
OpenAI-compatible LLM inference across many models. Pay-per-token in USDC on Base, no API key.
What does this x402 API do?
true402 LLM Router. This is an x402-gated GET API resource from true402.dev. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-04. The listing records The registry reports a $0 published price on Base. No settled paid call has been verified.
- Published price
- The registry reports a $0 published price
- Networks
- Base
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-04
- Resource ID
- 1c6a64e61d7a7167cf9a4697
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://true402.dev/api/v1/chat/completions", {
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://true402.dev/ returned 200.
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: healthy.
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 The registry reports a $0 published price. Raw protocol requirements remain visible below for implementation and audit use.