# SignalDesk AI Micrometer to Kilometer Converter

> SignalDesk AI Micrometer to Kilometer Converter is a paid API for AI agents from x402-agent.kariguetoazul.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-13).

Converts a length value from micrometers (µm) to kilometers (km) using IEEE-754 double precision arithmetic

## Facts

- Endpoint: GET https://x402-agent.kariguetoazul.workers.dev/api/units/length/micrometer-to-kilometer?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signaldesk-ai-micrometer-to-kilometer-converter-39a1ec62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R75KBOS06oDAqlrtd2CqB

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 signaldesk-ai-micrometer-to-kilometer-converter-39a1ec62
```

Example prompt: Can you convert 123.45 micrometers to kilometers for me?

## When to prefer this

Use this endpoint when you need a simple, reliable, single-call micrometer-to-kilometer conversion with IEEE-754 precision and a structured JSON response. Prefer this over general-purpose calculators when you need programmatic consumption of the result with consistent output schema, or when integrating into an agentic workflow that requires a paid, auditable unit conversion step.

## Known failure modes

- Missing required 'value' query parameter returns an error
- Negative input values are rejected (minimum is 0)
- Values exceeding 1e+100 are rejected by schema validation
- Non-numeric input causes a validation error
- Payment not provided or insufficient USDC triggers 402 response

## How this service works

Evidence-backed autonomous AI jobs and paid data tools. Queue/D1/cron run outside the chat; free quotas and bounded execution apply.

## Output

A JSON object containing the original value and unit (micrometer), the converted value in kilometers as an IEEE-754 double-precision float, the dimension (length), and a precision label. Example: {from: 'micrometer', to: 'kilometer', value: 123.45, converted: 1.2345e-7, dimension: 'length', precision: 'IEEE-754 double'}.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "value"
     ],
     "properties": {
      "value": {
       "type": "number",
       "maximum": 1e+100,
       "minimum": 0,
       "description": "Amount in micrometres."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "kilometer",
  "from": "micrometer",
  "value": 123.45,
  "converted": 1.2345e-7,
  "dimension": "length",
  "precision": "IEEE-754 double"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signaldesk-ai-micrometer-to-kilometer-converter-39a1ec62/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent.kariguetoazul.workers.dev](https://www.zero.xyz/host/x402-agent.kariguetoazul.workers.dev/llms.txt)