# Tanship PayAI Console — AI Answer Endpoint

> Tanship PayAI Console — AI Answer Endpoint is a paid API for AI agents from x402.tanship.dev, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-15).

Returns an AI-generated answer to a question or prompt, gated by USDC micropayment via the x402 protocol on Base.

## Facts

- Endpoint: POST https://x402.tanship.dev/v1/ai/answer
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tanship-payai-console-ai-answer-endpoint-2b772c2f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_to002ZxvxgueRg7Imeqpr

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-ai-answer-endpoint-2b772c2f -d '<json body>'
```

Example prompt: Ask the Tanship PayAI answer endpoint: what are the main differences between Proof of Work and Proof of Stake consensus mechanisms? Pay the $0.008 USDC fee via x402 on Base.

## When to prefer this

Choose this endpoint when you need a pay-per-call AI answer service with no subscription required, where each query is settled via USDC micropayment on the Base blockchain using the x402 protocol. Ideal for agents that need to answer questions on demand without committing to a flat-rate plan, or for applications billing end-users per AI query using on-chain stablecoin payments.

## Known failure modes

- Payment not included or invalid x402 header — returns HTTP 402 Payment Required
- Insufficient USDC balance on Base wallet — payment fails, request rejected
- Malformed request body — returns 400 Bad Request if required fields missing
- Network congestion on Base causing payment validation delays
- AI backend timeout if prompt is too long or complex
- Invalid bodyType enum value causes schema validation error

## 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

A text response containing the AI-generated answer to the submitted question or prompt. The response is returned after the x402 USDC micropayment on Base is validated and the request is processed.

## 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-ai-answer-endpoint-2b772c2f/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)