# OmniAPI Base64 Encode

> OmniAPI Base64 Encode is a paid API for AI agents from omni-api-cyan.vercel.app, paid per call via x402, $0.071681/call, status unknown (last checked 2026-09-15).

Encodes a string or binary input into Base64 format

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/base64/encode
- Price: $0.071681/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-base64-encode-2d02df42
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ONYWR_lkVJIALZGTY4xmo

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 omniapi-base64-encode-2d02df42 -d '<json body>'
```

Example prompt: Can you base64 encode the string 'Hello, World!' for me so I can embed it in a JSON payload?

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call base64 encoding operation without standing up your own infrastructure, especially within a broader x402 micropayment workflow already in use on OmniAPI. It is less appropriate than a local library for high-volume batch encoding where per-call costs accumulate.

## Known failure modes

- Missing required 'query' field returns validation error
- Oversized input may be rejected or time out
- Malformed JSON request body returns 400 error
- Payment failure via x402 (insufficient USDC balance) blocks the request
- Network or Vercel cold-start timeout on large payloads

## How this service works

444 endpoints across 9+ chains. Crypto, AI, Social, Finance, Weather, Tools. Pay per call in USDC via x402 with 4 facilitators: Dexter, Meridian, FluxA, GoPlausible.

## Output

Returns a base64-encoded representation of the provided input string or data, delivered as a JSON object containing the encoded output string.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Input data for the endpoint"
  },
  "query": {
   "type": "string",
   "description": "Search query or input text"
  },
  "params": {
   "type": "object",
   "description": "Additional parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/omniapi-base64-encode-2d02df42/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omni-api-cyan.vercel.app](https://www.zero.xyz/host/omni-api-cyan.vercel.app/llms.txt)
