> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://api.docs.siftsy.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://api.docs.siftsy.com/_mcp/server.

## 1.4.1

Documentation only — no API behavior changed.

* **Adding content is a core concept, separate from the read pipeline.** The [Overview](/guides/get-started/overview) keeps Select → Analyze → Comments as the three-step read path and adds a distinct **Adding content** section for the write path (`POST /content/…` → job → posts process → readable), with its own guide card. In the sidebar it follows Retrieving comments, after the read-pipeline pages.
* [Adding content](/guides/core-concepts/adding-content#how-adding-content-works) now walks through the ingest process end to end: the order of operations for `POST /content/posts/add` (validate → target team → collections → replay → dedupe → fund check → reserve + create → queue) and for `POST /content/accounts/add` (request-side steps, then discover → filter → add in a worker), plus a post-lifecycle table showing which statuses reserve, consume, or refund a credit and when a post becomes readable. The two POST operations in the API reference summarize the same order.
* [Authentication](/guides/core-concepts/authentication) and the [Quickstart](/guides/get-started/quickstart) now state the plan requirement (Powerhouse / Enterprise) and describe key management: create, rotate, revoke, scope toggles, and the usage view.
* [Rate limits](/guides/core-concepts/rate-limits) gains a **Usage history** section explaining what Team Settings → API shows and how it relates to the daily budgets.
* `Post.addedVia` is fully enumerated in the reference: `dashboard`, `api`, or `automation` (posts pulled in by a Siftsy Automation on a schedule). Previously `automation` was returned but not listed. [BI sync](/guides/core-concepts/bi-sync) documents the field alongside `addedByEmail`.
* The API reference description notes the plan requirement.