#binary

Bit-level integer maths as an API, at 8-, 16-, 32- or 64-bit width with exact big-integer arithmetic. The inspect endpoint takes a number (decimal, 0x hex, 0b binary or 0o octal) and returns its decimal, signed (two's-complement), hexadecimal, binary and octal forms, plus the population count (Hamming weight), parity, leading and trailing zero counts, whether it is a power of two, its bit-reversed value and its byte-swapped (endianness) value. The ops endpoint performs a bitwise operation — AND, OR, XOR, NAND, NOR, XNOR, NOT, logical and arithmetic shifts (shl, shr, sar) and rotations (rol, ror) — masked to the chosen width. The bit endpoint sets, clears, toggles or tests an individual bit by index. Everything is computed locally and deterministically, so it is instant and private. Ideal for embedded and systems programming, network-protocol and flag handling, graphics and hashing, emulators and reverse engineering, and teaching binary. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is bit manipulation; for base 2-36 conversion use a base-convert API and for IEEE-754 floating-point bits use a floating-point API.

api.oanor.com/bitwise-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

Inspect and build IEEE 754 floating-point numbers — see exactly how a number is stored in the bits. The encode endpoint takes a number and decomposes its single (32-bit) or double (64-bit) representation into the sign bit, the raw and unbiased exponent, the mantissa, the full binary layout split into sign / exponent / mantissa, the hexadecimal word, and a classification (normal, subnormal, zero, infinity or NaN); for single precision it also returns the actual value after rounding, so you can see floating-point error directly. The decode endpoint goes the other way — give it a hex word or a 32-/64-bit binary string and it returns the number it represents along with the same field breakdown. It accepts inf, -inf and nan, and lays bytes out big-endian. Everything is computed locally and deterministically, so it is instant and exact. Ideal for systems and embedded programming, teaching how floats work, debugging precision and rounding bugs, binary protocols and file formats, and interview prep. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This inspects floating-point bits; for integer base conversion use a base-convert API.

api.oanor.com/ieee754-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

Convert integers between any numeral systems with exact big-integer math. Pass a number and a from/to base (radix 2 to 36, arbitrarily large, signed) and the convert endpoint returns the result and the decimal value; common 0x, 0b and 0o prefixes are accepted when they match the base, and whitespace or underscores in the input are ignored. The bases endpoint shows a single number across binary, octal, decimal, hexadecimal, base32 and base36 at once, together with its bit length, byte length and sign. Everything is computed locally with BigInt, so values of any size are exact and deterministic. Ideal for low-level and embedded debugging, networking and bit-twiddling work, teaching number systems, and anywhere you juggle hex, binary and decimal. A numeral-base converter — distinct from the text-encoding toolkit (encoding: base64/base32/hex of bytes), the Elixir/Erlang Hex package registry (hex) and number-to-words (numberwords). No upstream key, no cache.

api.oanor.com/baseconvert-api