# ONE Engine Base64 Encode

> ONE Engine Base64 Encode is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0009/call, status unknown (last checked 2026-10-02).

Encodes UTF-8 text as standard Base64 or URL-safe Base64URL (unpadded) via a pay-per-call API

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/base64/encode?utm_source=zero.xyz
- Price: $0.0009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-base64-encode-d8f672ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sMYzysDSAPVcWSEv3HWyh

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 one-engine-base64-encode-d8f672ec -d '<json body>'
```

Example prompt: Base64-encode the text 'Hello, World!' for me — use the URL-safe format so it's safe to embed in a URL without padding.

## When to prefer this

Choose this endpoint when an AI agent needs a lightweight, pay-per-call Base64 or Base64URL encoding utility without managing local encoding libraries or infrastructure. Ideal for agents operating in environments where running code is not possible and a simple HTTP call suffices. The url_safe option makes it directly useful for JWT construction, URL parameter encoding, and data URI preparation.

## Known failure modes

- Non-UTF-8 or malformed text input may cause a 400 error
- Missing required 'text' field returns validation error
- Network or worker availability issues may cause 5xx responses
- Payment failure or insufficient funds returns 402 status

## How this service works

Encode UTF-8 text as standard Base64 or Base64URL

## Output

Returns a Base64 or Base64URL-encoded string representation of the input UTF-8 text. When url_safe is true, the output uses the URL-safe alphabet (- and _ instead of + and /) and omits padding characters (=).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "UTF-8 text to encode"
  },
  "url_safe": {
   "type": "boolean",
   "description": "Return unpadded Base64URL when true"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-base64-encode-d8f672ec/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)