Blob Decode
Identify and unwrap a bounded caller-supplied opaque string into readable JSON, text or binary evidence using deterministic local rules for JWT payloads, canonical Base64/Base64URL and gzip. Ambiguous hex/Base64 representations stop in auto mode; canonical hex and Brotli can be selected only through explicit bounded hints. JWT claims are decode-only and always marked unverified.
Forest exposes this capability as a deterministic machine-readable API for software agents. Discovery is free; execution uses the canonical paid endpoint below. The live x402 challenge is the source of truth for payment terms.
Typical agent tasks
This capability is intended for bounded machine decisions such as:
- decode this opaque blob into readable JSON or text
- unwrap a Base64 gzip JSON payload from a webhook or API response
- decode a JWT header and payload without claiming signature verification
- identify and decode nested Base64 or explicitly hinted hex data safely
- inspect an encoded log payload without using an LLM or external service
What Forest guarantees
- local deterministic CPU-only decoding with zero network, provider, shell, persistence or secret access
- at most 4 unwrap transformations with 131072-byte per-layer and 262144-byte aggregate decoded-output bounds
- gzip and hinted Brotli decompression use an effective output cap of max(1024 bytes, compressed bytes x 64)
- auto mode stops explicitly on ambiguous hex/Base64 input; the hex hint accepts only canonical even-length hexadecimal input and never falls back to another decoder
- terminal JSON, text or binary classification still runs after the final allowed unwrap without consuming another transform layer
- JWT compact values are decoded only when header and payload are canonical Base64URL JSON objects, and verified is always false
- binary results are returned as bounded Base64 instead of lossy UTF-8 replacement text
Boundaries
- JWT/JWS signature verification, authenticity, authorization or trustworthiness of decoded claims
- encryption/decryption, password cracking, archive extraction or arbitrary compression-format detection
- automatic selection of hex over Base64 for ambiguous strings; callers must use the explicit hex hint when that representation is intended
- automatic Brotli detection; Brotli requires the explicit bounded hint
- semantic interpretation of decoded JSON/text or recursive document fetching
Machine contract
The request and response schemas are published in the canonical OpenAPI document. This page shows a representative input from the same production manifest.
Input example
Canonical paid endpoint
Related capabilities
- Text Base64 — Encode bounded caller-supplied UTF-8 text as standard or URL-safe Base64, or decode canonical Base64 back to valid UTF-8 text. Forest performs the transform locally with no network request and rejects invalid encodings, non-UTF-8 decoded bytes, and outputs beyond the 100 KiB byte bound.
- Json Diff — Deep-compare two caller-supplied JSON values with deterministic object-key ordering and explicit index-based array semantics. Returns bounded added, removed and changed paths with primitive before/after values when safe; performs no network request, model inference, persistence or mutation.
- Json Validate — Validate caller-supplied JSON against Forest bounded JSON Schema subset v1 before an agent trusts or forwards structured output. Returns deterministic machine-readable violations with stable paths; performs no network request, remote $ref resolution, regex evaluation, model inference or mutation.