#encoding

Morse code conversion as an API, computed locally and deterministically. The encode endpoint turns text into International Morse code, mapping A–Z, the digits 0–9 and common punctuation to dots and dashes, separating letters with a space and words with a slash, and listing any unsupported characters it skipped. The decode endpoint turns Morse code back into text, accepting word separators written as a slash, a pipe or a wide gap, and marking unrecognised symbols. The timing endpoint computes the PARIS-standard timing from a words-per-minute speed — the dot duration is 1200/WPM milliseconds, a dash is three dots, and the gaps are one, three and seven dot units for intra-character, inter-character and word spacing — and, given a Morse message, the total number of units and the transmission time. The word PARIS is exactly 50 units, which defines the WPM scale. Everything is computed locally and deterministically, so it is instant and private. Ideal for amateur-radio, aviation, education, accessibility, puzzle and game app developers, signalling and CW-training tools, and learning Morse. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Morse code; for Base64 and JWT use an encoding API and for Caesar and substitution ciphers a cipher API.

api.oanor.com/morse-api

Roman numeral conversion as an API, computed locally and deterministically. The encode endpoint turns an integer from 1 to 3999 into its Roman numeral using standard subtractive notation, so 1994 becomes MCMXCIV and 2024 becomes MMXXIV. The decode endpoint turns a Roman numeral back into an integer with strict validation — it rejects malformed forms such as IIII or VV and also returns the canonical way to write the same value, accepting any letter case. The arithmetic endpoint adds, subtracts or multiplies two values given as either integers or Roman numerals and returns the result as a Roman numeral and as an integer, provided the result stays within the classic 1–3999 range. The standard subtractive pairs are IV, IX, XL, XC, CD and CM. Everything is computed locally and deterministically, so it is instant and private. Ideal for typesetting, publishing, education, clock-face, game and document-processing app developers, numbering and chapter tools, and history teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Roman numeral conversion; for binary, octal and hexadecimal number-base conversion use a base-conversion API.

api.oanor.com/roman-api

Encode and decode MessagePack — the compact binary serialization format ("it's like JSON, but fast and small") used by Redis, Fluentd, many RPC systems and IoT protocols. The encode endpoint turns a JSON value into MessagePack bytes, automatically choosing the smallest representation for each integer, string, array and map; the decode endpoint parses MessagePack back into a JSON value. It implements the full spec — nil, booleans, every fixed and variable integer width, float32 and float64, str and bin, arrays and maps, and the ext family — and rejects trailing or truncated data rather than silently mangling it. Binary (bin) values and any non-UTF-8 string come back losslessly as a {"_bytes_hex":"…"} object, and ext values as {"_ext":{"type":N,"hex":"…"}}, so encode and decode round-trip exactly. Bytes are exchanged as both hex and base64 so they survive any transport. Everything is computed locally and deterministically, so it is instant and private. Ideal for debugging MessagePack payloads, bridging JSON and msgpack systems, RPC and cache tooling, IoT pipelines, and teaching the format. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is MessagePack specifically; for JSON, YAML, TOML or XML use those format APIs, for BitTorrent's Bencode use the Bencode API, and for base64, hex, URL or HTML encoding use a general encoding API.

api.oanor.com/msgpack-api

Encode and decode Base45 (RFC 9285) — the compact binary-to-text encoding designed to pack densely into the alphanumeric mode of QR codes, best known as the carrier for the EU Digital COVID Certificate. The encode endpoint turns text (UTF-8) or raw bytes given as hex into a Base45 string; the decode endpoint turns a Base45 string back into bytes, returned as hex and — when the bytes are valid UTF-8 — as text. It uses the official 45-character alphabet (0-9, A-Z and a handful of symbols), packs two bytes into three characters (or one byte into two), and validates length and value ranges strictly so malformed input is rejected rather than silently mangled. Everything is computed locally and deterministically, so it is instant and private. Ideal for QR-code payloads, digital health and travel certificates, alphanumeric-mode encoders, and any binary data that must survive an uppercase-only channel. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Base45 specifically; for base64, base32, hex, URL or HTML entity encoding use a general encoding API.

api.oanor.com/base45-api

The email and MIME text encodings that general base64/hex toolkits leave out. The quoted-printable endpoint encodes and decodes Quoted-Printable (RFC 2045) — the Content-Transfer-Encoding that keeps mostly-ASCII text readable while escaping everything else as =XX hex, with the soft line-wrapping at 76 columns and trailing-whitespace handling the spec requires. The encoded-word endpoint encodes and decodes RFC 2047 encoded-words — the =?UTF-8?Q?…?= and =?UTF-8?B?…?= form used to carry non-ASCII text in email Subject, From, To and other headers — in either the Q (quoted-printable-style) or B (base64) variant, and decodes any mix of them back to plain text. Everything is UTF-8 and computed locally and deterministically, so it is instant and private. Ideal for building and parsing email (SMTP/IMAP), .eml and MIME tooling, newsletter and transactional-mail systems, and migrating legacy mail data. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. These are the MIME-specific encodings; for base64, base32, hex, URL and HTML entity encoding use a general encoding API.

api.oanor.com/mimeencode-api

Produce a canonical hex dump of any input and parse a hex dump back into bytes. The dump endpoint formats data the way hexdump -C and xxd do — an offset column, the bytes in hex (grouped in eights), and a printable-ASCII gutter — with a configurable number of bytes per line and optional uppercase. Feed text as UTF-8, or binary as hex or base64. The parse endpoint reverses any hex dump — tolerating offset columns and ASCII gutters, or a plain run of hex — and returns the reconstructed bytes as hex, base64 and (when printable) text. Perfect for inspecting binary payloads, debugging protocols and file formats, diffing buffers and teaching. Pure local computation — no key, no third-party service, instant; up to 1 MB via POST. Live, nothing stored. 3 endpoints. Distinct from a plain base64/hex encoder.

api.oanor.com/hexdump-api

Encode content into a data: URI and decode a data: URI back to its content (RFC 2397). data: URIs inline a file directly into HTML, CSS, JSON or email — perfect for small images, SVG, fonts and icons that you want to embed without a separate HTTP request. The encode endpoint wraps your content (given as UTF-8 text, base64 or hex for binary) with a chosen media type and charset, in either base64 or URL (percent) encoding; the decode endpoint parses any data: URI and returns its media type, charset, whether it was base64, the byte size, and the payload as text and/or base64. Pure local computation — no key, no third-party service, instant; up to 4 MB via POST. Live, nothing stored. 3 endpoints. Distinct from a plain base64/hex encoder and from SVG-specific tooling.

api.oanor.com/dataurl-api

Parse and build URL query strings — with full support for nested objects and arrays. Turn a query string like a[b][c]=1&tags[]=x&tags[]=y into a clean nested JSON object, and turn any JSON object back into a properly-encoded query string. Choose how arrays are serialised (indices, brackets, repeated keys or comma-separated) and whether to URL-encode. Far beyond a flat key=value encoder — it handles the deep structures real web frameworks (Rails, PHP, Express/qs) use. Pure local processing — no key, no third-party service, instant. Live. 3 endpoints. Built for API request construction, parsing complex links and redirects, form-encoded bodies and webhook payloads.

api.oanor.com/querystring-api

Turn sequential integer IDs into short, unique, non-sequential strings — and back again. Encode one or more non-negative integers (or a hex string such as a Mongo ObjectId) into a compact YouTube-style id like "vbYCZIYD", then decode it to recover the exact original values. Add a salt so your ids are unique to your application, set a minimum length, or supply a custom alphabet. It is reversible obfuscation (not encryption): perfect for hiding row ids in public URLs, building short links, and avoiding leaking how many records you have. Pure local computation — no key, no third-party service, nothing stored. Stateless: decode with the same salt/min-length/alphabet you encoded with. Live. 5 endpoints. Distinct from UUID generation, base conversion and snowflake decoding.

api.oanor.com/hashids-api

A fast, fully-local encoding toolkit: encode and decode text between base64, base64url, base32 (RFC 4648), hex, URL percent-encoding, HTML entities, binary and ASCII85 — plus JWT inspection (decode header and payload without verifying the signature). Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for developer tools, webhooks, data pipelines, debugging and integrations.

api.oanor.com/encoding-api