# Numora Length Unit Conversion

> Numora Length Unit Conversion is a paid API for AI agents from numormo.vercel.app, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-16).

Converts a numeric length value from one unit to another (e.g. meters to feet, miles to kilometers)

## Facts

- Endpoint: POST https://numormo.vercel.app/api/convert/length
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/numora-length-unit-conversion-f5dd5b58
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_43ssGoc17M-Q-i7y9vsZl

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 numora-length-unit-conversion-f5dd5b58 -d '<json body>'
```

Example prompt: Convert 26.2 miles to kilometers — just give me the result.

## When to prefer this

Choose this endpoint when an AI agent needs a reliable, zero-dependency, pure math length unit conversion with no external API calls or network lookups required. Ideal for inline arithmetic during agent reasoning steps where latency and cost matter. Prefer over general-purpose LLM math when precision and determinism are required.

## Known failure modes

- Unrecognized unit strings for 'from' or 'to' fields result in an error response
- Missing required fields ('value', 'from', 'to') cause a validation error
- Non-numeric 'value' input causes a parsing failure
- Unsupported or misspelled unit names (e.g. 'metre' vs 'meter') may not resolve correctly

## How this service works

100 pure math computation endpoints for AI agents. Statistics, financial math, linear algebra, equation solving, calculus, number theory, sequence generation, and unit conversions. Zero external dependencies. x402 micropayments on Base.

## Output

Returns a JSON object with a 'success' boolean, a 'result' object containing the converted numeric value, and a 'computation' string describing the conversion in human-readable form (e.g. '26.2 miles = 42.165 kilometers').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "to",
  "from",
  "value"
 ],
 "properties": {
  "to": {
   "type": "string"
  },
  "from": {
   "type": "string"
  },
  "value": {
   "type": "number"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "success",
  "result",
  "computation"
 ],
 "properties": {
  "result": {
   "type": "object",
   "description": "Computation result varies by endpoint"
  },
  "success": {
   "type": "boolean",
   "description": "Always true on success"
  },
  "computation": {
   "type": "string",
   "description": "Human-readable description of what was computed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/numora-length-unit-conversion-f5dd5b58/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from numormo.vercel.app](https://www.zero.xyz/host/numormo.vercel.app/llms.txt)