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.

coreex-api-e2e - Prompt - OpenSmartRoute

Name: coreex-api-e2e
Author: Avanade

Prompt file imported from Avanade/CoreEx (.github/prompts/coreex-api-e2e.prompt.md). Copyright stays with the author.

Guide this workspace through adding a complete new entity with CRUD API endpoints end-to-end.

Use .github/skills/coreex-api-e2e/SKILL.md and its referenced workflow as the authoritative workflow.

Operational contract:

Read the solution-root AGENTS.md Feature Configuration first (rop-enabled, outbox-enabled, data-provider — SqlServer / Postgres / Cosmos / None) and check whether src/*.Domain/ exists — do not ask questions already answered there.
Batch all interview questions into one turn: entity name, CRUD operations, key properties, identifier type, whether a business guard is needed, and (for any ref-data property) whether that reference-data type already exists.
Invoke L1 skills in sequence — coreex-refdata (only if a brand-new reference-data type was identified), coreex-aggregate (only when *.Domain project exists), coreex-contract, coreex-db-migration, coreex-repository, coreex-validator, optionally coreex-policy, coreex-app-service, coreex-api, coreex-test-api — passing resolved context so no L1 re-asks what was already answered.
Decide the identifier type once, upfront — pass the same value to coreex-aggregate (TId) and coreex-contract (IIdentifier<T>).
Skip migration and repository when data-provider = None.
If any prompt text conflicts with the skill, the skill wins.

Outcome:

A complete vertical slice from database table to HTTP endpoint is in place, with unit tests for the validator (and policy if applicable) and integration tests for all operations.

Install coreex-api-e2e 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.

Guide this workspace through adding a complete new entity with CRUD API endpoints end-to-end. Use `.github/skills/coreex-api-e2e/SKILL.md` and its referenced workflow as the authoritative workflow. Operational contract: - Read the solution-root `AGENTS.md` **Feature Configuration** first (`rop-enabled`, `outbox-enabled`, `data-provider` — `SqlServer` / `Postgres` / `Cosmos` / `None`) and check whether `src/*.Domain/` exists — do not ask questions already answered there. - Batch all interview questions into one turn: entity name, CRUD operations, key properties, identifier type, whether a business guard is needed, and (for any ref-data property) whether that reference-data type already exists. - Invoke L1 skills in sequence — `coreex-refdata` (only if a brand-new reference-data type was identified), `coreex-aggregate` (only when `*.Domain` project exists), `coreex-contract`, `coreex-db-migration`, `coreex-repository`, `coreex-validator`, optionally `coreex-policy`, `coreex-app-service`, `coreex-api`, `coreex-test-api` — passing resolved context so no L1 re-asks what was already answered. - Decide the identifier type once, upfront — pass the same value to `coreex-aggregate` (`TId`) and `coreex-contract` (`IIdentifier<T>`). - Skip migration and repository when `data-provider = None`. - If any prompt text conflicts with the skill, the skill wins. Outcome: - A complete vertical slice from database table to HTTP endpoint is in place, with unit tests for the validator (and policy if applicable) and integration tests for all operations.

{ "prompt": "\n\nGuide this workspace through adding a complete new entity with CRUD API endpoints end-to-end.\n\nUse `.github/skills/coreex-api-e2e/SKILL.md` and its referenced workflow as the authoritative workflow.\n\nOperational contract:\n- Read the solution-root `AGENTS.md` **Feature Configuration** first (`rop-enabled`, `outbox-enabled`, `data-provider` — `SqlServer` / `Postgres` / `Cosmos` / `None`) and check whether `src/*.Domain/` exists — do not ask questions already answered there.\n- Batch all interview questions into one turn: entity name, CRUD operations, key properties, identifier type, whether a business guard is needed, and (for any ref-data property) whether that reference-data type already exists.\n- Invoke L1 skills in sequence — `coreex-refdata` (only if a brand-new reference-data type was identified), `coreex-aggregate` (only when `*.Domain` project exists), `coreex-contract`, `coreex-db-migration`, `coreex-repository`, `coreex-validator`, optionally `coreex-policy`, `coreex-app-service`, `coreex-api`, `coreex-test-api` — passing resolved context so no L1 re-asks what was already answered.\n- Decide the identifier type once, upfront — pass the same value to `coreex-aggregate` (`TId`) and `coreex-contract` (`IIdentifier<T>`).\n- Skip migration and repository when `data-provider = None`.\n- If any prompt text conflicts with the skill, the skill wins.\n\nOutcome:\n- A complete vertical slice from database table to HTTP endpoint is in place, with unit tests for the validator (and policy if applicable) and integration tests for all operations.", "variables": [], "notes": "Add a complete new entity with CRUD API endpoints end-to-end — contract, migration, repository, validator, optional policy, app-service, API controller, and integration tests in one guided workflow", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/Avanade/CoreEx", "path": ".github/prompts/coreex-api-e2e.prompt.md", "ref": "2a0ba32a24e10ad109bd51608bcd26fb063effa4", "url": "https://github.com/Avanade/CoreEx/blob/2a0ba32a24e10ad109bd51608bcd26fb063effa4/.github/prompts/coreex-api-e2e.prompt.md", "key": "Avanade/CoreEx/.github/prompts/coreex-api-e2e.prompt.md" } } }

coreex-api-e2e

About

Use it

Install coreex-api-e2e 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