AgentBreeder™ — v2.0
The only agent platform that doesn't pick a winner.
Build with anyone's framework. Deploy to anyone's cloud. Govern automatically. One YAML, one command — Apache 2.0, no vendor lock-in.
Quick Start · Install · Docs · Contributing
Your company has 47 AI agents. Nobody knows what they cost, who approved them, or which ones are still running. Three teams built the same summarizer. The security team hasn't audited any of them.
AgentBreeder fixes this.
Write one agent.yaml. Run agentbreeder deploy. Your agent is live — with RBAC, cost tracking, audit trail, and org-wide discoverability. Automatic. Not optional.
The Problem
AI coding tools make it easy to build agents. Nobody has made it easy to ship them responsibly.
| What happens today | What happens with AgentBreeder |
|---|---|
| Every framework has its own deploy story | One YAML, any framework, any cloud |
| No RBAC — anyone deploys anything | RBAC validated before the first container builds |
| No cost tracking — $40k surprise cloud bills | Cost attributed per team, per agent, per model |
| No audit trail — "who deployed that?" | Every deploy logged with who, what, when, where |
| No discoverability — duplicate agents everywhere | Org-wide registry — search before you build |
| Governance is bolted on after the fact | Governance is a structural side effect of deploying |
Governance is not configuration. It is a side effect of the pipeline. There is no way to skip it.
How It Works
Eight atomic steps run in sequence:
parse → RBAC check → *(approval gate if required)* → resolve deps → build container → provision infra → deploy → health check → register. If any step fails, the entire deploy rolls back.
Three Ways to Build
All three tiers compile to the same internal format. Same deploy pipeline. Same governance. No lock-in.
| Tier | Who | How | Eject to |
|---|---|---|---|
| No Code | PMs, analysts, citizen builders | Visual drag-and-drop canvas — pick model, tools, prompts from the registry | Low Code |
| Low Code | ML engineers, DevOps | Write agent.yaml in any IDE |
Full Code (agentbreeder eject) |
| Full Code | Senior engineers, researchers | Python/TS SDK with full programmatic control | — |
Use with Claude Code
Install the /agent-build architect as a Claude Code plugin:
claude plugin marketplace add agentbreeder/agentbreeder
claude plugin install agent-build@agentbreeder
Then run /agent-build in Claude Code to scaffold an agent (it recommends framework, model, memory, RAG, and deploy target, then generates agent.yaml + code).
Documentation
User docs (guides, references, examples) — agentbreeder.io/docs
| How-To guides | Install, deploy, orchestrate, evaluate |
| Quickstart | Full local platform in one command |
| Self-hosting | Run the platform on your own Kubernetes via Helm (deploy/helm/agentbreeder) |
| CLI reference | All commands and flags |
| SDK reference | Python + TypeScript full-code SDK |
For contributors — internal engineering references in this repo:
| Contributing | How to contribute — setup, standards, PR process |
| Architecture | Platform architecture — deploy pipeline, abstractions, data model |
| Design | Feature design docs — RBAC, LiteLLM gateway, polyglot agents |
Changelog · Roadmap · Issues · Discussions · Discord · Apache 2.0 · Trademark · Code of conduct · CLA · Security · Governance
Metadata
Release files for agentbreeder 2.7.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| agentbreeder-2.7.3.tar.gz | 8.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentbreeder-2.7.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.0 MB
Release files / agentbreeder-2.7.3.tar.gz
| Download URL | agentbreeder-2.7.3.tar.gz |
|---|---|
| Size | 8.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08dd19c49a1fb7103370e0c26d35021884b07966800fecf7d44ef19a9edddde3
|
|
BLAKE2b-256 checksum How to use checksums |
3cfcade41d1fc7320bbea3bf2b07ed6c79746cf09f80b27bac5f55455c443094
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logRelease files / agentbreeder-2.7.3-py3-none-any.whl
| Download URL | agentbreeder-2.7.3-py3-none-any.whl |
|---|---|
| Size | 971.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44cfa41f0da32d9e79c4539b48f03732b7031860a48150b5868cc6643af3dec1
|
|
BLAKE2b-256 checksum How to use checksums |
ae9935db99028d9b33b08633a5e0ac3823e4afae36d8a3dd9580b3d0856463e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logSecurity for agentbreeder 2.7.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agentbreeder-2.7.3.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.