Migrate and build
OpenAI drop-in replacement
Move an existing OpenAI app onto Roadie by changing two lines — the base URL and the key —
in Node and Python. Keep streaming, tools, embeddings, and images.
Build a Node chat backend
Stand up a server-side chat + embeddings service on
@roadie/sdk, with streaming, end-user
attribution, typed errors, and feedback.Ship a mobile app
AI image enhance on iOS
The real Create Pro flow: draw, select a region, describe it, and get an edited image back
from
images.edit — with RoadieKit and no provider key in the app.App Attest device sign-in
Authenticate each device silently with Apple App Attest — no login screen, no shipped secret
— and mint a per-device client token.
Free → Pro with StoreKit
Sell a subscription with StoreKit, verify it on your backend, and flip the device’s plan to
pro with a secret-key entitlement grant.Zero-backend federated identity
Ship an app with no backend of your own: exchange your existing Firebase / Auth0 / OIDC ID
token for a Roadie client token straight from the device.
Control and operate
Per-user limits
Give each end user their own rate limits and quotas, cap project spend with a budget, and
block an abuser instantly.
Cross-provider fallback
Configure a static, ordered fallback so an OpenAI outage transparently fails over to
Anthropic, and watch the circuit breaker do its work.
Automate with a management key
Script the control plane from CI with an
rd_mk_ management key — read projects, set a quota,
pull usage.Observability
Pull per-user usage, cost, and request logs from the control-plane API and the dashboard.
Before you start
Every tutorial assumes you have a Roadie project with at least one provider credential (your OpenAI or Anthropic key — BYOK) and the right credential for the job:- A secret key (
rd_sk_…) for server-side code. - A publishable key (
rd_pk_…) for client apps that mint their own tokens. - A management key (
rd_mk_…) for control-plane automation.