Catalog and Pulse
The Catalog is for deliberate search; Pulse is a multi-section recent-activity projection. Neither is an automatic approval of a project.
Catalog workflow
- Describe the outcome and constraints.
- Filter by the fields supported by the current view.
- Compare source, license, activity and operational fit.
- Open the upstream project and verify claims there.
- Test a bounded proof of concept with non-production data.
The public API exposes GET /api/catalog/top for a public discovery view and GET /api/catalog/search for eligible API-key or paid-session search. POST /api/catalog/solve accepts a task and returns the documented solution projection.
Pulse contract
GET /api/pulse returns independent sections for repositories, news, workflows, templates, skills, MCP, models and AI companies. A source failure can mark only that section unavailable, so clients should read each section's state, not assume the whole response is complete. Use types, limit and the section-specific cursor fields documented in Swagger.
curl --fail-with-body \
'https://public-api.atlasrepo.com/api/pulse?types=repositories,skills&limit=6'
GET /api/pulse/home is the compact home-page projection. Do not derive full-section totals from the number of cards rendered in a compact view.