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.

migrate-config-table - Prompt

Prompt file imported from robesonw/sampleT (.github/prompts/migrate-config-table.prompt.md). Fill in {{apiName}} before use. Copyright stays with the author.

Migrate the legacy mock configuration for {{apiName}} from our existing config-table/stored-proc service into API Simulation Platform.

This supports Principle 7 (migrate, never big-bang) — the legacy mocks must keep working while we move.

Steps:

Use the spec-ingest config-table importer to read the legacy entries and produce a valid MockDefinition. Report anything that doesn't map cleanly.
Where the legacy mock relied on a data-prep stored proc, replace it with data-engine data pools or synthetic generation — capture the shapes the proc produced, not the SQL itself.
Mask any PII found in legacy sample data before persisting it.
Produce the mock-as-code files and verify the migrated mock behaves equivalently to the legacy one for a few representative requests.
Summarize: what migrated cleanly, what needs a human decision, and the diff vs. legacy behavior.

Do not reproduce stored-proc SQL. Do not break the legacy service.

Migrate the legacy mock configuration for `{{apiName}}` from our existing config-table/stored-proc service into API Simulation Platform. This supports Principle 7 (migrate, never big-bang) — the legacy mocks must keep working while we move. Steps: 1. Use the `spec-ingest` config-table importer to read the legacy entries and produce a valid `MockDefinition`. Report anything that doesn't map cleanly. 2. Where the legacy mock relied on a data-prep stored proc, replace it with `data-engine` data pools or synthetic generation — capture the shapes the proc produced, not the SQL itself. 3. Mask any PII found in legacy sample data before persisting it. 4. Produce the mock-as-code files and verify the migrated mock behaves equivalently to the legacy one for a few representative requests. 5. Summarize: what migrated cleanly, what needs a human decision, and the diff vs. legacy behavior. Do not reproduce stored-proc SQL. Do not break the legacy service.

Install migrate-config-table 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.

migrate-config-table

About

Use it

Install migrate-config-table 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

Manifest

Reviews