OpenAI API vs Prism Inference

OpenAI API

Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026.

Prism Inference

Three wire formats, a public OpenAPI 3.1 file, per-token prices in a keyless catalogue and zero data retention by default on every tier. The service launched on 24 September 2026 with two models, one of them by request, from a two-person company. No rate-limit numbers, SLA document, free tier or deprecation policy was found.

OpenAI API

1. Build on the Responses API. Astra calls tools only there
2. Use gpt-6-luna for routing and extraction and gpt-6.1-sol for most work. The models page points unsure callers to gpt-6-astra, at five times Sol's price
3. Move off the gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro snapshots before 2026-12-11, and off gpt-5.1, gpt-5.3-codex and gpt-5.4-nano before 2027-04-01
4. Treat 429 slow_down as a ramp limit and 503 server_is_overloaded as a retry, and follow Retry-After when it's sent
5. Prompts over 272K tokens cost double on input. Trim before you pay for it

Prism Inference

1. Call GET https://api.prisminference.com/v1/models at start-up, with no key, and use only ids it returns. Expect 403 on gemma-4-31b without organisation access
2. Use base URL https://api.prisminference.com/v1 for OpenAI clients and https://api.prisminference.com with no /v1 for Anthropic clients
3. Read error.retryable before retrying, and wait for Retry-After on 429, which covers both key limits and model capacity
4. Send reasoning_effort: "none" or low when latency matters. Reasoning is on by default and its tokens are billed as output
5. Keep conversation state yourself and send store: false on Responses. previous_response_id, stored responses and hosted tools aren't supported