API reference

Base64: Encode

Encode text as Base64 (RFC 4648).

GET POST /api/base64/encode MCP tool base64_encode

Encodes the UTF-8 bytes of input. standard uses +/ with = padding; url uses -_ without padding.

Browser version (runs locally): Base64.

Try it
Credentials
Remember these credentials

Not saved: you will paste them again next time.

No credentials yet? Get a client ID and secret. They are sent only to this site, in an Authorization: Basic header.

POST /api/base64/encode with a JSON body

Parameters

Parameter Type Default Description
input required string — Text to convert. As a text/plain POST body it is used verbatim.
mode standard | url standard standard: RFC 4648 §4 — A–Z a–z 0–9 + / with = padding. url: RFC 4648 §5 — - and _ instead of + and /, no padding (JWT style)

Also accepted on every endpoint: format (json | text). Parameters may come from the query string, a JSON object body, an urlencoded or multipart form, or (for input) a text/plain body.

Global parameters
Parameter Type Default Description
format json | text json json returns the documented object. text returns only the primary value as text/plain (see "Text output").

Response 200 application/json

Field Type Description
operation "encode" The direction performed.
mode "standard" | "url" The mode used (the default if none was given).
output string The converted text.

Text output (format=text, text/plain): The converted text only.

Errors

Errors are JSON: {"error": "<message>", "code": "<code>", "param": "<name>"?}.

Status Code When
400 missing_parameter A required parameter is absent.
400 unknown_parameter A parameter name is not in the table above (typos are rejected, not ignored).
400 invalid_parameter A value has the wrong type, is out of range, or is not an allowed value.
413 payload_too_large The request body exceeds 1 MiB.
405 method_not_allowed A method other than GET, POST or OPTIONS.

Behaviour

  • Idempotent: the same arguments always return the same result.
  • Requires a client ID and secret (authentication). Each call is recorded as one metadata row against your client ID; inputs and outputs are never stored or logged. Responses carry cache-control: no-store.
  • CORS: any origin may call this endpoint from a browser, using your credentials.

Examples

Responses below were produced by running each request through this code at build time. Long strings are shortened.

Standard alphabet

curl 'https://util.caruana.me/api/base64/encode?input=h%C3%A9llo%20w%C3%B6rld'

Response 200

{
  "operation": "encode",
  "mode": "standard",
  "output": "aMOpbGxvIHfDtnJsZA=="
}
Same call as an MCP tools/call
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "base64_encode",
    "arguments": {
      "input": "héllo wörld"
    }
  }
}

URL-safe

curl 'https://util.caruana.me/api/base64/encode?input=%3F%3F%3E&mode=url'

Response 200

{
  "operation": "encode",
  "mode": "url",
  "output": "Pz8-"
}
Same call as an MCP tools/call
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "base64_encode",
    "arguments": {
      "input": "??>",
      "mode": "url"
    }
  }
}