# Tanship PayAI Console — Queue Enqueue

> Tanship PayAI Console — Queue Enqueue is a paid API for AI agents from x402.tanship.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-11).

Enqueues an HTTP-type job (POST request with JSON, form-data, or text body) into the Tanship PayAI task queue, gated by a $0.003 USDC micropayment via the x402 protocol on Base.

## Facts

- Endpoint: POST https://x402.tanship.dev/v1/queue/enqueue?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanship-payai-console-queue-enqueue-35c20dfb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8QXG5vouOnfgwdTu0ANBV

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 tanship-payai-console-queue-enqueue-35c20dfb -d '<json body>'
```

Example prompt: Add a new job to the Tanship PayAI queue — send an HTTP POST with a JSON body containing the task details I want to run, and pay the $0.003 USDC x402 fee automatically.

## When to prefer this

Use this endpoint when you need to asynchronously enqueue an HTTP-based AI or browser automation job and are comfortable paying a $0.003 USDC micropayment per call via the x402 protocol on Base. Prefer this over synchronous endpoints when the task may take time and you want to receive a job ID to poll or retrieve results later.

## Known failure modes

- Payment rejected or insufficient USDC balance — x402 402 Payment Required response
- Invalid body type enum value (must be json, form-data, or text) — 400 validation error
- Missing required input fields (type, method, bodyType, body) — 400 schema validation error
- x402 payment on wrong network (not Base eip155:8453) — payment failure
- Queue service unavailable or overloaded — 503 or timeout

## How this service works

Payment-gated AI and browser automation API using the x402 protocol. All /v1/* endpoints require USDC payment on Base (eip155:8453) via x402 v2 exact scheme.

## Output

Returns a confirmation that the job has been enqueued, typically including a job or queue ID and initial status, allowing the caller to track or retrieve results later.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tanship-payai-console-queue-enqueue-35c20dfb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.tanship.dev](https://www.zero.xyz/host/x402.tanship.dev/llms.txt)