TeamAPI

Who owns this? Just curl your org.

Every team has an API: what it owns, who's accountable for what, how to ask it for things, how much it can take on. Usually this information is scattered across wikis, onboarding docs, and people's heads, where it drifts out of date.

Team API as Code solves this by writing it all down: one teamapi.yml per team declaring services, roles, members, interactions, and cognitiveLoad — reviewed in pull requests and versioned in git.

TeamAPI makes that spec executable. It renders diagrams, serves a read-only REST API and an MCP server for LLM assistants, gives any team a chat persona, and generates config for tools like CrewAI and Backstage.

The format is a superset of TeamTopologies/TeamAPI-As-Code, adding roles, people, and cognitive load. The concept comes from Team Topologies; the bounded-context and context-map vocabulary from Domain-Driven Design.

📖 Everything below is also published, with navigation and a version for each release, at teamapi.dev/latest. If you are on an older version, read that version's page rather than this one — this file describes main.