# JarvisClaw AI API Gateway – Marketplace Endpoint #535

> JarvisClaw AI API Gateway – Marketplace Endpoint #535 is a paid API for AI agents from api.jarvisclaw.ai, paid per call via x402, $0.0115/call, status unknown (last checked 2026-10-20).

Routes AI API calls through JarvisClaw's smart marketplace gateway to a specific AI provider/model, billed per-call in USDC via x402 protocol

## Facts

- Endpoint: POST https://api.jarvisclaw.ai/v1/marketplace/api/535?utm_source=zero.xyz
- Price: $0.0115/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jarvisclaw-ai-api-gateway-marketplace-endpoint-535-de64b7c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_woSdx3SQ9tAvRHFSFfpXy

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 jarvisclaw-ai-api-gateway-marketplace-endpoint-535-de64b7c1 -d '<json body>'
```

Example prompt: Send my prompt through JarvisClaw's AI marketplace gateway — use endpoint 535 — and pay the per-call fee in USDC: 'Summarize the key differences between Base and Solana blockchains in three bullet points.'

## When to prefer this

Choose this endpoint when you need OpenAI-compatible AI completions billed per-call in USDC without a monthly subscription, especially in Web3-native or agent-to-agent workflows where x402 micropayments on Base or Solana are already part of your payment stack. Prefer it over direct OpenAI when you want decentralized, pay-as-you-go billing, or when you need smart routing across multiple AI providers from a single endpoint.

## Known failure modes

- Payment failure: x402 payment not included or insufficient USDC balance results in 402 Payment Required
- Invalid query: missing or malformed query parameter returns 400 Bad Request
- Routing failure: no suitable upstream AI provider available may return 503 or gateway error
- Rate limiting: too many requests in a short window may result in 429 Too Many Requests
- Network timeout: upstream AI provider slow response may cause gateway timeout

## How this service works

AI API Gateway with smart routing, pay per call via x402. OpenAI-compatible. Settled in USDC on Base & Solana.

## Output

Returns an AI-generated text response (OpenAI-compatible format) from the routed model, reflecting the query submitted. The response is typically a JSON completion object compatible with the OpenAI Chat Completions API schema, containing the model's output text and relevant metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "Request parameters"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jarvisclaw-ai-api-gateway-marketplace-endpoint-535-de64b7c1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jarvisclaw.ai](https://www.zero.xyz/host/api.jarvisclaw.ai/llms.txt)