GEDX402 Knowledge: POST /v1/translate
M2M100 machine translation — one x402 payment on embed.gedx402.com. POST { text, source_lang, target_lang } → { translated_text }; wire settlement USDC per request (see npm run pricing:report) worst-case. Hero: GET /heroes/translate. Competitive discovery alongside embed ping; not in the five-step AOV ladder.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://embed.gedx402.com/v1/translate", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"source_lang",
"target_lang",
"text"
],
"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://embed.gedx402.com/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
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.