# Blog

- Canonical collection: <https://hubset.live/blog>
- Detail pattern: `https://hubset.live/blog/{slug}`
- Public collection API: [`GET /api/posts`](https://hubset.live/api/posts)
- Public detail API: `GET /api/posts?slug={slug}`

## Purpose

Important updates from the agentic ecosystem, shaped into clear posts for builders. Use Blog as a research index for current developments, product changes, benchmark context, and useful linked sources. A featured or newest post leads the page; the remaining posts follow chronologically.

## Human-page behavior

- Search is client-side and searches title, cleaned excerpt, author, and tags.
- The current Blog page does not require a query parameter to traverse its content.
- A post can expose an original `source_url`; use the HubSet detail page for the curated post and the source URL for provenance.
- Blog is not a complete newswire. Check the post date and original source before relying on a time-sensitive claim, deal, or product capability.

## Record shape

Useful fields include `id`, `title`, `slug`, `excerpt`, `content`, `author`, `tags`, `image_url`, `source_url`, `created_at` or `date`, `featured`, and `status`. Treat optional fields as nullable and ignore unknown additive fields.

The detail renderer can contain rich HTML or Markdown-style content, images, tables, code, Mermaid diagrams, source embeds, and X/Twitter embeds. Prefer the API's structured record for ingestion and the human page for rendered reading.

Use a Blog post to understand the reported change and locate its source. Suggest relevant related HubSet sections to a human when the post points to a skill, repository, tutorial, AI access option, or benchmark; do not infer endorsements or current availability from a post alone.

## Navigation

- Post page: `/blog/{slug}`
- Legacy `/news` and `/news/{slug}` redirect to Blog and should not be emitted as canonical links.
- Back to [agent index](https://hubset.live/agent.md)
- See [content routes](https://hubset.live/agent/content-routes.md)