AgentRevati is a zero-dependency, strict-typed Python library that brings 11 production-tested patterns — recovery, lifecycle, permissions, cost tracking, circuit breaker — to your AI agent system. Framework-agnostic: works with CrewAI, LangGraph, AutoGen, or your own stack. Available to design partners, with public CI.
Zero dependencies
Pure Python stdlib only. No supply-chain risk, no version conflicts, no transitive surprises.
11 patterns out of the box
Recovery, lifecycle, permissions, policy engine, cost tracking, circuit breaker, green contract, task packets, hooks, compression, events.
Framework-agnostic
Drop-in compatible with CrewAI, LangGraph, AutoGen, Pydantic AI, or bespoke agents.
Type-safe
Strict mypy coverage with the py.typed marker. Catches errors at design time, not in production.
Built-in observability
OpenTelemetry events plus per-step cost tracking — production-ready from the first commit.
Available to design partners
MIT-licensed, Semantic Versioning, public CI. A pre-1.0 dev release we onboard via design-partner access — audit it, fork it, ship it.
Tech stack
- Python 3.11+
- PyPI
- OpenTelemetry
- mypy
- pytest
- MkDocs

Who it's for
Built for people who build agents.
Readable, low-dependency patterns you can adopt in an afternoon.
AI engineers
Reusable agent patterns you can read in an hour and drop into your stack.
Technical founders & CTOs
A dependable foundation for agent features, without framework lock-in.
Teams & consultancies
A shared vocabulary of patterns to standardise how your agents are built.
FAQ
Frequently asked questions
Why not just use my framework's built-in features?
AgentRevati complements them by adding the cross-cutting reliability and cost layer most frameworks leave to you. It stays portable, so it keeps working if you ever switch orchestrators.
Is it actively maintained?
It's a pre-1.0 dev release, MIT-licensed, with public CI, Semantic Versioning, and an open changelog. It's available to design partners rather than publicly published, so reach out for access and you can verify the activity yourself before adopting anything.
Stdlib-only with zero dependencies — is that really enough?
That's exactly the point: fewer moving parts means fewer failure modes and easier audits. You read the patterns, fork them, and ship them with no supply-chain risk.
Have a project in mind?
Tell us what you want to build. We respond within one business day.