OpenAPI acceptance corpus

For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

OpenAPI acceptance corpus

MongoDB Atlas Agent Engine is in Public Preview and intended for evaluation and prototyping purposes only. We do not recommend production deployments during preview and expect to communicate breaking changes with you periodically. To learn more about preview feature considerations, see Preview Features.

manifest.json is the executable product boundary for OpenAPI generation. It pins exactly 100 APIs.guru documents by URL and SHA-256 and records the declared operation count, accepted authentication presentation, and minimum compiled operation count for each document.

The set was curated from the APIs.guru index retrieved on 2026-09-15. Here, “popular” means recognizable APIs that developers are likely to connect to agents, not an objective download ranking: the first group emphasizes widely used developer services, and the remainder broadens provider and OpenAPI representation coverage. Provider identities are unique so one vendor cannot dominate the result. Changing the membership, fixed totals, or selection policy requires product review.

Fetch and run the strict gate from the repository root:

./scripts/test.sh agent-engine-runner-shared-corpus

The fetched documents are intentionally untracked. A normal unit run validates the manifest but skips document compilation when specs/ is absent. The strict selector fetches every document, rejects digest drift or an incomplete fixture set, and then runs all corpus cases.

Minimums ratchet upward. Lowering one requires a reviewed soundness explanation showing why the previously generated operation could not be executed faithfully. Unsupported operations are acceptable only when skip_unsupported records the reason in catalog provenance.