Directory / encoding.openverbs.com
Decode 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.
# 1. Ask the endpoint what it costs (no payment, no wallet needed): curl -i -X GET 'https://encoding.openverbs.com/v1/transcode' # -> HTTP/1.1 402 Payment Required # the response carries the price, asset and pay-to address. # 2. Pay and retry with any x402 client: npx x402-fetch 'https://encoding.openverbs.com/v1/transcode'
Endpoint: https://encoding.openverbs.com/v1/transcode. Operated by encoding.openverbs.com, not by Animica. Price and availability were correct at the last probe on 2026-10-01 and are set by the operator, who may change them.
Guess the character set of a base64-encoded byte buffer: sniffs a byte-order mark, then falls back to ASCII / UTF-8 validation and a UTF-16 NUL-pattern heuristi…
Break a string into its Unicode code points, each with its U+ notation, decimal value and UTF-8 / UTF-16 byte layout, plus total byte lengths.
Apply a Unicode normalisation form (NFC, NFD, NFKC or NFKD) to a string. Reports whether the text changed and its length in UTF-16 code units and code points.