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.

README - Agent - OpenSmartRoute

Name: README
Author: izzywdev

Claude Code subagent imported from izzywdev/FuzeInfra (.claude/agents/README.md). Copyright stays with the author.

Domain agents

Single-responsibility agents for building features in FuzeInfra. Each agent owns one domain, hard-stops at its boundary, and is forbidden from grading the whole feature — it reports only its own slice. This exists because a monolithic feature-agent once reported "DONE/GREEN" while siblings (UI/tests) were unbuilt. Scoped agents that report an honest, scoped "done" are the guardrail.

Boundary = domain, not repo. Agents enforce scope; skills are procedure. This set mirrors izzywdev/FuzeFront's domain-agent set, adapted for FuzeInfra.

The roles

Agent	Owns	Never touches
contract-designer	Frozen OpenAPI + event schemas + generated client, PR'd	Implementation of anything
backend-engineer	Services, APIs, DB, migrations + own unit tests	Contract, UI, acceptance tests, infra, docs
frontend-engineer	UI / dashboard / operator config surface	Backend, infra, tests, docs
test-engineer	INDEPENDENT acceptance/contract/integration tests	Implementing or fixing product code
devops-engineer	Helm chart/values, Argo, CI, kubeconform/helm-lint, reconciliation	Product code, UI, contract, product tests
docs-maintainer	Operator/onboarding docs only	Code, infra, tests, contract

Every agent consults the repo expert fuzeinfra-expert for conventions.

The mandatory DONE contract (non-negotiable)

No agent may ever declare the feature done. Each reports only its slice, in exactly this shape:

SCOPE DONE (verified): <what exists in MY domain and how I verified it>
OUT OF SCOPE — NOT DONE: <everything outside my domain> — owned by their agents.

If something can't be verified, the agent says so. "Tests pass" is only ever emitted by test-engineer, about tests it actually ran.

Orchestration sequence

contract-designer runs FIRST and alone — the sequential gate. It freezes the OpenAPI + event schemas + generated client and opens a PR. Nothing else starts until that contract is merged.
Once the contract is frozen, fan out the rest in parallel, gated only on the contract: backend-engineer, frontend-engineer, test-engineer, devops-engineer, docs-maintainer.
test-engineer is the independent grader — it tests against the spec, not the implementation, and reports real results. A failing acceptance test is a correct output, not a blocker to hide.
The orchestrator (not any single agent) assembles the slice-level "done" reports to judge whether the feature is actually complete.

                 contract-designer  (sequential gate: freeze + PR contract)
                          │
        ┌──────────┬──────┴───────┬───────────────┬─────────────┐
backend-engineer  frontend-eng  test-engineer  devops-engineer  docs-maintainer
   (impl+unit)     (UI/dash)    (independent)   (chart/Argo/CI)    (operator docs)

FuzeInfra platform facts every agent honors

Dual delivery: local docker-compose.FuzeInfra.yml and Helm chart at helm/fuzeinfra (Argo CD).
GitOps prod / self-heal (selfHeal: true): change git, let Argo reconcile — never kubectl patch/edit live resources.
Ingress: Traefik → ClusterIP, Cloudflare-tunnel-only (no public LoadBalancer/NodePort).
Validation: helm lint + kubeconform -strict -ignore-missing-schemas (per .github/workflows/helm-validate.yml).
CI secrets: alphanumeric-only passwords.

Install README 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": "izzywdev-fuzeinfra-readme-subagent", "kind": "agent", "name": "README", "description": "Single-responsibility agents for building features in FuzeInfra. Each agent owns **one domain**, hard-stops at its boundary, and is **forbidden from grading the whole feature** — it reports only its own slice. This exists because a monolithic feature-agent once reported \"DONE/GREEN\" while siblings (UI/tests) were unbuilt. Scoped agents that report an honest, scoped \"done\" are the guardrail.", "publisher": "izzywdev", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "agent-md", "github-claude-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Single-responsibility agents for building features in FuzeInfra. Each agent owns **one domain**, hard-stops at its boundary, and is **forbidden from grading the whole feature** — it reports only its own slice. This exists because a monolithic feature-agent once reported \"DONE/GREEN\" while siblings (UI/tests) were unbuilt. Scoped agents that report an honest, scoped \"done\" are the guardrail." ], "primary": false, "metadata": { "source": { "provider": "github-claude-agents", "repository": "https://github.com/izzywdev/FuzeInfra", "path": ".claude/agents/README.md", "ref": "1049b7f0923967ea4c771bf362816ea4765beef1", "url": "https://github.com/izzywdev/FuzeInfra/blob/1049b7f0923967ea4c771bf362816ea4765beef1/.claude/agents/README.md", "key": "izzywdev/FuzeInfra/.claude/agents/README.md" } }, "instructions": "# Domain agents\n\nSingle-responsibility agents for building features in FuzeInfra. Each agent owns\n**one domain**, hard-stops at its boundary, and is **forbidden from grading the\nwhole feature** — it reports only its own slice. This exists because a monolithic\nfeature-agent once reported \"DONE/GREEN\" while siblings (UI/tests) were unbuilt.\nScoped agents that report an honest, scoped \"done\" are the guardrail.\n\n> Boundary = **domain, not repo**. Agents *enforce scope*; skills are *procedure*.\n> This set mirrors `izzywdev/FuzeFront`'s domain-agent set, adapted for FuzeInfra.\n\n## The roles\n\n| Agent", "cost": { "context_tokens": 877 } }

README

About

Domain agents

The roles

The mandatory DONE contract (non-negotiable)

Orchestration sequence

FuzeInfra platform facts every agent honors

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