# x402 AI APIs – Discord Shield Chat Endpoint

> x402 AI APIs – Discord Shield Chat Endpoint is a paid API for AI agents from x402-ai-peach.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).

Provides a pay-per-call chat completion endpoint (OpenAI-compatible) accessible via x402 micropayments, routed through a Discord-shield branded path

## Facts

- Endpoint: POST https://x402-ai-peach.vercel.app/api/discord-shield
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-ai-apis-discord-shield-chat-endpoint-7e1662a7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y0X5qX7dolFwV3a3SubfA

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 x402-ai-apis-discord-shield-chat-endpoint-7e1662a7 -d '<json body>'
```

Example prompt: Send this conversation history to the x402 discord-shield chat endpoint, allow up to 512 tokens in the response, use temperature 0.7, and pay the $0.05 USDC fee automatically: [{"role":"user","content":"What is the capital of France?"}]

## When to prefer this

Choose this endpoint when you need an OpenAI-compatible chat completion API with no subscription and pay-per-call billing via x402 USDC micropayments. Ideal for agents or apps that want to avoid API key management and instead use programmable crypto payments. Best when call volume is low or unpredictable and you want cost control at the individual-request level.

## Known failure modes

- Payment not included or insufficient USDC — returns HTTP 402 Payment Required
- Missing required 'messages' field — returns 400 Bad Request
- Model backend unavailable — returns 500 or 503
- Invalid temperature or max_tokens values — may return 422 or 400
- Streaming requested but client does not handle chunked responses correctly — partial data loss

## How this service works

Paid AI API endpoints via x402 micropayments

## Output

Returns an OpenAI-style JSON object containing a response ID, and a choices array with the assistant's generated message (role + content string). Supports optional streaming mode for incremental token delivery.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "messages"
 ],
 "properties": {
  "stream": {
   "type": "boolean",
   "description": "Stream response"
  },
  "messages": {
   "type": "array",
   "description": "Chat messages array"
  },
  "max_tokens": {
   "type": "integer",
   "description": "Max tokens"
  },
  "temperature": {
   "type": "number",
   "description": "Temperature"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string",
   "description": "Response ID"
  },
  "choices": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "message": {
      "type": "object",
      "properties": {
       "role": {
        "type": "string"
       },
       "content": {
        "type": "string"
       }
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-ai-apis-discord-shield-chat-endpoint-7e1662a7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-ai-peach.vercel.app](https://www.zero.xyz/host/x402-ai-peach.vercel.app/llms.txt)
