# Publishing and delivery

Understand which content becomes available to websites and agents.

Refracto's Feed is a read-only delivery surface for a workspace's published content. It supports website and other client integrations; MCP lets agents read supported published content.

## Publication gates

The Feed uses the workspace's current publication and access rules. Unpublished or withdrawn briefings are not available through the ordinary published-content routes. When a briefing stops being live, its associated media is no longer available through those routes on subsequent requests.

An item may disappear between listing and reading it. Handle that response rather than displaying a cached item as if its current publication were confirmed.

## Keep states distinct

Content generation, editorial review, Feed availability and publication to a social network are separate outcomes. Verify each outcome required by your workflow. A successful API response does not confirm that a page on your website has updated.

## Integrate a website

Read [Feed API integration](/docs/feed-api), discover the current contract on your assigned endpoint and use only enabled features. Keep private credentials on your server.

## Integrate an agent

Read [MCP access](/docs/mcp). Use the tenant context and available tools returned by discovery. An agent can inspect existing published content; this interface does not grant workspace administration or content generation.
