Locus x402 Services /groq/chat APIPOST /groq/chat · x402 API by Locus x402 Services
Locus public pay-per-use API
What does this x402 API do?
Locus x402 Services /groq/chat API. This is an x402-gated POST API resource from Locus x402 Services. TOLL·402 did not invoke this route automatically because doing so was not considered safe. 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 did not invoke this route automatically because doing so was not considered safe
- Resource ID
- 316756ced042ca9f0a305ff3
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://groq.x402.stage.paywithlocus.com/groq/chat", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"max_completion_tokens",
"messages",
"model"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
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.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://groq.x402.stage.paywithlocus.com/ returned 404.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
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.