Inspect code points
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.
- Category
- Developer tools
- Starting price
- $0.002
- Paid calls · 30 days
- 12
- Unique payers · 30 days
- 12
Paid endpoints
4 endpoints, sorted by usage. Prices are per request.
- POST/v1/transcode
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.
$0.002Base3calls / 30d - POST/v1/inspect
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.
$0.002Base3calls / 30d - POST/v1/detect
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 heuristic. Returns a best-effort charset with a confidence label — a low-confidence guess is still a successful 200.
$0.002Base3calls / 30d - POST/v1/normalize
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.
$0.002Base3calls / 30d