Skip to content
Benchmark

Changelog

Benchmark is actively building toward a stable v1. The capabilities below are available in the evolving v1 surface, but breaking changes remain possible.

Week of Aug 31, 2026

  • Basic and Enriched entity reads — Read profiles, posts, and public web links through separate Basic and Enriched views. Responses report freshness, data level, and completeness without exposing stored media locations or transcript contents.

  • Refreshes and collections — Request Basic data or a supported Enriched output asynchronously, receive a collection ID, and poll the collection for queued, running, complete, or failed status. Missing-data responses can point to the refresh request needed to create the requested view.

  • Profile history and social listening — Request a profile’s post history and read it page by page. It is separate from a normal profile read. A history refresh collects Basic post data and does not download post media.

  • Subscriptions and webhooks — List recurring refresh subscriptions through the API or CLI. Subscriptions are paused in this release, so they do not start refreshes. There is no public create or deactivate operation yet. When a workspace has a webhook configured, Benchmark can send a signed notification when a collection completes.

  • Social and link coverage — Acquire profiles and posts from Instagram, TikTok, YouTube, and X, including distinct social post subtypes such as reels, Shorts, photo posts, threads, replies, and quotes. Approved public HTTPS links can be refreshed into a normalized current page record.

  • Structured content analysis — Enriched post and link responses include safe nested analysis for the whole post or link, its post items, and supported media. A post keeps its first completed analysis. A changed link reports when its analysis is outdated. Public responses never include stored media, transcript text, prompts, or model details.

  • API and CLI access — Use the HTTP API or the matching CLI for entity reads, refreshes, collections, subscription listing, and profile history. Manage API keys in the dashboard. Every operation uses the same validation, authentication, rate-limit, and error responses.