How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

api-types - Skill - OpenSmartRoute

Name: api-types
Author: supabase

Imported from supabase/supabase (.agents/skills/api-types/SKILL.md). Install upstream with npx skills add supabase/supabase --skill api-types. Copyright stays with the author.

API types

The generated API contract has three specs: API v1, API v2, and Platform. Their committed outputs are packages/api-types/types/api-v1.d.ts, packages/api-types/types/api-v2.d.ts, and packages/api-types/types/platform.d.ts.

Update types

Make the API/schema change and ensure it is deployed to production before relying on a type PR. Production is the merge-gate source of truth.
Update the committed types, either:
- Run pnpm api:codegen against a running local API environment. It fetches all three local OpenAPI specs and updates the committed files.
- Or, if you don't have a local API environment running, run pnpm api:codegen:prod. It fetches the three production OpenAPI specs directly and overwrites the committed files with them (no diffing — it always writes).
Inspect and commit only the intended generated type changes.
Run pnpm api:verify-types. It fetches the three production OpenAPI specs, regenerates types with the repository tooling, and compares them with the committed files.

Complete the update only when pnpm api:verify-types passes after the production deployment is available. If you used api:codegen:prod, this should already pass since the committed files came straight from production.

Interpret verification

A pass means the committed generated declarations match all three production specs at the time of the check.
A mismatch means production and the committed files differ. If the API is not deployed, deploy it and rerun the check. If production is correct, regenerate and review the changed files.
A fetch failure means the production schema endpoint could not be read; fix or retry the endpoint before treating the result as a type mismatch.

Pull requests

The Verify production API types CI job runs when packages/api-types/types/** changes and performs the same production comparison. It is a required merge check. Run the local verifier before requesting review and treat a failed CI verification as production drift that must be resolved.

Install api-types and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "supabase-supabase-api-types", "kind": "skill", "name": "api-types", "description": "Maintain Supabase API types. Use when changing generated API type declarations, OpenAPI schemas, or investigating API type deployment drift.", "publisher": "supabase", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Maintain Supabase API types. Use when changing generated API type declarations, OpenAPI schemas, or investigating API type deployment drift." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/supabase/supabase", "path": ".agents/skills/api-types/SKILL.md", "ref": "HEAD", "url": "https://github.com/supabase/supabase/blob/HEAD/.agents/skills/api-types/SKILL.md", "key": "supabase/supabase/.agents/skills/api-types/SKILL.md" } }, "instructions": "# API types\n\nThe generated API contract has three specs: API v1, API v2, and Platform. Their committed outputs are `packages/api-types/types/api-v1.d.ts`, `packages/api-types/types/api-v2.d.ts`, and `packages/api-types/types/platform.d.ts`.\n\n## Update types\n\n1. Make the API/schema change and ensure it is deployed to production before relying on a type PR. Production is the merge-gate source of truth.\n2. Update the committed types, either:\n - Run `pnpm api:codegen` against a running local API environment. It fetches all three local OpenAPI specs and updates the committed files.\n - Or, if you don't have a local API environment running, run `pnpm api:codegen:prod`. It fetches the three production OpenAPI specs directly and overwrites the committed files with them (no diffing — it always writes).\n3. Inspect and commit only the intended generated type changes.\n4. Run `pnpm api:verify-types`. It fetches the three production OpenAPI specs, regenerates types with the repository tooling, and compares them with the committed files.\n\nComplete the update only when `pnpm api:verify-types` passes after the production deployment is available. If you used `api:codegen:prod`, this should already pass since the committed files came straight from production.\n\n## Interpret verification\n\n- A pass means the committed generated declarations match all three production specs at the time of the check.\n- A mismatch means production and the committed files differ. If the API is not deployed, deploy it and rerun the check. If production is correct, regenerate and review the changed files.\n- A fetch failure means the production schema endpoint could not be read; fix or retry the endpoint before treating the result as a type mismatch.\n\n## Pull requests\n\nThe `Verify production API types` CI job runs when `packages/api-types/types/**` changes and performs the same production comparison. It is a required merge check. Run the local verifier before requesting review and treat a failed CI verification as production drift that must be resolved.", "cost": { "context_tokens": 511 } }

api-types

About

API types

Update types

Interpret verification

Pull requests

Install api-types and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews