Ringside migration library

Migrating to Ringside in 5 minutes from any of these APIs. Pick your source:

• OpenAI Chat Completions → Ringside: Three-line diff. Swap base_url, add a user field, get per-end-customer billing attribution + webhooks + budgets + 19 providers behind one SDK. Target persona: Team Lead Tanya shipping a multi-tenant SaaS.
• OpenAI Assistants → Ringside: The flagship. Wire-compatible drop-in replacement for the Assistants API before OpenAI shuts it down on August 26, 2026. Two-line migration (base URL + key); every client.beta.threads.* and client.beta.assistants.* call keeps working. Target persona: teams with production Assistants code facing a hard deprecation.
• Anthropic Messages → Ringside: Use Claude behind the OpenAI SDK, plus 18 other providers, per-Customer billing, webhooks, Client Tokens, and margin reporting. Target persona: Anthropic-primary shops who want multi-provider without single-vendor ecosystem tax.
• OpenRouter → Ringside: Near-passthrough wire compatibility. The unique win: OpenRouter sells tokens, Ringside sells Customers. Get per-end-customer billing attribution, budgets, Client Tokens, conversation persistence and margin. Target persona: Solo-Dev Sam running a multi-provider app.
• Chatbase → Ringside: When you outgrow the no-code chatbot framework and need primitives. Keep your training docs, persona, and conversation history; gain 19 providers, per-Customer billing, SDK-level control, and full UI ownership. Target persona: founders graduating from no-code into a real product build.

Why migrate to Ringside

Four features, all absent from the APIs listed above, all production-critical:

1. Customer Object. Every call tags to an end-customer via user: "cus_xxx". Ringside tracks per-Customer usage, budgets, rate limits, and margin server-side with no database schema on your end.
2. Client Tokens. Short-lived Ed25519-signed JWTs pinned to a single Customer, with optional Origin allowlist and IP binding. Safe to hand to browsers, mobile apps and third-party integrations.
3. Webhooks. 13 event types (customer.budget_exceeded, wallet.low, run.completed, moderation.flagged, and more), HMAC-signed, retried with exponential backoff.
4. 19 providers, one URL. OpenAI, Anthropic, Google, Mistral, Groq, Together, Fireworks, Perplexity, DeepSeek, xAI, Cerebras, SambaNova, Cohere, OpenRouter, Ollama, Azure OpenAI, Bedrock, HuggingFace, Replicate. Swap models per-call or via slot:<alias>.

Plus: margin reporting, conversation persistence, canonical streaming + error taxonomy, JSON-schema fallback enforcement on non-native providers, and GDPR hard-delete.

Assistants API shutdown countdown

You have [COUNTDOWN_DAYS] days until OpenAI's Assistants API stops responding.

If your app uses client.beta.assistants.* or client.beta.threads.*, start with the Assistants → Ringside guide. The migration is two lines.

Live countdown + embedable widget: ringside.fightclub.pro/assistants.

Guide shape

Every guide follows the same skeleton so you know what to expect:

1. Hero: the one-paragraph pitch + headline code diff.
2. Why migrate: the 3-5 capabilities the source API lacks.
3. Step-by-step: sign up → token → base URL → attribution → deploy, in 5 minutes.
4. Drop-in code diffs: Python + Node side-by-side for the common call shapes.
5. Feature mapping: a table of origin-API feature → Ringside equivalent.
6. Gotchas: the known behavioural differences + how to handle them.
7. FAQ: 5 questions we actually hear.
8. Next steps + links: playground, docs, support, related migrations.

Not listed here?

Open an issue at github.com/fightclub/ringside-issues or email support@fightclub.pro with the source API you're coming from. We add migration guides on request. If you're asking, others are too.

Target migrations on the roadmap (v1.1):

• LangChain / LangGraph → Ringside
• LiteLLM → Ringside
• Portkey → Ringside
• Langflow → Ringside (DataStax sunset April 9, 2026)
• Vercel AI SDK → Ringside (native config doc, not a migration per se)

Support

• Free migration call (first 10 customers): book a 1-hour Zoom. We migrate your app live. Produces a working app + case study + permanent founding-customer pricing.
• Discord #migration channel: discord.gg/ringside. Founders answer personally for the first 6 months.
• Email: support@fightclub.pro (4-business-hour response).
• Bugs: github.com/fightclub/ringside-issues.

Corrections, feedback, or a migration guide request: chka@stratus5.com.