The Snyk AiBom API exposes 4 operations. It is one of 48 APIs that Snyk publishes on the network, described by a machine-readable OpenAPI specification, served from api.snyk.io/rest.
Four operations is a small API. The category it represents is not small at all.
AIBOM is SBOM asked about a harder dependency
A Software Bill of Materials answers what is in this build — which packages, which versions, which licenses, which known vulnerabilities. Fifteen years of tooling, a regulatory mandate in several jurisdictions, and a mature answer.
An AI Bill of Materials asks the same question about a model. Which model, which weights, which version, which license, which training data, which fine-tune, which provider, and what happens to your obligations when any of those change underneath you.
Almost nobody can answer it. Most organisations running models in production could not produce an inventory of which models, at which versions, are reachable from which services — the exact question SBOM tooling answers routinely for npm packages.
Where it sits in Snyk’s surface
The AiBom API is one entry in a 48-API estate that reads like a well-decomposed security platform:
- SBOM and AiBom — inventory
- Findings, Issues, Issues Export — what is wrong
- Container Image, Container Registry Import Policy, Custom Base Images — the container path
- Broker Connections / Contexts / Deployments — the on-prem bridge
- Audit Logs, Access Requests, Apps (OAuth) — the governance and integration layer
One resource per API, one OpenAPI per resource. This is what a refined surface looks like: you can reason about which contract you need without reading a 4,000-line monolith.
Snyk also publishes a GraphQL schema alongside the REST contracts, and documentation broken out per tag — Orgs, Projects, Issues, Targets, Integrations, Audit Logs, SBOM, Container Images, Webhooks.
The honest limitation
Four operations will not give you a defensible AI inventory on its own. What an AIBOM needs to be useful is the same thing an SBOM needed: universal generation at build time, a standard format everyone emits, and a consumer that fails a pipeline when the inventory does not match policy.
SBOM got there through CycloneDX and SPDX plus a decade of pressure. AIBOM has no settled format and no mandate. This API is an early bet that one is coming.
That is the right bet. The AI supply chain has all the properties that made the software supply chain a problem — deep transitive dependencies, opaque provenance, license terms nobody reads, and updates that ship underneath you — with less tooling and more regulatory attention arriving.
Takeaway
Four operations against the inventory question that every organisation running AI in production will be asked and most cannot currently answer. It is early, the format war has not been fought, and Snyk is publishing the contract before the standard exists.
Read the docs at apidocs.snyk.io, and see the provider entry at apis.io/providers/snyk/.