by Microservice.MD by Koesion.comCommunityGive AgentOne your microservice catalog: specs, API and event contracts, and what breaks when a service changes.
Microservice.MD connects AgentOne to your microservice.md catalog, so it can work from your actual service designs instead of guessing from the code in one repo.
Each service in your catalog has a MICROSERVICE.md spec and a set of generated files: OpenAPI, AsyncAPI, proto and GraphQL contracts, runbooks, ADRs, C4 diagrams and a context pack. AgentOne can read all of them, including the contracts of the services yours depends on, before it writes code that calls or consumes them.
It also answers the question that matters before a breaking change: what else does this affect? AgentOne can look up which services publish or consume an event, and which services depend on a given service, including the endpoints they call when those are recorded. It then tells you which services and teams are involved.
What you can do:
Access is read-only. You sign in with OAuth, AgentOne sees only your own catalog, and it reads your last saved versions by default. If a service has unsaved edits, AgentOne tells you they aren't included.
A microservice.md account is required.
monday.com project management and CRM for projects, tasks, portfolios, boards, workflows, milestones, dependencies, forms, dashboards, cross-project portfolio status, and critical paths.
by monday.com
Manage databases, authentication, and storage
by Supabase
Access and create new content on Miro boards
by Miro