oanor
Sign up free
Marketplace Pricing Features Sign in

API · /msgpack-api

MessagePack API

healthy 3,183 Subscribers

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.

#msgpack #messagepack #serialization #binary #encoding #developer-tools
api.oanor.com/msgpack-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/msgpack-api/openapi.json
/api/msgpack-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
85 ms
Server probes · 24h
Subscribers
3,183
active
Total calls
39
last 7 days
status Full status page → · 9 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 5,435 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 5,435 calls/month
  • 2 req/sec
  • Encode + decode
  • No credit card
Sign in to subscribe

Starter

€6.95 /month

  • 14,950 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 14.95k calls/month
  • 8 req/sec
  • Full spec incl. bin/ext
  • Email support
Sign in to subscribe

Pro

€26.85 /month

  • 200,500 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 200.5k calls/month
  • 20 req/sec
  • RPC / cache / IoT pipelines
  • Priority support
Sign in to subscribe

Mega

€64.85 /month

  • 1,045,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1.045M calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

CBOR API

Encode and decode CBOR (RFC 8949, Concise Binary Object Representation) — the IETF-standard binary data format behind COSE, WebAuthn/FIDO2, the EU Digital COVID Certificate, and many IoT and constrained-device protocols. The encode endpoint turns a JSON value into compact, definite-length CBOR, choosing the smallest head for each integer, string, array and map; the decode endpoint parses CBOR back into a JSON value. It implements the spec across all major types — unsigned and negative integers of every width, byte and text strings (including indefinite-length chunked strings), arrays, maps, tags, the simple values false/true/null, and half-, single- and double-precision floats — and rejects trailing or truncated data rather than silently mangling it. Byte strings and any non-UTF-8 text come back losslessly as {"_bytes_hex":"…"}, tags as {"_tag":{"tag":N,"value":…}}, non-finite floats as {"_float":"NaN|Infinity|-Infinity"}, and other simple values as {"_simple":N}, 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 CBOR, COSE and WebAuthn payloads, bridging JSON and CBOR systems, IoT and smart-card pipelines, and teaching the format. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is CBOR specifically; for MessagePack use the MessagePack API, for BitTorrent's Bencode use the Bencode API, for JSON, YAML, TOML or XML use those format APIs, and for base64, hex, URL or HTML encoding use a general encoding API.

api.oanor.com/cbor-api

Bencode API

Encode and decode Bencode (BEP 3) — the serialization format BitTorrent uses for .torrent metainfo files and tracker responses. The encode endpoint turns a JSON value into Bencode: objects become dictionaries with their keys sorted in raw byte order exactly as the spec demands, arrays become lists, whole numbers become integers, and strings become length-prefixed byte strings. The decode endpoint parses Bencode back into a JSON value and enforces the spec strictly — no leading zeros in integers, no negative zero, dictionary keys must be sorted and unique, and no trailing data is tolerated — so malformed input is rejected rather than silently mangled. Binary byte strings that are not valid UTF-8 are represented losslessly as a {"_bytes_hex":"…"} object, so encode and decode round-trip exactly even for the binary "pieces" field of a real torrent. Decode accepts the data either as text or, for genuinely binary payloads, as hex; encode returns both the Bencode text (when printable) and its hex bytes. Everything is computed locally and deterministically, so it is instant and private. Ideal for building and parsing .torrent files, tracker tooling, BitTorrent clients and DHT messages, and teaching how the format works. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is BitTorrent's Bencode specifically; for base64, hex, URL or HTML encoding use a general encoding API, and for JSON, YAML, TOML or XML use those format APIs.

api.oanor.com/bencode-api

Bitwise API

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

IEEE 754 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

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for MessagePack API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call MessagePack API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for MessagePack API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does MessagePack API cost?
MessagePack API has a free tier with 100 calls / month. Paid plans start at €6.95 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is MessagePack API GDPR-compliant?
All requests to MessagePack API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/msgpack-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/msgpack-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/msgpack-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/msgpack-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.