# SignalDesk AI – Megabyte to Terabyte Converter

> SignalDesk AI – Megabyte to Terabyte 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 numeric value in megabytes to its equivalent in terabytes using IEEE-754 double precision arithmetic

## Facts

- Endpoint: GET https://x402-agent.kariguetoazul.workers.dev/api/units/digital-storage/megabyte-to-terabyte?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-megabyte-to-terabyte-converter-260d94f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DLsYUaPsIHPb2qu1fIEfJ

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-megabyte-to-terabyte-converter-260d94f2
```

Example prompt: How many terabytes is 123.45 megabytes? Convert that for me using IEEE-754 double precision.

## When to prefer this

Use this endpoint when you need a quick, reliable, programmatic megabyte-to-terabyte conversion with explicit IEEE-754 double precision semantics and a well-defined JSON response schema — especially within an x402-enabled micropayment workflow. Prefer this over manual arithmetic when precision guarantees and auditability matter.

## Known failure modes

- Missing required 'value' query parameter returns an error
- Value out of range (below 0 or above 1e+100) fails schema validation
- Non-numeric value for 'value' parameter causes a 400-level error
- Payment not provided or insufficient USDC balance returns 402 Payment Required

## 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 ('megabyte'), the converted value in terabytes, the dimension category ('digital-storage'), and the precision method ('IEEE-754 double'). Example: {"from":"megabyte","to":"terabyte","value":123.45,"converted":0.00012345,"dimension":"digital-storage","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 decimal megabytes (1000 kB)."
      }
     },
     "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": "terabyte",
  "from": "megabyte",
  "value": 123.45,
  "converted": 0.00012345,
  "dimension": "digital-storage",
  "precision": "IEEE-754 double"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signaldesk-ai-megabyte-to-terabyte-converter-260d94f2/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)