# Myncellium Paid LLM Route (MCP)

> Myncellium Paid LLM Route (MCP) is a paid API for AI agents from paid.myncellium.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-12).

Routes paid LLM tool calls via the Model Context Protocol (MCP) with per-call micropayment billing at $0.0005 USDC

## Facts

- Endpoint: POST https://paid.myncellium.com/mcp?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/myncellium-paid-llm-route-mcp-45f65c5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BFqwIl_oBpDh4SBItHYrZ

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 myncellium-paid-llm-route-mcp-45f65c5b -d '<json body>'
```

Example prompt: Call the Myncellium paid LLM route MCP tool named 'summarize_text' using streamable-http transport, passing in my input schema with a text field containing 'The quick brown fox jumps over the lazy dog' — charge the $0.0005 USDC fee per call.

## When to prefer this

Choose this endpoint when you need to invoke a paid, metered LLM or AI tool via the Model Context Protocol with automatic micropayment handling ($0.0005 USDC per call). It is ideal for agent pipelines that need to integrate monetized MCP tools without managing billing infrastructure separately. Prefer it over free MCP endpoints when the tool requires pay-per-use access control, or over REST-based LLM APIs when MCP protocol compatibility (streamable-http or SSE transport) is required.

## Known failure modes

- Insufficient USDC balance causes payment failure and request rejection
- Invalid or missing toolName results in tool-not-found error
- Malformed inputSchema causes schema validation failure
- Unsupported transport enum value causes routing error
- Network timeout on long-running LLM tool calls
- Missing required 'type' field in input object causes 400-level error

## How this service works

Myncellium paid MCP tool: paid_llm_route

## Output

Returns an MCP-formatted output object containing the result of the invoked LLM tool, typed according to the output schema specified in the request. The response reflects the tool's computation or generation result, delivered via the chosen MCP transport (streamable-http or SSE).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "toolName",
    "inputSchema"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "mcp"
    },
    "example": {
     "type": "object"
    },
    "toolName": {
     "type": "string"
    },
    "transport": {
     "enum": [
      "streamable-http",
      "sse"
     ],
     "type": "string"
    },
    "description": {
     "type": "string"
    },
    "inputSchema": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/myncellium-paid-llm-route-mcp-45f65c5b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from paid.myncellium.com](https://www.zero.xyz/host/paid.myncellium.com/llms.txt)