# OmniAPI Data Conversion Tool

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

Converts data from one format or representation to another via a general-purpose conversion endpoint

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/convert/data
- Price: $0.06397/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-data-conversion-tool-da96f855
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hUa5q-nPg25N4ehMraSNB

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-data-conversion-tool-da96f855 -d '<json body>'
```

Example prompt: Can you convert this base64-encoded string back to plain text for me: 'SGVsbG8gV29ybGQ='?

## When to prefer this

Use this endpoint when you need a general-purpose data conversion or transformation — especially for encoding/decoding, format changes, or unit conversions — and you are already operating in an x402 micropayment context and want a single paid API to handle multiple conversion needs without managing separate services.

## Known failure modes

- Missing required 'query' field returns a 400 validation error
- Unsupported conversion type may return an empty or error response
- Malformed input data string may cause unexpected output or failure
- Payment failure via x402 returns a 402 Payment Required response

## 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 JSON object containing the converted or transformed output corresponding to the provided input data and query parameters.

## 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-data-conversion-tool-da96f855/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)