The API-BOM
The inventory of every endpoint your applications actually serve, including the shadow, zombie, and undocumented ones.
Use case · AI-BOM & API-BOM
An SBOM tells you what you built. Not what's exposed.
An SBOM lists your libraries, packages, and versions. It does not tell you what is actually exposed and reachable at runtime.
The AI-BOM
The same discipline applied to AI: the models, agents, MCP servers, and third-party AI services your applications call.
Neither is a separate framework. The SBOM covers the supply chain you assembled; the API-BOM and AI-BOM cover the attack surface you published.
How Surface builds them
Outside-in, against what's actually running.
Surface builds both for you. It works outside-in against your live environment, so it finds what is running rather than what a repo claims should be. The output is a continuously refreshed inventory: every endpoint and AI asset, its authentication posture, whether it appears in any documentation, and whether it has ever been tested for exploitability. No agents, no spec files, no engineering tickets.
This is the prerequisite for everything downstream: you cannot test what you have not found.