Service Catalog & API Context · For Engineering
Deterministic static analysis builds a continuously fresh inventory of every service, API, field, and downstream consumer. Centralized across your org, or local on a single repo. Used by platform engineers, technical PMs, and AI coding agents.
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
The problem
The teams that need that picture most are improvising.
OpenAPI, protobuf, and GraphQL schemas tell you what an API is. They do not tell you which services call it, which fields are touched, or what fails when you change it.
The spreadsheet goes stale the moment a PR merges, and the next planning cycle starts from guesswork.
“Who calls this?” gets asked in Slack and answered with a half-remembered service name. The real answer lives across millions of lines and dozens of repos, with no one source of truth.
What you get
The catalog is built by ProtoMap, a deterministic static analyzer that reads your code on every pull request, with no manual data entry.
Every service in every repo, with language, protocol, and maintainers drawn from git history.
Every service, RPC, message, and field, extracted from protobuf files and the code that serves and calls them.
For every API, the exact list of services that call it and the line numbers where they call it. No grepping.
A directed graph of service-to-service relationships, queryable through the assistant, MCP, or a visual viewer.
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
Worked example
street_address on the shared Address messageHere’s an example based on the Google Cloud Online Boutique microservices demo (eleven polyglot microservices, gRPC over protobuf). The protobuf change is one line. The blast radius is what matters.
Ask ProtoMap about your code and data
List all gRPC services
Which services call <RPC method>?
What is the blast radius of changing <field name>?
One sender service, three receiver services, one repository. Each one needs a PR before street_address can be safely removed.
How freshness works
The catalog is regenerated from source on each PR, not on a schedule and not by hand. Nothing drifts.
A GitHub, GitLab, or Bitbucket integration runs ProtoMap against the diff and the working tree.
Parses gRPC today, with GraphQL and REST coming soon. Source languages: Python, JavaScript, TypeScript, C#, Go, Java, Swift, Rust, and Kotlin.
The catalog refreshes in place. AI agents and humans query the same source of truth through the assistant, MCP, or a web viewer.
No embeddings. No probabilistic recall. The analyzer is deterministic by design: two runs of the same commit produce identical catalogs.
Who reads the catalog
The catalog earns its keep before you ever turn on an AI coding agent. Three readers, one source of truth.
Pull request review, migration planning, deprecation hygiene, on-call investigations.
Org-wide service inventory, ownership clarity, what we ship to which customer segment. Replace the spreadsheet you keep apologizing for.
Claude Code, Cursor, Codex, and Copilot read the same catalog through a local MCP server. The catalog is what lets them reason about cross-repo change without grep-bombing.
Building this for your AI coding agents? See AI Coding Agent Context
Claude Code with Opus 5.5 at high effort, across 20 prompts on 9 gRPC repositories (5M LOC), with higher accuracy (100% vs. 98%). See the benchmarks
See it in action
10:53
Live demo · MozFest 2026
Live demo of HoundDog.ai’s ProtoMap at MozFest’s Open Source House: callers and callees, and the blast radius of changing a field name.
The same prompt in two live sessions: ProtoMap’s answers in 50 seconds for $0.40, the baseline’s in 6 minutes for $14.44.
Rollout
Install the self-hosted platform and CLI with Docker, scan your repositories, and query ProtoMap in plain English or over MCP. Free for code scanned on your machine.
git clone https://github.com/hounddogai/protomap.git
cd protomap
./self-hosted/scripts/install.sh
Enterprise keeps context current across every repository in your organization, so agents no longer clone repositories they don’t own.
Discovery vs. reasoning
AI agents are great at reasoning. They are an expensive and inefficient way to repeatedly rediscover deterministic facts about your codebase.
Without precomputed context, every agent has to search files, follow references, inspect protobuf definitions, and reconstruct dependencies before it can start on the actual problem. Across developers, prompts, and repositories, you pay for the same discovery again and again in tokens, latency, and compute.
HoundDog.ai separates discovery from reasoning. ProtoMap computes API, field, consumer, and service relationships deterministically, keeps them current as code changes, and makes that evidence available to your existing AI agents through MCP.
Compute the facts once. Keep them fresh. Let every authorized AI agent reason over them.
FAQ
Every service, API, field, and downstream consumer across your repos. Service owners, language and protocol, call sites, and cross-repo dependency edges are captured deterministically from the code.
A CI hook runs ProtoMap on every pull request. The catalog updates the moment code lands. There is no manual edit step, no spreadsheet to maintain, and no nightly batch that drifts behind the codebase.
Backstage is a developer portal. Its software catalog is built from catalog-info.yaml files that teams write and keep next to their code. Backstage can discover and register those files across your repositories automatically, but the contents are written by hand: which APIs a service provides and consumes, and what it depends on, are declared in YAML rather than extracted from the code. ProtoMap generates the catalog from the code itself, so the inventory and dependency map are accurate by construction rather than by discipline.
No. Analysis runs locally or inside your CI environment. Source code never leaves your infrastructure.
gRPC is supported today, with GraphQL and REST coming soon.
Install the self-hosted version for free. It runs on your machine with Docker, and your source code stays in your environment.
Paste into your coding agent
Set up ProtoMap and show me what it can do. ProtoMap maps gRPC services and protobuf messages across repositories, and gives coding agents that graph over MCP. Docs: https://docs.protomap.ai/quickstart/
Tell me what you are about to do before each step that installs something.
1. Check that this computer has git, Docker with Compose 2.23.1 or newer, at least 4 GB of RAM, and 20 GB of disk space. If anything is missing, tell me and stop.
2. Install ProtoMap Server, in a folder outside this repository:
git clone https://github.com/hounddogai/protomap.git
cd protomap
./self-hosted/scripts/install.sh
The installer asks questions. Choose Trial, which runs PostgreSQL locally and logs the CLI in, and keep the default port.
3. Show me the address and the one-time setup key the installer prints. Ask me to open the address, enter the key, and create my organization and owner account. Wait until I say that's done.
4. Scan this repository, from a new shell so the CLI is on the PATH:
protomap scan .
If it has no gRPC services in a supported language, tell me, and offer to scan a public example instead:
git clone https://github.com/GoogleCloudPlatform/microservices-demo.git
protomap scan microservices-demo
5. From the scanned repository's folder, add ProtoMap to yourself as an MCP server:
Claude Code: claude mcp add protomap -- protomap mcp serve
Codex: codex mcp add protomap -- protomap mcp serve
Antigravity: add "protomap": { "command": "protomap", "args": ["mcp", "serve"] } under mcpServers in ~/.gemini/config/mcp_config.json
Others: https://docs.protomap.ai/coding-agents/
Tell me if I need to restart you for it to take effect.
6. Tell me what the scan found, then use ProtoMap's tools to answer one question about my services, such as which services call a method and where. Suggest two more questions I could ask.