ai.chat

OpenAI-compatible chat completions across every frontier model on one endpoint — GPT-5, Claude, Gemini, Grok, DeepSeek, Llama, Mistral and ~290 more. POST { model, messages, max_tokens?, temperature?, top_p?, stop? } and get back a standard chat.completion (choices[].message + usage). Pay per call in USDC via x402 — no accounts, no provider keys, no subscriptions. Price scales with the model and max_tokens and is quoted in the 402. List selectable models at GET /api/ai/models.

price
variable — from $0.0010 USDC, computed per request and quoted in the 402 before you pay (see Pricing below)
method
POST/api/ai/chat
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The chat API is a pay-per-call ai endpoint built for AI agents and autonomous software. OpenAI-compatible chat completions across every frontier model on one endpoint — GPT-5, Claude, Gemini, Grok, DeepSeek, Llama, Mistral and ~290 more.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in chat data source for an agent tool-use loop, an MCP host, or a backend that needs ai data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
modelrequiredstringGateway model id, e.g. openai/gpt-5, anthropic/claude-opus-4.8, google/gemini-3-pro-preview. Full list: GET /api/ai/models.
min 1 chars · max 80 chars
messagesrequiredarrayOpenAI-style message list.
max_tokensintegerMax output tokens (default 1024).
min 1 · max 8192
temperaturenumber
min 0 · max 2
top_pnumber
min 0 · max 1
stop

Code samples

cURLbash
# 1. Probe the endpoint with no auth — receive 402 with PaymentRequirements
curl -sS -X POST 'https://2s.io/api/ai/chat' \
  -H 'Content-Type: application/json' \
  -d '{"model":"example","messages":[{"role":"system","content":"example"}],"max_tokens":1,"temperature":0,"top_p":0,"stop":"example"}'

# 2. Sign the EIP-3009 transferWithAuthorization for the advertised price +
#    payTo from the 402 envelope, then retry with PAYMENT-SIGNATURE:
curl -sS -X POST 'https://2s.io/api/ai/chat' \
  -H 'Content-Type: application/json' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>' \
  -d '{"model":"example","messages":[{"role":"system","content":"example"}],"max_tokens":1,"temperature":0,"top_p":0,"stop":"example"}'

# Or just use the canonical runner — it handles the whole loop:
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/ai/chat'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.ai.chat({
  "model": "example",
  "messages": [
    {
      "role": "system",
      "content": "example"
    }
  ],
  "max_tokens": 1,
  "temperature": 0,
  "top_p": 0,
  "stop": "example"
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.ai.chat(model="example", messages=[{"role":"system","content":"example"}], max_tokens=1, temperature=0, top_p=0, stop="example")

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ai.chat",
    "arguments": {
      "model": "example",
      "messages": [
        {
          "role": "system",
          "content": "example"
        }
      ],
      "max_tokens": 1,
      "temperature": 0,
      "top_p": 0,
      "stop": "example"
    }
  }
}

FAQ

Do I need an API key to use the chat API?
No. ai.chat is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the chat API cost?
Pricing is dynamic: the exact amount is computed per request and quoted in the 402 challenge before you pay (from $0.0010 USDC). There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call ai.chat from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: chat api · ai chat api · chat api for ai agents · x402 ai api · chat api no api key · pay per call chat api · ai api