# CortexCloud Jobs Queue (x402)

> CortexCloud Jobs Queue (x402) is a paid API for AI agents from api.cortexcloud.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Submits an x402 endpoint call as an asynchronous job and returns a job ID with queued status, enabling non-blocking background execution of AI and data API requests paid per-call in USDC on Base.

## Facts

- Endpoint: GET https://api.cortexcloud.org/x402/v1/jobs
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cortexcloud-jobs-queue-x402-2a3ea193
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_af1OUEON9Qi-7twdRA_3B

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 cortexcloud-jobs-queue-x402-2a3ea193
```

Example prompt: Queue a background job on CortexCloud to run a search request — use the /x402/v1/search endpoint with POST method and my query payload — and give me the job ID so I can check back on it.

## When to prefer this

Choose this endpoint when you need to fire-and-forget a potentially slow or expensive CortexCloud AI/data API call without blocking your agent's main execution thread. It is ideal when the downstream operation (e.g. large inference, search, enrichment) may take more than a few seconds and you want to poll for results asynchronously. Prefer this over direct synchronous calls when orchestrating multi-step pipelines or when you need to parallelize several CortexCloud tasks at once.

## Known failure modes

- Invalid or missing endpoint path — returns error if 'endpoint' field is absent or malformed
- Payment failure — x402 USDC payment on Base not completed, resulting in 402 rejection
- Unsupported HTTP method — if method value is not accepted by the target endpoint
- Malformed payload — JSON parse errors or schema violations in the nested payload object
- Target endpoint unavailable — downstream CortexCloud service is down or unreachable

## How this service works

OpenAI-compatible AI and data API for agents. Pay per call in USDC on Base via x402 — no API keys, no subscriptions, no lock-in.

## Output

Returns a JSON object containing a job ID (e.g. 'job_abc') and a status field set to 'queued', confirming the async task was accepted and is waiting to be processed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "method": {
   "type": "string",
   "default": "POST"
  },
  "payload": {
   "type": "object",
   "description": "Request body to send to the endpoint"
  },
  "endpoint": {
   "type": "string",
   "description": "Relative x402 endpoint to call asynchronously, e.g. /x402/v1/search"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "format": "application/json",
 "example": {
  "id": "job_abc",
  "status": "queued"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cortexcloud-jobs-queue-x402-2a3ea193/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.cortexcloud.org](https://www.zero.xyz/host/api.cortexcloud.org/llms.txt)