mocop
Browse · Docs · Guide · Analyze

A2UI Atomic Catalog

API by A2uicatalog · rest

573 typed UI atoms an agent composes into real rendered interfaces — charts, gauges, steppers, dashboards — across 13 surfaces including web, Google Meet, Apps Script, Google Chat and MCP Apps hosts. The agent names a component from a fixed vocabulary; a renderer that already knows that component draws it, so no HTML is ever generated by the model. The primary integration surface is the MCP (Model Context Protocol) server at /mcp, which exposes its tools over JSON-RPC 2.0. The REST paths documented here are the supporting surfaces: the machine-readable catalog, the declared data proxy, and the natural language composer. No API key, no signup, no OAuth required for normal use. Versioning The wire-format version is carried in an X-API-Version response header (currently 1), not a URL path prefix — the MCP endpoint URL lives in users' client config files and moving it would break every existing integration. Additive changes (new atoms, tools, optional fields) ship without…

Endpoint: https://a2uicatalog.ai/

Verification: observed. Source: crawl.

Capabilities (17)

  • Agentic Resource Discovery catalog (legacy alias)
  • Agentic Resource Discovery catalog (ARD v0.91 canonical path)
  • Natural language to atom blocks
  • Declared data-source proxy
  • A2UI payload to HTML
  • Render many payloads in one call
  • Render as an async job (202 Accepted then poll)
  • Render job status
  • Render job result
  • NLWeb natural-language catalog search (GET)
  • NLWeb natural-language catalog search (POST)
  • Strict per-atom JSON Schema
  • Catalog selection menu
  • Server descriptor
  • MCP JSON-RPC 2.0 endpoint
  • Published short link
  • Full atom vocabulary
About · Contact · Privacy