# Animica Standard Chat Completions (x402)

> Animica Standard Chat Completions (x402) is a paid API for AI agents from animica.dev, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-15).

Provides OpenAI-compatible chat completions via Animica's serving bridge, billed per-call at $0.003271 USDC through the x402 payment protocol.

## Facts

- Endpoint: POST https://animica.dev/x402/v1/standard/chat/completions
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/animica-standard-chat-completions-x402-7a0c1895
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x3dbALOrmZBpa7C_QncZ5

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 animica-standard-chat-completions-x402-7a0c1895 -d '<json body>'
```

Example prompt: Send a chat message to the Animica LLM endpoint using the model listed at /v1/models, with max 200 tokens, asking: 'Explain the concept of zero-knowledge proofs in two sentences.'

## When to prefer this

Choose this endpoint when you need a pay-per-call LLM inference API with no monthly subscription or API key setup, particularly when your agent already handles x402 micropayments in USDC. It is ideal for sporadic or bursty usage patterns where a flat-rate subscription would be wasteful, or for agents operating in crypto-native environments that prefer on-chain verifiable micropayments over traditional billing.

## Known failure modes

- Payment failure or insufficient USDC balance returns 402 Payment Required
- Streaming requested (stream: true) is unsupported on this paid path and will be rejected
- Invalid or unrecognized model ID returns an error — check /v1/models first
- Malformed messages array (missing role or content fields) causes a 400 Bad Request
- Exceeding model context length with too many messages or a very high max_tokens may cause an error
- Service unavailability on animica.dev returns 5xx errors

## How this service works

Standard-tier chat/completions (OpenAI-compatible), served by Animica's network. Cheaper than priority, standard latency — priced at 3x settlement gas.

## Output

An OpenAI-compatible chat.completion JSON object containing the assistant's reply message, finish reason, model used, and token usage statistics (prompt tokens, completion tokens, total tokens).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "model": {
   "type": "string",
   "description": "model id (see the free /v1/models)"
  },
  "stream": {
   "type": "boolean",
   "description": "must be false/absent — streaming is not yet supported on the paid path"
  },
  "messages": {
   "type": "array",
   "description": "OpenAI-style chat messages"
  },
  "max_tokens": {
   "type": "integer",
   "description": "completion budget"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/animica-standard-chat-completions-x402-7a0c1895/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from animica.dev](https://www.zero.xyz/host/animica.dev/llms.txt)
