# JarvisClaw AI API Gateway – Marketplace Endpoint 623

> JarvisClaw AI API Gateway – Marketplace Endpoint 623 is a paid API for AI agents from api.jarvisclaw.ai, paid per call via x402, $0.046/call, status unknown (last checked 2026-09-15).

Routes AI API requests through a smart gateway with pay-per-call billing via x402, settling in USDC on Base or Solana, compatible with OpenAI-style request formats.

## Facts

- Endpoint: GET https://api.jarvisclaw.ai/v1/marketplace/api/623
- Price: $0.046/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jarvisclaw-ai-api-gateway-marketplace-endpoint-623-9fed8030
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fUsgxpca1wuQylvPGUV2H

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-623-9fed8030
```

Example prompt: Send my query through the JarvisClaw AI gateway marketplace endpoint and pay per call in USDC — I want to ask: 'Summarize the key trends in renewable energy for 2024.'

## When to prefer this

Choose this endpoint when you need pay-per-call AI inference with no subscription commitment, want to settle payments in USDC on Base or Solana via x402, or require an OpenAI-compatible gateway that works within crypto-native agent workflows. It is ideal for agentic systems that need fine-grained cost control per AI call without pre-paying for a fixed API quota.

## Known failure modes

- Insufficient USDC balance causes x402 payment failure and request rejection
- Invalid or missing query parameter returns 400 Bad Request
- Gateway routing failure if no available backend model matches the request
- Rate limiting or marketplace endpoint unavailability returns 503
- Malformed OpenAI-incompatible request structure may cause parsing errors

## 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 routed through JarvisClaw's smart gateway, structured in an OpenAI-compatible format. The response includes the model's completion text and any associated metadata from the routed provider.

## 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-623-9fed8030/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)