Home / Agents / Base64 Check and Decoded Size
Base64 Check and Decoded Size
Check whether text is valid base64 or base64url (RFC 4648): the alphabet, the padding fix, the first bad character, canonical bits, the decoded size and whether it is UTF-8, without returning the content, with a signed record.
Testing
- What it does
- Check whether text is valid base64 or base64url (RFC 4648): the alphabet, the padding fix, the first bad character, canonical bits, the decoded size and whether it is UTF-8, without returning the content, with a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
base64_checkat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
Base64 Check and Decoded Size is for coding agents and developers that pass tokens, keys, file bodies or API payloads around as base64 and need to know, the same way every time, whether a string will decode and how big it is. Check whether text is valid base64 or base64url (RFC 4648 sections 4 and 5) before you decode it or send it on. Send the text; get back which alphabet it uses, whether the padding is right (and exactly how many '=' to add or remove), the first bad character and its position if there is one, whether line breaks or spaces are in it, whether the unused bits are zero (canonical, RFC 4648 3.5), the decoded size in bytes, and whether the decoded bytes are valid UTF-8 text. The decoded content itself is never returned. Padding rule: required (RFC 4648 default), optional, or none (as JWT and other base64url users do). It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Gitlab, Postman). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Coding agents and developers that pass tokens, keys, file bodies or API payloads around as base64 and need to know, the same way every time, whether a string will decode and how big it is.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not return, store or sign the decoded content (only its size and whether it is UTF-8). Does not check what the bytes mean (a key, an image, JSON). Does not decode base32, base16 or other encodings, and does not check MIME's 76-character line limit or PEM's 64 (it reports the longest line). An empty text is valid base64 of zero bytes (RFC 4648 section 10). Not security advice: base64 is not encryption.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "base64_check", "arguments": {"text": "Zm9vYg=="}}}For agents
Tool base64_check on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:sasf2tkjwtb4z6cjeg3f6o43ie): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): bBY8IcIF8MXQ/6VVZW9thOLsLs7SOpIPEFzwMzZz9j0=
For agents that search MCP registries for base64, base64url, RFC 4648 tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A base64 check is one step of fixing an integration. Tell LLPRO the whole job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card