# AgentShelf Base64 Encode

> AgentShelf Base64 Encode is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.009/call, status unknown (last checked 2026-09-29).

Encodes a given text string into its Base64 representation, with no network calls or LLM involvement.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/base64-encode?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentshelf-base64-encode-7829888c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_n21ShoR9VYk8wkXVAZTqp

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentshelf-base64-encode-7829888c -d '<json body>'
```

Example prompt: Can you base64 encode this text for me: 'Hello, World! This is my API payload.'

## When to prefer this

Choose this endpoint when an agent needs a deterministic, server-side Base64 encoding of a text string without relying on LLM output or local code execution. It is useful in sandboxed environments where executing local encoding libraries is restricted. Note: the description recommends preferring an unpaid POST /v1/sandbox/base64-encode endpoint if available, as it provides the same function at no cost. Use this paid endpoint when the sandbox alternative is unavailable.

## Known failure modes

- Empty or missing 'text' field returns a validation error
- Input exceeding 100,000 characters is rejected due to maxLength constraint
- Malformed JSON request body results in a 400-level error
- Payment failure or insufficient USDC balance causes a 402 Payment Required response

## How this service works

Call when an agent needs text encoded with base64. No network and no LLM. Exact $0.009 USDC. Prefer unpaid POST /v1/sandbox/base64-encode first.

## Output

Returns the Base64-encoded representation of the input text string. The output is a standard Base64 string that can be used directly in HTTP headers, JSON payloads, MIME messages, or any context requiring Base64-safe data encoding.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "examples": [
    "Hello, World!"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Input for this SKU. The route description says whether it is plain text, a URL, base64 bytes, or an already-encoded token."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentshelf-base64-encode-7829888c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)