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.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

tdd - Prompt - OpenSmartRoute

Promptv1.0.0

tdd

Name: tdd
Author: sandialabs

Follow TalkPipe TDD workflow. Use when implementing features, fixing bugs, or adding segments/sources. Enforces write-fail-fix-pass order.

by sandialabs(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from sandialabs/talkpipe (.github/prompts/tdd.prompt.md). Copyright stays with the author.

Follow the TalkPipe TDD workflow for this change:

Write or update a test in tests/ that fails without the change. Prefer updating an existing test file over creating a new one.
Verify the test fails: run source .venv/bin/activate && pytest <test-file> -v
Implement the change
Verify the test passes: re-run the same pytest command

Constraints:

Tests mirror src/ structure under tests/talkpipe/
Keep tests as short as possible while covering the functionality completely
Use pytest.fixture and pytest-mock for dependencies
Always use the .venv environment; abort and alert if it doesn't exist

If a unit test is not reasonable (e.g., requires external LLM, is purely cosmetic), notify the user and explain why.

The change to implement: $input

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Follow the TalkPipe TDD workflow for this change:

1. **Write or update a test** in `tests/` that fails without the change. Prefer updating an existing test file over creating a new one.
2. **Verify the test fails**: run `source .venv/bin/activate && pytest <test-file> -v`
3. **Implement the change**
4. **Verify the test passes**: re-run the same pytest command

Constraints:
- Tests mirror `src/` structure under `tests/talkpipe/`
- Keep tests as short as possible while covering the functionality completely
- Use `pytest.fixture` and `pytest-mock` for dependencies
- Always use the `.venv` environment; abort and alert if it doesn't exist

If a unit test is not reasonable (e.g., requires external LLM, is purely cosmetic), notify the user and explain why.

The change to implement: $input

Installed into a catalogue, chosen by a router

Install tdd 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.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

sandialabs-talkpipe-tdd-prompt.prompt.jsonjson

{
  "prompt": "Follow the TalkPipe TDD workflow for this change:\n\n1. **Write or update a test** in `tests/` that fails without the change. Prefer updating an existing test file over creating a new one.\n2. **Verify the test fails**: run `source .venv/bin/activate && pytest <test-file> -v`\n3. **Implement the change**\n4. **Verify the test passes**: re-run the same pytest command\n\nConstraints:\n- Tests mirror `src/` structure under `tests/talkpipe/`\n- Keep tests as short as possible while covering the functionality completely\n- Use `pytest.fixture` and `pytest-mock` for dependencies\n- Always use the `.venv` environment; abort and alert if it doesn't exist\n\nIf a unit test is not reasonable (e.g., requires external LLM, is purely cosmetic), notify the user and explain why.\n\nThe change to implement: $input",
  "variables": [],
  "notes": "Follow TalkPipe TDD workflow. Use when implementing features, fixing bugs, or adding segments/sources. Enforces write-fail-fix-pass order. Mode: agent.",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/sandialabs/talkpipe",
      "path": ".github/prompts/tdd.prompt.md",
      "ref": "4b4d232612ef1a1d8008738f9c04c6caf9725c0a",
      "url": "https://github.com/sandialabs/talkpipe/blob/4b4d232612ef1a1d8008738f9c04c6caf9725c0a/.github/prompts/tdd.prompt.md",
      "key": "sandialabs/talkpipe/.github/prompts/tdd.prompt.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/sandialabs-talkpipe-tdd-prompt/manifest?version=1.0.0

About

Use it

Install tdd 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