Spec

Frammenti di codice

curl "https://api.oanor.com/bencode-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/bencode-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/bencode-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/bencode-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Risposta di esempio

Una risposta reale di questo endpoint, acquisita dall'ultimo health check.

{
    "data": {
        "name": "Bencode API",
        "notes": "Bencode has four types: byte strings, integers, lists and dictionaries. There is no boolean, null or float — torrents use 0/1 and integers. Dictionary keys are always emitted sorted by raw byte order. This is BitTorrent's format; for base64/hex/URL/HTML use a general encoding API and for JSON/YAML/TOML/XML use those format APIs. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/encode",
                "params": {
                    "json": "a JSON value to encode (string)"
                },
                "returns": "the Bencode text (when printable), its hex, and byte length"
            },
            {
                "path": "/v1/decode",
                "params": {
                    "hex": "or the raw Bencode bytes as hex (for binary .torrent data)",
                    "bencode": "the Bencode text"
                },
                "returns": "the decoded JSON value"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Encode and decode Bencode (BEP 3) — the serialization format used by BitTorrent for .torrent metainfo files and tracker responses. The encode endpoint turns a JSON value into Bencode (objects become dictionaries with keys sorted in raw byte order as the spec requires, arrays become lists, whole numbers become integers, strings become length-prefixed byte strings); the decode endpoint parses Bencode back into a JSON value, enforcing the spec's rules (no leading zeros in integers, no negative zero, strictly sorted unique dictionary keys, no trailing data). Binary byte strings that are not valid UTF-8 are represented losslessly as {\"_bytes_hex\":\"…\"} so encode/decode round-trip exactly. Decode accepts the data as text or, for real binary .torrent payloads, as hex; encode returns both the Bencode text (when printable) and its hex. Everything is computed locally and deterministically. Pure local computation — no key, no third-party service, instant. Live, nothing stored."
    },
    "meta": {
        "timestamp": "2026-06-03T17:42:18.060Z",
        "request_id": "583ef47d-4389-4f84-b821-de14e2b305e0"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}