API and CLI

API overview

Use Conflux as one governed API layer across OpenAI-compatible and Anthropic-compatible clients.

Base URL

Production API traffic should use the API hostname.

https://api.yoiyoi.xyz

OpenAI-compatible endpoints

Use these when a client expects OpenAI-style APIs.

POST /v1/chat/completions
POST /v1/responses
GET  /v1/models

curl https://api.yoiyoi.xyz/v1/chat/completions \
  -H "Authorization: Bearer <CONFLUX_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "auto",
    "messages": [{ "role": "user", "content": "Explain the workspace memory graph." }]
  }'

Anthropic-compatible endpoint

Use this for Claude CLI and Anthropic-style message payloads.

POST /v1/messages

API keys

A Conflux API key belongs to a workspace and can be constrained by mode, model access, quota, and owner. Usage is recorded for analytics and quota accounting without deleting historical usage when a key is revoked.

Context-window recovery

Direct passthrough preserves the original client payload first. If the upstream model rejects the request for context-window size, Conflux can retry with audited context optimization for eligible intermediate tool output. The latest user instruction and client-native conversation memory are not treated as generic noise.