Atomic Agents

In this catalog it is the Frameworks option when you need to compose multi-step agent loops and tool handoffs. Keep Atomic Agents on the observe/propose side of the loop: useful signals and drafts, with human or policy authority still required before anything irreversible runs.

Atomic Agents composes small Pydantic-schema agents — each atom has typed I/O instead of a monolithic agent class.

1. Define atomic agents with Pydantic input/output schemas.
2. Wire atoms into a pipeline / graph of calls.
3. Validate every hop; fail closed on schema mismatch.
4. Emit the final typed object to the host.

Related: pydantic-ai · mirascope · topics/12-central-nervous-system

• Use when: Atomic Agents is a lightweight Python framework that uses Pydantic schemas for small, composable agent components rather than monolithic agent classes matches the bottleneck and you specifically need to compose multi-step agent loops and tool handoffs.
• Skip when: another pack already covers the need with less ops surface, or Atomic Agents would become a second place people retype truth.
• Prefer instead: compare Pydantic AI, Mirascope before locking the cell.

• Ops: confirm license, hosting, and release cadence for Atomic Agents (Eigenwise/atomic-agents) before relying on it in a live corridor.
• Integration: bad credentials, scopes, or schema drift produce empty retrievals or runaway tool/model spend without an obvious UI alarm.
• Scope: Frameworks components support agents; they are not the company ledger or the approval authority.