Skip to main content

Discovery

ProductAtlas discovery is a two-step flow: search compact metadata, then retrieve the chosen immutable release.

What public search covers​

Text search covers title, summary, categories, tags, Publisher namespace, and Publisher display name. Exact filters can narrow by category, Publisher, trust badge code, license, and available section. Every supplied value in a filter group must match.

Public results exclude Drafts, withdrawn content, private assets, and confidential verification evidence. Results expose the latest eligible public release metadata and enough fields to choose the next retrieval:

  • namespacedId, title, summary, Publisher, and latest version
  • categories, trust badge codes, license, and available section keys
  • publication time and canonical resource URI

Search through MCP​

Call search_blueprints with outcome-oriented words rather than an assumed exact title. For example, use query: "incident investigation", then inspect the best matches. The default page contains 20 results and the service caps a request at 50. Continue only with the opaque nextCursor returned by the same search.

After selecting a match, call get_blueprint with its namespacedId. Start with summary, review the available sections, and request only the relevant section keys. This keeps agent context bounded.

Interpreting rank and trust​

Lexical relevance is the initial primary signal, followed by deterministic publication-time and identity ordering. Trust and popularity must not be treated as substitutes for relevance. A verified Publisher is an identity signal, not a quality guarantee, and a badge never means that the resulting implementation is secure or correct.