/api/docs

Catalog API and Public Artifacts

The catalog is a public read-only API and MCP server. Every result is backed by the same schema-validated generated catalog used to render the UI, with its recorded generation timestamp preserved.

Repositories

207

Capabilities

49

Implementations

2,990

Validation failures

0

MCP Catalog Server

Public read-only JSON-RPC tools, resources, and prompts backed by the generated catalog evidence.

/api/mcp

Health

Public static health payload with generation status, validated manifests, discovery status, and route-contract status.

/api/health

Global Capability Index

Normalized reusable capabilities, implementations, recommended source, scores, risks, and source repositories.

/catalog/generated/capabilities.json

Repository Index

Repository summaries with language, framework, maturity, confidence, and capability counts.

/catalog/generated/repos.json

Search Index

Plain JSON search records for repositories, capabilities, tags, risks, source paths, and reuse metadata.

/catalog/generated/search-index.json

Graph

Node and edge graph connecting repositories to implemented capabilities.

/catalog/generated/graph.json

Best Implementations

Ranked candidate implementations for each global capability.

/catalog/generated/best-implementations.json

Vision Tool Selection

Browser, PlatPhorm Content, and PlatPhorm Docs mapped to evidence-backed catalog capabilities and privacy-defense mission tracks.

/catalog/generated/vision-tool-selection.json

Vision Evidence Pack

Preview-only JSON and Markdown-ready operator briefing generated from the tool selection and scaffolded controls.

/catalog/generated/vision-evidence-pack.json

Validation Report

Schema and evidence-path validation results for generated scans, manifests, and indexes.

/catalog/generated/validation-report.json

Dependency Census API

Evidence-backed npm dependency usage with repository and production-classification counts.

/api/v1/catalog/dependencies

Technology Census API

Inferred language/framework technology signal inventory from GitHub artifacts.

/api/v1/catalog/technologies

Catalog Scans API

Generated artifact and publication file inventory used by route contracts and artifact sync.

/api/v1/scans

Route Compliance API

Platform contract route checklist and protected-action metadata for this deployment.

/api/v1/route-compliance

Discovery Files
/api/health/api/v1/health/api/mcp/api/vision/capabilities/api/vision/evidence-pack/api/v1/catalog/census/api/v1/catalog/dependencies/api/v1/catalog/technologies/api/v1/catalog/publications/api/v1/catalog/publications/[filename]/api/v1/scans/api/v1/route-compliance/llms.txt/llms-full.txt/llms-index.json/openapi.yaml/openapi.json/sitemap.xml/sitemap-index.xml/rss.xml/feed.xml/atom.xml/robots.txt/.well-known/trust.json/.well-known/agents.json/.well-known/mcp.json/.well-known/ai-plugin.json/.well-known/security.txt
Static Contract
  • Public read-only catalog artifacts are served directly from the static Vercel output.
  • MCP search, detail, recommendation, resources, and prompts are public and read-only.
  • Catalog mutation endpoints are protected and require either API key auth or trusted OIDC tokens.
  • Protection controls now enforce auth before writes and trust checks are intentionally strict.
  • Source evidence is preserved as paths and summaries; secret values are not published.
  • Generated timestamps remain visible; verify a source repository before adopting a recommendation.
  • Use PLATPHORM_API_KEY for manual calls, or trusted OIDC from GitHub/Vercel workflows.