# OmniAPI Base64 Decode

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

Decodes a Base64-encoded string back into its original plain-text or binary representation

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/base64/decode
- Price: $0.052257/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-decode-96fa7bd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UGV4cF6Suicj-k0mVizOi

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-decode-96fa7bd7 -d '<json body>'
```

Example prompt: Can you decode this Base64 string for me: 'SGVsbG8sIFdvcmxkIQ=='?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call Base64 decoding step within an automated workflow and already have access to the OmniAPI x402 payment infrastructure. It is ideal for agents that encounter Base64-encoded strings in API responses, JWTs, or data pipelines and need to recover the original content without setting up a local decoding library.

## Known failure modes

- Invalid Base64 input string causes a decoding error or malformed response
- Empty or missing query/input field returns an error
- Padded vs unpadded Base64 variants may cause parsing issues
- Binary output may not be human-readable if the original was non-text data
- Network or payment (x402) failure prevents the request from completing

## 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 the decoded plain-text or binary content that was originally encoded as the Base64 input string, allowing the agent to read or process the underlying data.

## 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-decode-96fa7bd7/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)