The living API catalog
Every scan turns your repo into a living catalog: scored, searchable collections that rebuild themselves on every push so what agents see is always what you shipped.
What a collection is
A collection is one API spec, plus everything Elva computes around it. Under the hood each collection carries:
- The stored spec (synthesized OpenAPI from a repo scan, or the file you imported), re-uploaded to storage only when its content hash changes.
- Computed insights — the overall score and A to F grade, per-category breakdowns, and error/warning counts.
- Embeddings of every operation, schema, and parameter so the AI assistant and semantic search can retrieve it.
That means a collection is never a static file dump. It is a scored, indexed, agent-queryable unit of your API surface.
How the catalog organizes itself
When Elva scans a repo, it does not drop one giant spec on you. It derives buckets and materializes each one as a collection, so your catalog mirrors how your system is actually built.
Repo shape | What Elva does |
No services detected | Collapses to a single All endpoints collection (only if endpoints exist) |
Normal service | One collection per service |
Large service | Splits into per-domain collections when it has 50+ endpoints across 3+ domains, keeping a Misc bucket so nothing is lost |
Same domain in several services | Merges into one repo-wide collection (for example, Users across core and frontend) |
On this page
- The living API catalog