# JEGA MCP Schema Translator

> JEGA MCP Schema Translator is a paid API for AI agents from api.jega.digital, paid per call via x402, $0.001/call, status down (last checked 2026-10-13).

Converts legacy OpenAPI, Swagger, or unstructured JSON API documentation into strict, token-optimized MCP/Anthropic tool-calling schemas deterministically at 4ms latency.

## Facts

- Endpoint: POST https://api.jega.digital/api/schema/mcp?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-jega-digital-78154037
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CPbebY8alSRKGupk2EVos

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 api-jega-digital-78154037 -d '<json body>'
```

Example prompt: Convert this API into an MCP tool-calling schema — the name is 'WeatherService' and the description is 'Returns current weather and 5-day forecast for a given city and country code'.

## When to prefer this

Choose this endpoint when you need to deterministically convert API documentation or descriptions into MCP/Anthropic tool-calling schemas without incurring LLM inference costs or latency. Ideal for bulk schema migrations, cost-sensitive pipelines, or automated tooling workflows where consistent, reproducible output is required at sub-10ms speeds.

## Known failure modes

- Missing or empty 'name' field returns a validation error
- Missing or empty 'description' field returns a validation error
- Malformed JSON body returns a 400 error
- Service unavailability returns a 5xx response
- Payment failure (x402) returns a 402 status requiring USDC payment

## How this service works

Deterministic MCP Schema Translator.

## Output

Returns a strict, token-optimized MCP/Anthropic tool-calling schema derived from the provided API name and description, ready to inject into an LLM system prompt or tool registry without further LLM post-processing.

## Example request

```json
{
 "name": "WeatherService",
 "description": "Returns current weather and 5-day forecast for a given city and country code"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "name": {
   "type": "string"
  },
  "description": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "name",
  "description",
  "inputSchema"
 ],
 "properties": {
  "name": {
   "type": "string"
  },
  "description": {
   "type": "string"
  },
  "inputSchema": {
   "type": "object",
   "required": [
    "type",
    "required",
    "properties"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "required": {
     "type": "array",
     "items": {
      "type": "unknown"
     }
    },
    "properties": {
     "type": "object",
     "required": [],
     "properties": {}
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-jega-digital-78154037/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jega.digital](https://www.zero.xyz/host/api.jega.digital/llms.txt)