Read your atom library as clean JSON over the content API

Spectare exposes every published atom as clean JSON at GET /api/content. A bare request with no credentials returns the Spectare library. A request carrying a Bearer org API key returns that organisation's own published content, so the WordPress plugin and the Next.js SSR helper can serve the same feed on your own domain rather than from spectare.ai.

The index response is an array of objects, each containing a stable slug, the atom title, a summary drawn from the first sentence of the body, the category, a lastUpdated timestamp, and a canonicalUrl. Fetch a single atom in full at /api/content/{slug}, which returns the same fields plus the complete markdown body. Numeric internal IDs and all personalisation metadata are intentionally excluded from both responses.

The stable slug is the right identifier to store in any integration. It will not change when content is edited, so cached references stay valid across updates. Because the endpoint requires no authentication for the Spectare library, any agent or crawler can fetch it without a credentials step.

The /api/content endpoint is documented in full on the API reference page at /docs, alongside the qualify and assemble endpoints. If you are building an agent integration, the qualify endpoint pairs naturally with the content feed: fetch content to understand what is available, then POST to qualify to get a personalised page URL for a specific user.