English Français العربية

Base64 Codec API

Official registry Other

Encode/decode base64 and URL-safe base64. x402 micropayment.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (sse)
Claude Code 
claude mcp add --transport sse base64-codec-api 'https://base64-codec.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "base64-codec-api": {
            "type": "sse",
            "url": "https://base64-codec.api.klymax402.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Base64 Codec API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Base64 Codec API

Encode text to base64 or decode base64 to text. Supports standard and URL-safe variants with metadata. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "base64-codec": {
      "url": "https://base64-codec.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://base64-codec.api.klymax402.com/api/encode" \
  -H "Content-Type: application/json" \
  -d '{"data":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
utility_encode_base64POST/api/encode$0.003Encode or decode base64 data
utility_encode_base64

Use this when you need to encode text to base64 or decode base64 back to plaintext. Returns the result string with encoding metadata.

Parameters

NameTypeRequiredDescription
datastringyesThe data to encode or decode
actionstringnoAction: 'encode' or 'decode' (default: encode)

Example response:

{"result":"SGVsbG8gV29ybGQ=","action":"encode","inputLength":11,"outputLength":16,"urlSafe":false}

When to use: embedding binary data in JSON, preparing email attachments (MIME), or decoding base64 tokens from APIs. Use this BEFORE sending data through channels that only support ASCII.

Not for: hashing (use crypto_generate_hash), JWT decoding (use security_decode_jwt), URL slug creation (use text_generate_slug).

Example agent prompts

  • "Encode text to base64 or decode base64 back to plaintext"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Frequently asked questions

What is Base64 Codec API?

Encode/decode base64 and URL-safe base64. x402 micropayment.

How do I install Base64 Codec API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse base64-codec-api 'https://base64-codec.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Base64 Codec API need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Base64 Codec API open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Base64 Codec API?

It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.