Discover / encoding.openverbs.com
Transcode between character sets
■ Challenge detectedDecode a base64 byte buffer from one character set and re-encode it into another (utf-8, utf-16le, utf-16be, latin1, ascii). Characters that the target set cannot represent, or bytes invalid for the source set, are clean 400s.
- Listed price
- $0.002
- Challenge detected
- 1 of the last check
- Median response
- 346 ms
- Last checked
- 14 Oct, 21:21 UTC
- In our index since
- 14 Oct 2026
Endpoint
curl -i https://encoding.openverbs.com/v1/transcode # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/encoding.openverbs.com
Recent checks
All 1 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 14 Oct, 21:21 UTC | Challenge detected | 402 | 346ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 14 Oct, 21:21 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.
What price is recorded for Transcode between character sets?
Its listed price is $0.002.
What payment terms does Transcode between character sets advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Where is Transcode between character sets listed?
In x402 Bazaar. Superstables first indexed it on 14 Oct 2026.
Something wrong on this page? Tell us.