# OmniAPI Length Unit Converter

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

Converts a length value from one unit of measurement to another (e.g. miles to kilometers, inches to centimeters).

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/tools/convert/length
- Price: $0.026508/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-length-unit-converter-7ea38a66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xVRej6fnQwrs15u9uDvsj

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-length-unit-converter-7ea38a66 -d '<json body>'
```

Example prompt: Can you convert 26.2 miles to kilometers for me?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call length unit conversion without setting up a local conversion library. Suitable for AI agents that need on-demand measurement conversions across a wide range of length units as part of a broader workflow, especially when already integrated with the OmniAPI x402 payment ecosystem.

## Known failure modes

- Unrecognized unit names return an error or null result
- Missing query parameter returns a 400 bad request
- Ambiguous query text may produce incorrect unit interpretation
- Non-numeric input values may cause a parsing error
- Payment failure via x402 returns a 402 response before processing

## 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 converted length value in the requested target unit, typically as a numeric result accompanied by the unit label and original input details.

## 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-length-unit-converter-7ea38a66/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)