Skip to main content
Within v1, Heralded adds routes, fields, MCP tools and enum values. Versioning states the rules. Each change appears here with its date.
  • 2026-11-13: An ecommerce report’s shopping.products adds appearances: your products’ appearances in organic product cards and each maker’s, most first, counted over every product shown rather than the capped products and shown_instead lists. It is null on sections written before it was counted.
  • 2026-11-13: New Products reads for ecommerce brands. GET /v1/brands/{brand_id}/products lists your products with the period’s product card figures, complete product data and revenue from AI, which is null without a Google Analytics read of purchases. Revenue from AI comes by assistant and by landing page, each page with the topics and questions whose answers cite it, and with one trend point per weekly read. /products/{product_id} reads one product’s trend, engines, questions, products shown instead, facts, cited pages and work. /products/sellers, /products/google-shopping and /products/readiness read the sellers shown, your Google Shopping positions and your product pages against Google’s and OpenAI’s standards. The MCP tool get_products reads the same.
  • 2026-11-13: An ecommerce brand’s work adds the retailer_distribution kind, work to get your products sold by a seller AI shows beside other brands’ products, and a product page’s markup fix, a site_fix on a page whose fix kit returns the Product markup to paste. GET /v1/brands/{brand_id}/evidence and list_evidence add the ecommerce module, with the kinds product_markup, markup_input, product_page, seller_opportunity and seller_exposure. Seller exposure and a markup field the catalogue holds no value for file no work, so handle evidence kinds you do not know.
  • 2026-11-12: A figure trend point’s instrument key adds shopping_pack_version: the version of the reading that judged an ecommerce report’s product cards, or null where the report read none. It is also a new value of a break’s parts, which only product card figures carry, so handle parts values you do not know.
  • 2026-11-12: Page types add product_detail, one item a shop sells, and collection, a shop’s listing of items for sale. GET /v1/brands/{brand_id}/audit/pages and GET /v1/scans/{scan_id}/audit/pages accept both as page_type and can return them on a page.
  • 2026-11-12: A report’s body adds products for a brand that sells products online, and null for any other: the shopping figures answers_with_cards, in_product_cards, seller_own and price_matches, the alerts the report saw on your products, and evidence, whether the shop’s catalogue and Google Shopping were read in complete, partial or unavailable form. Reports issued earlier return null.
  • 2026-11-12: Brands and scans say what they are measured as: mode is b2b_tech, or ecommerce for a brand selling goods to shoppers. GET /v1/brands returns it on each brand, GET /v1/brands/{brand_id}/profile and the get_brand_profile MCP tool on the profile, GET /v1/scans/{scan_id} on the scan, and the get_shared_snapshot MCP tool on the shared Snapshot. An ecommerce brand’s profile has no customer_size or service_area, and a change of mode is the mode part of a trend’s instrument key, which starts a new baseline.
  • 2026-11-11: Service Quick and Full audit reads include stack, with each detected tool’s name, category and page or DNS evidence. Stack detection does not change audit scores.
  • 2026-11-11: Service Quick and Full audit reads include screenshots: full-page desktop (1440 pixels wide) and phone (390) images of the audited URL, taken with JavaScript on and known consent banners declined, each with its url, width and height.
  • 2026-11-11: POST /v1/service/quick-audits and POST /v1/service/audits take an optional url, a full page address kept with its path and token, and preview, which leaves the indexing checks out of a draft’s score. GET /v1/service/audits/{scan_id} returns metrics once the audit completes: lcp_ms, page_weight_bytes, requests, performance_score, pages_read, ai_readable_pages and trackers_before_consent.
  • 2026-11-10: Editing a Snapshot’s profile with POST /v1/scans/{scan_id}/profile or the edit_snapshot tool no longer stops a run that is waiting: run_request.state stays requested, and the run starts on the profile as saved. A Snapshot writes its questions once Run is requested, so a profile nobody runs drafts none.
  • 2026-11-10: share_cards in GET /v1/shared/scans/{share_id} adds preview, the 1200 by 630 image a pasted report link shows. It appears with the other cards once a one-time Snapshot is final. The other cards stay 1200 by 1200.
  • 2026-11-09: Snapshot Your market figures carry gap, an estimate of how many more searches a month would show the brand in Google’s AI summary if it were named as often as its most-named competitor, with that competitor’s range. When the brand isn’t named, the verdict now lists the competitors that are. A sentence never names a brand the report hides. See Your market.
  • 2026-11-09: The Snapshot Your market figures in GET /v1/shared/scans/{share_id} carry llm_estimate, the search-like questions a month buyers ask ChatGPT, Gemini and Google AI Mode, with each engine’s ratio, and ad_value, what Google Ads would charge for the clicks the top result gets across those questions and the category’s Google searches, with the share of that demand AI answers. panels.llms shows whom those LLMs recommend, each engine weighed by its share of the questions, and searches_by_meaning groups the top searches that mean one thing into one row. Panels list only the report’s competitors. chatgpt_estimate, panels.openai, top_searches and demand.ad_value_usd/ad_value_eur stay until the report’s section reads the new fields.
  • 2026-11-09: The Snapshot Your market figures in GET /v1/shared/scans/{share_id} carry capture: what the brand holds today of the Google searches (google.clicks), the LLM questions (llms.questions) and the ad value (ad_value.usd/eur), each with its share of what the top spot would get. Each of searches_by_meaning carries your_rank, the brand’s best organic position, and ranks_read. The market constants move to v3, with the per-position click-through rates on pages with and without an AI answer.
  • 2026-11-09: In the Snapshot Your market figures, a top search whose Google AI summary names the brand shares the top spot evenly with the competitors the same summary names, in capture.google and capture.ad_value. The market constants move to v5.
  • 2026-11-09: In the Snapshot Your market figures, capture.google counts a top search whose Google AI summary names the brand as holding the top spot, as capture.llms counts a recommendation. Every checked AI summary is graded for who it names. Searches that name the report’s competitors leave the demand, the ad value and the top searches. The market constants move to v4.
  • 2026-11-09: Service audit reads include completed_at. Website findings include passed, true when a measured check passed and false when it failed or could not be measured. Passing Lighthouse checks say what the homepage does well. See Service audits and Website audits.
  • 2026-11-08: Weekly full Snapshots store Your market figures for your brand’s original market and All buyers audience, using existing research and tracked keyword checks. Market figures identify searches as top or tracked with searches_kind, and keep an unknown tracked search volume as null.
  • 2026-11-08: Full-access API keys and assistants run Snapshots. POST /v1/scans and MCP start_snapshot start one and return its drafted profile, POST /v1/scans/{scan_id}/profile and edit_snapshot correct it, /run and run_snapshot run it on your free Snapshot or a workspace credit, and /stop and stop_snapshot cancel a waiting run. GET /v1/scans/{scan_id} and get_scan add profile, run_request and payer, and there a Snapshot never run reads state: expired instead of failed with brief_abandoned. A write whose member cannot run work answers 403 forbidden with no scope challenge, and MCP refusals carry resets_at. See Run Snapshots.
  • 2026-11-08: Snapshot profiles returned by REST and MCP now include the category, buyer and competitors drafted so far. Competitors remain read-only. Scan reads and lists add report_url, a delivered Snapshot’s or weekly scan’s report page. Assistants are prompted to share the Snapshot page and expected run time, report live answer progress, and return the Heralded Score and report link when complete. See Run Snapshots and Connect an MCP client.
  • 2026-11-08: Signed-in Snapshot owners can edit, run and stop their waiting Snapshot from its profile link in another browser.
  • 2026-11-08: The shared Snapshot API and get_shared_snapshot assistant tool return the report’s stored Your market figures, with measured or estimated labels, ranges, top searches and the constants version.
  • 2026-11-08: Since 12 October, public leaderboards and MCP get_leaderboards return every source through position 20 and withhold all cited-page rows. Source rankings exclude brand sites by default; include_brand_sites=true includes them on filtered reads. GET /v1/leaderboards/hall-of-fame/sources and MCP get_leaderboards with resource=sources_hall_of_fame return source medals. See Leaderboards.
  • 2026-11-08: Added: Keywords, on Keywords and MCP get_keywords, add ai_overview_names_you and ai_overview_names_rivals: whether the latest check’s AI Overview names you, and which of your tracked rivals it names. Both are null where the page shows no AI Overview or its reading did not complete.
  • 2026-11-08: Changed: topic keywords no longer include one-off tasks with a provider, such as paying a phone or electricity bill or logging in, and two searches count as one only when they are close variants, not when their volumes match. Topic search demand drops where such searches were counted, so some Heralded Scores move from the next weekly report; issued reports keep their frozen weights. See Keywords.
  • 2026-11-08: API keys and assistant connections support Read only and Full access, with heralded:read and heralded:write scopes. Existing credentials stay read-only, and write refusals return an HTTP insufficient_scope challenge.
  • 2026-11-07: Studio removes legacy statement controls and review-fix undo. New pieces keep claim findings, passage highlights, comments and confirmations. Older drafts remain available for editing and approval.
  • 2026-11-06: Content reports include resolved questions. Answering a writer question posts one comment for that question; dismissing it leaves the draft unchanged. Page improvement orders accept an optional writer note.
  • 2026-11-06: Content language previews accept a page address. New pieces started from a bigger-change comment keep the original piece’s format and language, with Undo before the credit is spent.
  • 2026-11-06: New Snapshots, daily updates and weekly reports ask ChatGPT, Gemini, Google AI Overviews and Google AI Mode. Weekly reports can also ask Claude outside Europe where your plan includes it. Perplexity and Microsoft Copilot are retired; earlier reports keep their answers and history.
  • 2026-11-06: Content pieces in REST and MCP use ordering, researching_and_writing, applying_comments, your_review, approved, publishing, published, stopped, failed and paused. Brief and rewrite stages are removed. Older drafts remain readable and can still be approved. has_brief stays deprecated and is false on new pieces.
  • 2026-11-06: Content drafts show sentences the claim report could not confirm in Notes. Confirm a sentence for the current version, then choose whether to save it as a brand fact.
  • 2026-11-06: A topic’s Work list follows the topic pane’s selected period and filters. The Work page filtered to a topic keeps its four-report window.
  • 2026-11-06: Insight reads use topics, markets and audiences for every caller. Removed segment reads, Segment and Language filters, topic_market, tracked_topics, and subject IDs and segment fields from topic, question, keyword and source references. Question, question-fit and keyword writes accept tracked_topic_id. Measured language markers and Europe country breakdowns remain available.
  • 2026-11-06: Pooled Europe figures stay Calibrating when the earlier comparison window has no answers before the current window, instead of marking an existing brand as a first report.
  • 2026-11-06: Content pieces in REST and MCP support researching_and_writing and applying_comments stages and a report of questions, sources and references. Studio stages can also include the writer’s turn count without spend. has_brief is deprecated.
  • 2026-11-05: Work rows return focus: null when a brand has no starred topic or competitor; suggestions outside a configured focus still return the outside tag. See actions.
  • 2026-11-05: Understood is read part by part once a brand’s profile statements are split. In GET /v1/brands/{brand_id}/perception and /reputation, their claim reads and MCP get_perception and get_reputation, each profile claim row adds parts, each with its key, wording, quote, verdict counts and trend. facts_summary counts a split claim’s parts in its place. A figure trend point’s instrument key adds understood_measure, and Understood’s first report read part by part carries it in break.parts. See Understood.
  • 2026-11-05: Topic suggestions identify the suggestion and tracked topic to replace, and topic details include their selected engines. Market reads include Focus choices and Focus rows carry their market and audience. Keyword and Search comparison reads accept country separately from the topic’s market.
  • 2026-11-05: The Command Center assigns questions and keywords by tracked topic, preserving the topic’s market and audience.
  • 2026-11-05: GET /v1/brands/{brand_id}/topics and MCP get_topics return one item per tracked topic with its own id, market, audience and audience_id; topic_id keeps the shared subject. Insight market filters select the topic’s market, so a Romania selection excludes Romanian answers from Europe topics. audience selects an audience UUID or all_buyers. GET /v1/brands/{brand_id}/markets and /audiences, with MCP get_markets and get_audiences, replace public segment reads and MCP get_segments. See topics.
  • 2026-11-05: sites_total on GET /v1/brands/{brand_id}/cited-pages counts the sites AI cites, the sites whose pages it lists. found_via=ai_citation on GET /v1/brands/{brand_id}/sources keeps sites cited only in the baseline in its comparisons, and found_via applies to cited sites as well as uncited ones.
  • 2026-11-05: Shared Snapshot answers have unique positions within each engine across pages and pooled runs. Engine sites and citation counts are available through GET /v1/shared/scans/{share_id}/engines/{engine_id}/sites and MCP list_shared_engine_sites, with hidden competitors omitted.
  • 2026-11-05: Shared Snapshot answers return full Markdown in text, with text_highlights indexing that source. Hidden brands stay masked in text and links. Failing site checks include available fix steps.
  • 2026-11-05: Shared answers remove links to hidden brands while keeping safe labels readable. Understanding rows omit incomplete quotes, and competitor changes read Calibrating when your brand has earlier reports but no comparison score.
  • 2026-11-05: Scan list rows now include the Snapshot report’s market label. The Command Center shows it when a domain has runs in multiple markets.
  • 2026-11-05: Weekly report headlines describe the week behind; work counts appear under Next week. Work details and evidence return quoted AI passages as plain text.
  • 2026-11-05: Perception shows each profile statement’s parts, their agreement counts and gaps. Understood names the new measure on its trend, and the first weekly report using it carries a note.
  • 2026-11-05: List a managed brand’s Snapshots and their issued figures through GET /v1/brands/{brand_id}/snapshots with managed:read. Use managed:share on POST /v1/brands/{brand_id}/snapshots/{share_id}/share to get an unlisted link; revoked Snapshots stay revoked. See Managed Snapshots.
  • 2026-11-05: Topic previews and copies can select a market and audience from brand lists. Each tracked topic has its own name, star and tracking status. Topic focus IDs identify the tracked topic in its market and audience; topic_id identifies its shared subject. Europe reads topics with fewer than ten questions.
  • 2026-11-05: Plans count topics across your workspace and set a separate brand limit. Extra topics apply across brands after payment. Active topics keep reading above a limit. Organisation usage requires workspace settings or billing access. Manager allocation reads and writes use brands with 15 topics each; Usage and Billing show both capacities. Pending topic purchases keep their invoice link on Billing after a reload.
  • 2026-11-04: Weekly reports expose their own full Snapshot through scan_id on REST and MCP. Shared Snapshot reads include pdf_enabled; weekly runs start restricted to your brand’s report readers and can be made public from Share.
  • 2026-11-04: Shared question answers in REST and MCP include full masked text, text_highlights, and question-wide brands and pages counts. Cited links omit tracking parameters and combine matching URLs. Readability checks include group and plain labels. Snapshot positioning engine passages, flag titles and passages, and understanding-row quotes, values and gap notes mask hidden names and aliases. Flags exposing hidden names through their URL or domain are omitted, with matching flag counts. Robots.txt exclusions on query-string URLs do not produce blocked-page findings or actions.
  • 2026-11-04: Fact rows in the perception and reputation reads and MCP get_reputation split their counts into origins.probe, the answers to the fact’s own question, and origins.prompt, the answers to tracked prompts. They also name the definition_version they count and flag current_version_pending, and a claim trend sets definition_changed when its comparison would cross a change of meaning. A fact definition lists earlier_wordings, the wordings a typo fix replaced, and a fact’s trend is a new baseline while its comparison spans the first report that asked the fact its own question.
  • 2026-11-04: Review separate brand facts, their questions and agreement checks before saving in Strategy. Conflicting facts offer Keep both, Replace or Keep the existing one; replacements preserve identity and start a new definition. Perception fact reads include the current definition, author and next check date.
  • 2026-11-04: Brand profile facts and reputation fact definitions now include kind, comparison, probe question, definition version and author name. MCP get_reputation returns the same definitions and stays read-only.
  • 2026-11-04: Existing brand facts gain checks and questions without changing your wording. Compound facts offer a confirmed split in Strategy. Brand fact reads include split_candidates and interpretation_failed through the API and MCP.
  • 2026-11-04: The Command Center uses Question and Change consistently across tables and panels. Topic labels preserve AI, CRM and SEO, and Website findings spell out Total Blocking Time. The API uses question wording for low-quality tracking work and unmeasured topic reasons.
  • 2026-11-03: Action reads add job.failure, why a failed piece stopped, with job.stopped_at naming the step it reached. note.why_it_matters is one sentence that names the brand and the expected gain. An action’s title is its piece’s headline once the piece holds a draft. A pitch to a source is one action whichever segments cite it. REST, list_actions and get_action return the same. With with_viewer=true, the action’s viewer adds assigned_to_you.
  • 2026-11-03: List a workspace’s Snapshots with organization_id in GET /v1/scans or MCP get_scan. Snapshot owners can restrict or revoke report links from the share pane.
  • 2026-11-03: Brand look keeps default assets when a website logo or font cannot be fetched. Failed uploads still report a file error.
  • 2026-11-03: Setup starts with suggested competitors from your website and refuses your own brand or an owned website when you add a competitor.
  • 2026-11-03: Topic score sorts keep unscored topics last in either direction. Profile statements use Category, Audience, Offer and Difference, and Sources headlines distinguish cited sites from all discovered sites.
  • 2026-11-03: Competitor ranks, default leaderboard order and share of voice follow the selected side. Source panes count distinct read pages, answer summaries use Visibility’s measured population and pooled-market exclusions, and opinion changes compare the selected reports with their baseline. REST and MCP return the same figures, including mentioned_since, nullable unmeasured ranks and opinion change_detail.
  • 2026-11-03: Changing plans during a trial keeps its end date and charges nothing today. The expired founding offer is unavailable, and checkout status includes the number of credits added.
  • 2026-11-03: Setup links in the API read Automation and open the brand’s Automation settings page directly.
  • 2026-11-02: Each opinion quote from an AI answer carries answer_read_id and prompt_uid, in REST and MCP’s get_reputation, so the quote opens the answer and question it came from. Both are null for a quote from a page.
  • 2026-11-02: Topic, keyword, figure, engine and competitor panels open as full pages with paged sections, small figure trends and related Work. REST and MCP reads support compact previews and section paging; competitor-page Work targets the page’s exact URL.
  • 2026-11-02: Work panes show their evidence and steps, and long assets open in the full work page. The Assets view lists pieces, drafts and site changes by type, state and owner, also available through GET /v1/brands/{brand_id}/assets and the list_assets MCP tool. Action reads support compact previews and paged sections.
  • 2026-11-01: Question reads support compact previews with with_details=false and per-figure trends. Markets, Google searches, cited sites and leading brands have separate paging parameters.
  • 2026-11-01: The Home read and MCP get_weekly_brief include today’s decisions, team reviews, Heralded’s running work and suggestions with their reason and cost.
  • 2026-11-01: The week timeline API and MCP tool add daily summaries and a day filter for reading each day’s changes in lead order.
  • 2026-11-01: Competitor site moves read new and removed pages from each competitor’s own sitemap, and report a homepage or pricing change only when its headline or plans differ from the previous week’s. Moves from the vendor site map and key page hash changes no longer appear, and key_page_changed is no longer returned.
  • 2026-11-01: Sources uses the same listed-site total for its Sites tab and pagination, including after switching tabs. Perception’s facts summary includes profile claims. Competitor moves exclude watched-page hash changes.
  • 2026-10-31: The Website map API and get_site_map tool include citation counts for their pages. Use page to open a page’s language when language is unset. Citation counts are null when the citation measurement is unavailable.
  • 2026-10-31: Shared Snapshot reports add each competitor’s winning questions, engine results and citing sources, plus positioning readings by engine. Use the new get_shared_snapshot MCP tool to read the same evidence with a share id. See Shared report reads.
  • 2026-10-31: Perception and reputation headlines use a written statement when available, then the served figures. headline is now nullable on the Perception and reputation reads and is null when Understood has no measured value; the Perception page then omits it. See Perception.
  • 2026-10-31: Home headlines count the work in Needs you for the current reader. The weekly timeline shows observed changes and measured results, leaving out pending or unavailable checks.
  • 2026-10-31: Changed: competitor website changes on GET /v1/brands/{brand_id}/audit/competitors, /audit/competitors/{key}, MCP get_competitor_sites, and the competitor reads with with_details are the week’s moves, one per competitor and change type, each at its shallowest page. Add change to list each page of that type. Files such as PDFs and images no longer count as pages, in changes or in a competitor’s new, removed and weekly activity. See Competitor websites.
  • 2026-10-31: API and MCP links open the current Command Center pages, including Work, Strategy, Visibility, Competitors and Website. Route identifiers stay unchanged, and previously shared page links redirect.
  • 2026-10-31: Filter your Snapshot and Audit lists by domain with GET /v1/scans?domain=seedblink.com and GET /v1/audits?domain=seedblink.com.
  • 2026-10-31: Topic keywords, GET /v1/brands/{brand_id}/keywords and MCP get_keywords add source and replaced_by_next_add. The latter marks which researched keyword a member’s next add in that topic, segment and country would replace at the cap. See Keywords.
  • 2026-10-30: Website finding work adds status, the customer-facing stage from its work projection. insight.work identifies the canonical work returned by filing, including when a newer action also covers the finding. Insight filing results also carry status. See Website.
  • 2026-10-30: The brand’s Website pages read and MCP list_site_pages add headline, readable, with_findings and cited over the filtered population before paging. Rows add section and finding_ids. A null findings count means some matching pages were not measured. A null cited count means citation measurements are unavailable. Website’s headline summarizes page access and findings. See Website and Figures.
  • 2026-10-30: Perception and reputation reads and MCP tools add headline and facts_summary, with mostly_right, measured and insufficient_keys. Facts need three addressing answers and strictly more than half agreeing to count as mostly right. Reputation facts add insight, the actionable page and its existing work. Opinion evidence accepts pages_offset to page its holders. See Perception.
  • 2026-10-31: GET /v1/brands/{brand_id}/scores and MCP get_scores add headline, one sentence on how AI answers treat the brand under the read’s filters, and GET /v1/brands/{brand_id}/keywords and MCP get_keywords add headline, one sentence on the brand’s Google first-page rankings. Both come from templates with no model call, and are null while nothing is measured. See Filters and groups and Keywords.
  • 2026-10-31: Snapshot reports add leader to each scan.axes.by_prompt rollup, the brand recommended in the most answers to that question. It is null with fewer than two recommending answers, and hidden competitor names are not returned. See Shared report reads.
  • 2026-10-30: GET /v1/audits lists the Audits you ran, newest first, with id, state, domain, started_at, completed_at, progress_pct, failure_reason and, once delivered, share_id. See Scans.
  • 2026-10-30: GET /v1/shared/scans/{share_id}/questions/{query_id}/answers and MCP list_shared_question_answers add a shared question’s answers, 10 per page, with engine, run, strength marks, highlighted excerpts and citations. Snapshots name only their visible competitors and mask other names. See Shared report reads.
  • 2026-10-30: Topic and question reads and their MCP tools add measurement_status, first_answers_at and first_score_on. Questions keep their tracking status, and topics keep their tracking state. New topics sort first. See First answers and score.
  • 2026-10-30: Home adds three reads and MCP tools. weekly-brief serves scan_id, issued_at, done, total, remaining, decisions, new_since_monday and new_total. Each decision serves id, action_id, job_id, kind, title, demand, href, from_last_week and decided. week-timeline serves week, rows and total; rows carry id, kind, event, observed_at, target, action_id, work_href and result. focus-cards serves items with focus and figures; figures carry key and figure. First-party sessions also receive the brief’s headline and read_only, the event and focus sentence, and each focus figure’s label. All three carry meta; the brief and timeline also carry limit, offset and next_cursor. See Home fields.
  • 2026-10-30: GET /v1/brands/{brand_id}/reports and GET /v1/brands/{brand_id}/reports/{report_id}, with MCP get_reports, list and read the brand’s weekly and quarterly reports as they issued: ai and google standings, moved, work_completed, competitors, next, and for a quarterly report its weeks. Each section carries a state; focus holds the stars and a quarterly report’s goal the revision current at issue, and new_pages lists the pages cited for the first time. GET /v1/brands/{brand_id}/reports/{report_id}/recipients, and get_reports with recipients=true, list who a report was sent to. See Reports.
  • 2026-10-30: GET /v1/brands/{brand_id}/herald and MCP get_herald_greeting add greeting, decisions_waiting, new_results, seen_at, address and suggestions. They use templates with no model call or answer charge. page selects the suggested question, and scope carries its active filters through the counts and returned address. The Herald answers every kind of work in one conversation. Existing conversation paths return their history; former persona conversations accept no new messages. Onboarding answers before setup confirmation do not use the monthly allowance. See The Herald and Herald greeting.
  • 2026-10-30: GET /v1/brands/{brand_id}/moving-away-from and MCP get_perception with moving_away_from return, for each label the brand is moving away from, the share of answers naming it that describe it that way, the change in that share where the paired test calls it real, the newest answer’s words and the cited pages that repeat it. Moving away from maps the fields.
  • 2026-10-30: Action detail and MCP get_action add ordered results.steps, with each kind’s declared signals and pending, unchanged, unavailable and inconclusive states. Results rows in /v1/brands/{brand_id}/results and MCP list_results add the same results object. Measured steps distinguish No effect, Fell and Too early to tell. Recommended more and Paying off require verification of the targeted answer metric against untouched questions; a live site fix claims no answer gain. See Work results.
  • 2026-10-30: GET /v1/organizations/{organization_id}/usage and MCP get_usage add first_screen_rewrites to each brand: used, limit and resets_at for the free first-screen rewrites it has started this calendar month. GET /v1/actions/{action_id} and MCP get_action add the draft type value first_screen: a headline, subheading and call to action, one to a line. See First-screen rewrites.
  • 2026-10-30: Competitor list and detail reads, and MCP list_competitors and get_competitor, accept with_details to include weekly sites or website data and moves with stored before and after values, and AI descriptions dated by description_scan_id and description_at. The list adds a templated headline, its rows add brand_key and description, leaderboard rows add description, and detail adds description, most_said_for and most_said_against. Competitor website changes add nullable before, after and current screenshot_url; snapshots carry week, headline, checks and pricing as applicable. See Competitors and Competitor websites.
  • 2026-10-30: GET /v1/brands/{brand_id}/strategy and MCP get_strategy return the brand’s goal with its revisions, baseline, current Recommended, Mentioned and Understood on the goal’s questions and target, its focus stars on topics, competitors and markets, and moving_away_from. Actions from GET /v1/brands/{brand_id}/actions, GET /v1/actions/{action_id}, MCP list_actions and get_action add focus, the starred topic or competitor the work serves, or outside. GET /v1/brands/{brand_id}/settings and MCP get_settings add profile.profile.moving_away_from. See Strategy.
  • 2026-10-30: Rows a kind of work can address add insight, with a stable id, the kinds of work that fit it, each with its play, title and credits, and the work filed from it. They are Website findings on GET /v1/brands/{brand_id}/audit and MCP get_audit, a page’s findings and the checks it fell short on, on GET /v1/brands/{brand_id}/pages/{page_id} and MCP get_page, contradicting pages on Perception and Reputation claims with MCP get_perception and get_reputation, opinions on GET /v1/brands/{brand_id}/reputation, worth_pursuing on GET /v1/brands/{brand_id}/sources and MCP list_sources, unanswered coverage_questions on GET /v1/brands/{brand_id}/topics/{topic_id} and MCP get_topics, competitor website changes on GET /v1/brands/{brand_id}/audit/competitors, MCP get_competitor_sites and the competitor reads with with_details, and prompts an engine leaves you out of on GET /v1/brands/{brand_id}/prompts, one prompt, and MCP list_prompts and get_prompt. Changed: a worth_pursuing row’s title names the route its outreach takes when the source has none of its own yet. See Insights and their work.
  • 2026-10-29: GET /v1/actions/{action_id} and MCP get_action add content_piece.images, with featured-image state, file metadata, generations left, earlier results and the social preview’s source and style. GET /v1/actions/{action_id}/piece/images/{slot} redirects to a fresh download for featured or social. See Content credits.
  • 2026-10-29: GET /v1/brands/{brand_id}/pages/{page_id} and MCP get_page findings add note, this page’s own note, and others, the count of other affected pages. They drop points_off_score because a site-wide deduction does not describe one page. The Website findings read keeps points_off_score. See Findings.
  • 2026-10-28: Actions and MCP list_actions with assignee=mine_or_open return teammate-owned asks under group=waiting when both people can start work. Their holder is waiting, demand names the teammate and waiting_since stays unchanged. group=your_input keeps your own and open asks, oldest first. Omitting assignee, service tokens and readers who cannot start work keep their existing behaviour. Work includes daily updates in its newest completed scan and retains every finished group from the last 14 days. See Actions.
  • 2026-10-27: Topic leaders include measured discovered brands in the comparison, matching the Brands table. A discovered brand without a score does not block a lead. See Topics.
  • 2026-10-26: Every figure change in /v1 and MCP, and each Overview card’s change, adds compared_engines: the engine keys delta was taken on. Changed: when the engines asked in the period differ from the baseline’s, delta is the move over the engines both asked, not the move the trend draws, and compared_engines names them. A figure’s value, trend and engine boxes still include every engine asked. compared_engines is null when the size is the move the trend draws, and on Search. See Change.
  • 2026-10-25: Changed: GET /v1/brands/{brand_id}/keywords and MCP get_keywords with group=concept join the keywords sharing one English meaning across topics as well as markets. Concept keys are g:<sha1>, and a group=concept cursor issued before this change returns invalid_cursor. Each concept adds topics and members_checked, and topic, now deprecated, repeats the first of topics. With topic, a concept with a member in that topic keeps its members in other topics. A concept’s mentioned is shown once any member’s check has fetched its results, and concept and market searches_total count no_data keywords as zero. See Keywords.
  • 2026-10-25: Changed: A Search change is the move between the two points the Search trend draws, under any keyword filter, and its baseline dates are the baseline report’s own. A Search figure whose baseline report the trend draws as not measured reads first_report with delta: null and no baseline dates. Search reads the keywords you track today in every report, so archiving a keyword removes it from past points; this replaces the frozen coverage of 2026-10-24. A segment’s language policy stored as a cycle and as shares compares equal, so trend no longer labels a language change for the same mix. The words for not_comparable, such as trend.label on Prompts and claims, read New baseline; its state is unchanged. See Change.
  • 2026-10-25: GET /v1/brands/{brand_id}/keywords and MCP get_keywords accept mentions=mentioned|recommended, which selects the keywords whose latest check mentions or recommends you, before grouping, the summary and the totals. Changed: tracked_total and archived_total are each view’s total under the request’s filters and grouping, so group=concept counts concepts and group=market counts markets. rankings_total and each market row’s rankings count the selected keywords with a fetched check in the period instead of in its latest report. summary adds checked_top_3 and checked_top_10, those keywords in the top 3 and top 10. See Keywords.
  • 2026-10-25: Changed: Search detail, on Scores and MCP get_scores with with_search_detail=true, counts rankings as the keywords read does. rankings_total is every tracked ranking, checked or not, and the new rankings_checked those with a fetched check in the period, of which the new rankings_checked_on_axis have a positive share on the axis. rankings_on_axis and rankings cover every ranking whose latest check has a positive share on the axis, and each ranking adds volume_state. by_market has one row per country, as the keywords read’s market filter selects it, with every tracked ranking in it and the keywords read’s summary figure under that market; language is null for a country searched in more than one. own_pages_top10, ai_overviews_citing_you and ranking_pages read each ranking’s latest check. The new brands_led counts the brands below you on the axis. See Search detail.
  • 2026-10-25: Prompt google_searches entries add answers and volume_state. They sort by distinct answers that ran the search, then monthly Google searches, rank and text. The prompt pane reads Under 10 when Google returned no volume number. See Google searches.
  • 2026-10-25: GET /v1/brands/{brand_id}/prompts/{prompt_uid} and MCP get_prompt add mentioned_count and recommended_count to each engine_cards entry: the answers on that engine that mention or recommend you, over the answers of the matching mark in its figures. See Prompts.
  • 2026-10-25: Changed: Prompt and engine panes return answer_count: null for Understood, which has a graded share instead of a count of perfect matches. See Figures.
  • 2026-10-25: Changed: Search detail brands, on Scores and MCP get_scores with with_search_detail=true, lists every brand by the axis value, unmeasured last, instead of the first five with you in the fifth row. brands_total and each row’s fields are unchanged. See Search detail.
  • 2026-10-25: GET /v1/brands/{brand_id}/topics/{topic_id} and MCP get_topics with a topic_id and with_pane=true add ai_counts: the topic’s AI mentioned and recommended answer counts, each with numerator, denominator and answers. Without with_pane the response is unchanged. See Topics.
  • 2026-10-25: Scores and MCP get_scores with with_panes=true and side=ai or side=all add brands and brands_total to the Praised pane, in the shape of the Mentioned and Recommended panes, and paused_engines to the Understood and Praised panes. See Brands and paused engines.
  • 2026-10-24: Scores and MCP get_scores with with_panes=true and side=ai or side=all add brands, brands_total and paused_engines to the Mentioned and Recommended panes. brands lists up to five brands by the axis, pinning you fifth when you place lower, each with brand_key, name, domain, is_you, rank, value and change; paused_engines lists the engines paused for the period’s latest report. Search detail brands rows add brand_key. Existing fields keep their values. See Brands and paused engines.
  • 2026-10-24: MCP tool descriptions no longer end with the OpenAPI link. The server instructions and list_brands carry it, so the tool list is about 2 KB shorter. See Connect an MCP client.
  • 2026-10-24: Pane and API reads name the next step; Actions can be filtered to one prompt, topic, keyword, figure, source or competitor. One prompt, topic and keyword, each axis pane in GET /v1/brands/{brand_id}/scores?with_panes=true, one source and a competitor page’s rival, with their MCP tools, add actions_total, every live action about the subject, and next_step_action_id and next_step, the highest-priority live action that waits on you and that you can act on. Each lists its actions highest priority first. GET /v1/brands/{brand_id}/actions and MCP list_actions accept subject, such as topic:<id>, and add subject_label when you send it. Changed: one source’s actions and actions_total cover live work only, so finished and dismissed pitches leave the list. See Action fields.
  • 2026-10-24: Keywords and MCP get_keywords add group=concept|market, market, position, ai_overview, q, with_summary, and sorts markets_top10 and change. Each keyword adds mentioned_change. Optional concepts carry key, text, topic, member_ids, members, distinct markets, searches_total, volume_partial, best_rank, best_rank_keyword_id, best_rank_country, members_top10, ai_overview counts and mentioned. Optional market rows carry country, language, keywords, rankings, volume totals, top_3, top_10 and mentioned. Grouping or requesting a summary adds concepts_total, keyword_markets_total and rankings_total. summary adds mentioned, markets, positions with top_3, top_4_10, not_in_top_10 and unchecked, plus top_10. Grouping follows filters and precedes sorting and paging. The default list keeps its shape apart from mentioned_change. See Keywords.
  • 2026-10-24: GET /v1/brands/{brand_id}/topics/{topic_id} and MCP get_topics with a topic_id accept with_pane=true, which adds by_engine, search_trend, keywords_top10, brands, brands_total and pages_total. Without it the response is unchanged. On side=search, brands places brands by Mentioned. See Topics.
  • 2026-10-24: GET /v1/brands/{brand_id}/prompts/{prompt_uid} and MCP get_prompt add google_searches, the prompt’s Google searches grouped by text and market, each with the engines that ran it, its monthly searches, your Google rank and the matching keyword. They also add sources_total, the number of domains the prompt’s answers cite beside the five in sources, and mentioned_pct on each wording. See Google searches and Prompt AI searches.
  • 2026-10-24: Scores and MCP get_scores accept with_search_detail=true with with_panes=true and side=search. Mentioned and Recommended add search with ranking counts, your pages in Google’s top 10, AI Overviews citing you, ranked brands and their changes, rankings, market figures and related actions. The default response stays unchanged. See Search detail.
  • 2026-10-24: GET /v1/brands/{brand_id}/keywords/{keyword_id} and MCP get_keywords with keyword_id add rank_series: your best Google position at each weekly report that figures.mentioned.trend charts, oldest first, with the same at and break as that trend’s point. A point’s state is ranked, not_in_top_10 or unchecked, declared open to new values, and position is set only when it is ranked. See Keywords.
  • 2026-10-24: Changed: a figure’s change delta in /v1 and MCP is the shown value minus the baseline’s, in points, as the trend draws them, instead of the paired test’s estimate. The paired test still sets low, high and real. up and down need a real move that has the sign of delta; any other move is steady with its signed delta. No change serves calibrating any more, leaderboards included, and a baseline with no value is first_report. A claim’s trend on Perception follows the same rule. One report reads on the previous week in the comparison text. See Change and Figures in the API.
  • 2026-10-24: competitors_checked_7d (and its deprecated alias competitors_watched) on Work and the Overview counts only competitors you track now, so it never exceeds competitors_tracked. GET /v1/brands/{brand_id}/competitors adds page.checked_7d, the same figure. See Competitors and Actions.
  • 2026-10-24: Multi-week figures in /v1 and MCP weigh each language policy by its number of answers when the policy changed inside the period. Weights within each policy stay the same, as do figures for periods covered by one policy. Stored reports, leaderboards and issued Snapshots keep their frozen values. See Mentioned and Recommended.
  • 2026-10-24: GET /v1/brands/{brand_id}/answers and MCP list_answers accept read_since, an ISO 8601 time that keeps the answers whose run finished at or after it. With period=all or without period, it reads every weekly and daily answer once, and total matches the answer counts of GET /v1/brands/{brand_id}/work and MCP get_work for the same window. Changed: demand on delivered actions reads the result label, Paying off, Cited or Delivered, followed by result by and the date while the verdict is pending, such as Cited · result by 17 Nov. It replaces Verifying and the words of the measured outcome. See Prompts and answers in the API and Results.
  • 2026-10-24: Search-side figure changes use each report’s frozen keyword checks for coverage, even if you archive a keyword later. Mentioned, Recommended, Understood and Praised on Search read First report when the baseline did not measure them. A change between the AI part and the blend on All or AI remains not comparable. See Change.
  • 2026-10-24: Changed: ai_citation_share on each platform in GET /v1/brands/{brand_id}/reviews and MCP get_reviews is the share of your counted AI answers in the latest week that cite the platform, from 0 to 1, instead of the share of synced reviews also found in AI citations. It no longer moves when reviews sync. See Platform ratings.
  • 2026-10-24: Removed: trend_note from axis panes in GET /v1/brands/{brand_id}/scores?with_panes=true and MCP get_scores. Trends draw from the second weekly report, so no note applies. See Change.
  • 2026-10-24: Website reads and MCP get_audit count pages_with_findings over pages read. total is coverage.pages_read; unread pages contribute to neither count nor total. Every trend point with a saved site map uses the same count. A report without a map keeps its recorded value and starts a break. Cut-short reads leave the sitemap-link check not measured, with no points off. New reports use findings rules version 3, breaking the Website score trend at the change. AI can read follows each page’s access checks where available. See Website page counts.
  • 2026-10-24: Changed: facets.languages on GET /v1/brands/{brand_id}/audit/pages, GET /v1/scans/{scan_id}/audit/pages and MCP list_site_pages counts each language under every filter but language. See Website.
  • 2026-10-24: Changes on /v1 and MCP use the previous comparable report for Latest and the preceding equal-length window for multi-report periods. Baselines stop at non-comparable reports. From the second report, the paired test alone calls a move real; steady changes keep their signed delta, and calibrating means no interval. Since you started also compares from two reports. The Sources Citations card change is the difference between the period’s citation count and its baseline, with direction following the sign of that difference. Trend break adds comparable, true for engine or language changes alone. See Change and Sources.
  • 2026-10-24: Topic lists, one topic and MCP get_topics return leader_state as measured, no_clear_leader or not_measured. A leader needs a Heralded Score above Invisible, no tie and an interval’s low end above every other brand’s score. An unmeasured tracked competitor prevents a clear lead. leading counts your clear leads; competing counts all topics in view where your Heralded Score is measured. The Writer meter uses the same count for the latest report. See Topics.
  • 2026-10-24: Understood and Praised follow side in overview, scores and MCP get_brand_overview and get_scores. ai reads AI answers, search reads ranking pages, and all reads the blend. Overview adds both figures to every entry in sides. Figure panes carry their selected figure and trend, keep you and topic_id, and add parts.ai_answers and parts.web_pages for a blend. Engines without a rendered answer are left out of pane engine lists. figure_only is deprecated until 2026-11-23, with Deprecation and Sunset headers. See Figures.
  • 2026-10-24: Changed: the overview’s and MCP get_brand_overview’s sources_mentioning_you counts third-party sites with a read page naming you, out of the third-party sites with a read page, over period. It counted the pages of the latest report. Muted sites and competitors’ sites are left out, and the field keeps count, of and pct. The source list and MCP list_sources add recommending.naming, the same count. See Citations.
  • 2026-10-23: listActions and MCP list_actions accept assignee=mine_or_open for the Needs-you list and add waiting_since to date the current ask. With group=your_input, rows arrive oldest-waiting first and include failed first drafts handed back to you and stopped site checks. See Action metadata.
  • 2026-10-23: Removed: the engine filter from GET /v1/leaderboards and MCP get_leaderboards. HTTP requests that still send engine= read the board across all engines. Each engine’s top three, brand engine figures and engine_ranks remain available. See Leaderboards.
  • 2026-10-22: The Heralded Score uses AI answers only. Overview, scores, competitors and topics return the Heralded Score, Mentioned and Recommended for side=all. Search keeps its Mentioned and Recommended and returns heralded_score.value: null with the new state not_scored. Keyword score and trend are null; keyword detail keeps its shares and results. Stored reports read the same way without a history break. See Sides.
  • 2026-10-23: GET /v1/brands/{brand_id}/results and MCP list_results list delivered actions with Paying off, Cited or Delivered labels, first citation, citation count and measured outcome. Page by label or newest result, with label counts and a total. Setup, prompt additions and deliveries undone by reopening are excluded. The overview’s verified_actions keeps its verified gains and citations. See Results in the API.
  • 2026-10-22: Action lists and MCP list_actions add first_citation and citation_count. The overview and MCP get_brand_overview include cited pages in verified_actions. Changes and MCP list_changes add first_citation under the verification source, opening the action and folding its matching site-citation observation. See Action metadata.
  • 2026-10-22: Work operations (GET /v1/brands/{brand_id}/work, MCP get_work) add title, the action or piece the work is for, and finished_at and result on finished work. status adds waiting, for work waiting on someone other than the caller, and is declared open to new states. A report’s label names its run, such as Weekly report, and progress appears only while it reads answers. A delivered report is done even when a step failed, and a failed read is left out once a later one finishes. See Actions.
  • 2026-10-22: A Website read’s coverage (GET /v1/brands/{brand_id}/audit, MCP get_audit) adds pages, the pages on your site, with pages_read and pages_ai_readable, and the site map (GET /v1/brands/{brand_id}/audit/map, MCP get_site_map) adds site_pages, the same count in every language. pages_with_findings.total is that count, the pages read (GET /v1/brands/{brand_id}/audit/pages) list those pages, one row each, and fix_first lists the most points off the score first. pages_in_site on the website scope read counts Counted only sections too. See Website.
  • 2026-10-22: Changed: GET /v1/brands/{brand_id}/perception and MCP get_perception serve Understood and Praised as the blend of AI answers and pages, the same figures as the overview and the reputation read. See Perception.
  • 2026-10-22: Each side of a topic’s scores in GET /v1/brands/{brand_id}/topics, /topics/{topic_id}, a prompt’s topic_detail and MCP get_topics adds state: not_measured or too_few_answers for an AI or All side with no value, and not_scored on Search. See Topics.
  • 2026-10-22: Changed: a daily update’s finished keyword checks no longer set updating on the search.score, search.keywords and sources surfaces, because they count in the next weekly report. Pending checks still do. See Result freshness.
  • 2026-10-22: Figure changes add state for a first report, calibration, a measured move, a steady comparison or a comparison that cannot be made. Engine and language additions keep paired change. Search-side figures carry basis: "search". REST and MCP return the same states and trend markers. See Change.
  • 2026-10-20: Service Snapshot and Full audit starts require the Idempotency-Key header. The deprecated body alias idempotency_key has been removed. See Service starts.
  • 2026-10-20: Removed the pre-launch GET /v1/brands/{brand_id}/prompt-suggestions, MCP list_prompt_suggestions and topic detail’s buyer_questions. Read suggested topics through /topics?view=suggested or get_topics with view=suggested, and prompt AI searches through /prompts, /prompts/{prompt_uid}, list_prompts or get_prompt.
  • 2026-10-20: Service tokens can start a Quick audit through POST /v1/service/quick-audits without spending a scan credit, then read it through the service audit routes. Each workspace can start 100 per UTC day; replays do not count. Website results retire 30 days after delivery. See Service Quick audits.
  • 2026-10-19: Answers and prompts remove the deprecated search parameter from REST and MCP list_answers and list_prompts. Use q for text search. See Text search.
  • 2026-10-18: Each language in a Website read’s coverage.languages (GET /v1/brands/{brand_id}/audit, MCP get_audit) adds read, the pages the read covered in that language. It is 0 for a language the site holds and the read did not cover, and null on reads that kept no count. See Website.
  • 2026-10-18: Changed: competitors on POST /v1/service/snapshots is optional and deprecated. A Snapshot ranks the competitors its answers name and ignores any you send. The field goes on or after 2026-11-16. The body field idempotency_key on service starts also goes on or after 2026-11-16, so send the Idempotency-Key header. See Developers.
  • 2026-10-18: GET /v1/actions/{action_id} and MCP get_action add content_piece.fields, the settled draft’s title, summary or search details. Each field carries name, label and value. See Actions.
  • 2026-10-18: /v1/organizations/{organization_id}/usage and MCP get_usage add segments, with used, included, extra and limit, and each brand adds segments, its live segments with topics: tracked, limit and blocks. /v1/brands/{brand_id}/settings and MCP get_settings add features, with mentions_monitoring, reviews and advocacy, and each segment adds the same topics, which /v1/brands/{brand_id}/segments carries too. Existing fields stay the same. See Usage.
  • 2026-10-17: MCP rejects undeclared arguments, describes every input and returns actionable JSON errors. get_scores uses only topic, list_answers only prompt, and get_prompt only prompt_uid. Website and scan tools declare their required brand-or-scan selection. get_leaderboards adds resource=hall_of_fame. Tools omit output schemas and link to the response types in OpenAPI. Collection operationIds become listOrganizationBrands, listBrandSegments, listServiceAuditPages, listServiceAuditKeyPages, listAuditCompetitors, listScanAuditCompetitors and listConversationMessages. REST scores retains topic_id as deprecated. These are the approved pre-adoption changes; future removals follow Versioning.
  • 2026-10-17: The public API and MCP return data only. Composed sentences, enum labels, menus, cards and viewer affordances remain available to the first-party Command Center. Trend points add structured break data; prompt tiles add state, including not_applicable; competitor-site reads add reason; change targets add filters. Work rows add brand_id and deprecate tracked_domain_id; organization portfolios add kind. Nested lists state their totals, and evidence adds meta. Brands, conversations, evidence, key pages, website scope and segments now page with limit, cursor and next_cursor. Hall-of-fame and scan-competitor cursors are active. Both conversation message reads return newest first, remove viewer read markers and replace before/after with cursor; this changes MCP get_conversation_by_id arguments too. Answers and prompts add q, with search retained as a deprecated alias. Deprecated operations send Deprecation and Sunset; MCP results carry deprecated and sunset, and output schemas are omitted. This closes the pre-adoption exception.
  • 2026-10-17: Overview and MCP get_brand_overview add shared work counts and frozen report.actions_found. open_action_count is deprecated in favour of counts.open. Scheduled work is separate from Proposed, and Things to do is Your turn plus Proposed. Work adds competitors_tracked and competitors_checked_7d; competitors_watched is a deprecated alias of the latter. Figures carry basis and their own numerator and denominator. Sources count pooled answers once and apply market and language filters, so their numbers can be lower. They add site populations, one verdict from cited pages, and an opening filter; muted sites are excluded. Negative-source rows add domain_citations. Topics and keywords add tab counts. Website adds a change object next to the score. See Actions, Sources and Figures.
  • 2026-10-17: REST errors link their type to the code’s documentation on Errors and limits. This replaces about:blank under the pre-adoption exception.
  • 2026-10-17: API limits use sliding windows and a computed Retry-After. MCP counts tool calls only and returns rate_limited tool errors with retry_after. Service tokens have a 120-per-minute limit. Service starts accept Idempotency-Key, answer 201 with Location on create and 200 with Idempotent-Replayed: true on replay, and refuse changed payloads with 422. Service tokens can read their workspace’s Snapshot at GET /v1/service/snapshots/{scan_id}. New API and service tokens include a checksum; existing keys keep working. See Errors and limits, service starts and API keys.
  • 2026-10-16: Topics in /v1 and MCP get_topics remove status, status_label, page, citations, search_clicks, ai_visits, action, action_label, piece, pieces, open_action_id and why. Lists remove covered, cited, missing, sentence, statuses and the status parameter; sorts for the removed columns are also removed. Cards remove covered, total, cited, missing, missing_new, covered_change and cited_change. One topic removes problems, wins, unmeasured, value, page_checks, top_query, questions, questions_answered, question_total, sources and tasks. Sources’ topic chips remove status and status_label, keeping band. Scores, demand, Cited share, own pages, frozen question coverage, live actions and suggested-topic evidence remain. This follows the pre-adoption exception. See Topics.
  • 2026-10-16: Trials show six untouched suggestions at once. GET /v1/brands/{brand_id}/actions and MCP list_actions return shown actions and count the rest in suggestions_kept. Starting, dismissing or deferring a suggestion frees a place; billing shows every held-back suggestion. Home and Actions show the same count. See Proposed.
  • 2026-10-16: Your first report uses every engine on your plan, including Perplexity and Microsoft Copilot, with the same website assessment, search reads and scoring checks as every weekly report. Confirmation refuses a prompt set too small to score before starting the report. See First scan.
  • 2026-10-16: Topic reads and MCP get_topics add AI bands, band filtering, score and citation-share sorts, filtered prompt counts and head result figures. Detail adds frozen question coverage, own pages with topic signals, per-engine prompt rates, keyword volume and rank, competitor domains, weekly Heralded Score history and live actions. Leaders use the Heralded Score, count ties as you leading and exclude topics without a measured competitor. Display volume keeps earlier-month readings. Actions accept a topic filter. Existing page and status fields, tasks, problems, wins and unmeasured remain available. See Topics.
  • 2026-10-16: GET /v1/brands/{brand_id}/overview and MCP get_brand_overview add latest_read.scan_id, the weekly report’s scan ID. It can differ from the daily scan that meta.data_as_of.id pins. See Reads.
  • 2026-10-16: Action titles, details, notes and done-when read in plain words. An action changes only when the evidence changes what it suggests. See Actions.
  • 2026-10-16: Each page’s facts in GET /v1/brands/{brand_id}/pages/{page_id} and MCP get_page add load_ms: the milliseconds until the page’s main content shows on a simulated mobile load, PageSpeed’s Largest Contentful Paint. Weekly reports measure it on key pages; it is null on other pages and where PageSpeed did not answer. See Page stats.
  • 2026-10-16: Changed: in reports frozen from now on, each page’s category.name, the facets and categories of the site map and pages reads, and each competitor’s categories in GET /v1/brands/{brand_id}/audit/competitors and MCP get_competitor_sites use one fixed set of names, such as Blog, Documentation and Product, instead of folder and collection labels. Categories sharing a name and group are served once, their counts summed. See Pages.
  • 2026-10-16: Changed: in a weekly report, each segment’s figures count only the answers asked on that report’s market. Daily answers asked before a segment’s market changed sit out, so GET /v1/brands/{brand_id}/overview, GET /v1/brands/{brand_id}/scores and MCP get_brand_overview and get_scores keep their values that week, with state not_comparable and change null, instead of null values. Every trend point’s break_label names a market change in words, such as Romanian answers are now asked in English and Romanian; breaks[].value keeps the market key. See Change.
  • 2026-10-16: Outreach actions on YouTube, LinkedIn, Medium and Reddit name the channel, author, publication or subreddit in target_entity, such as reddit.com/r/notion, and /v1 sources give those sites no priority.
  • 2026-10-16: GET /v1/actions/{action_id}, GET /v1/brands/{brand_id}/actions and MCP get_action and list_actions offer primary_verb review whenever work needs your decision and has no other primary verb. Its job label is Answer questions for content questions and Review otherwise. GET /v1/brands/{brand_id}/changes and MCP list_changes net presence, citation and recommendation moves over the window, combining surviving gains and losses into one sentence per engine.
  • 2026-10-16: Perception quotes and page passages in GET /v1/brands/{brand_id}/perception and MCP get_perception are served as plain text. Claim quotes use prose sentences, never table rows or headings. See Perception.
  • 2026-10-16: Removed: prompt_slot_cost from GET /v1/actions/{action_id}, GET /v1/brands/{brand_id}/prompts/{prompt_uid}, GET /v1/brands/{brand_id}/scores and GET /v1/brands/{brand_id}/sources/{domain}, and from MCP get_action. The field was not part of GET /v1/brands/{brand_id}/actions or MCP list_actions. It has been 0 since tracking a prompt stopped being an action.
  • 2026-10-16: GET /v1/brands/{brand_id}/evidence and MCP list_evidence list the latest weekly report evidence Heralded holds for your brand: each item’s id, module, kind, target, segment, fact, observed_at and the plays its owner offers.
  • 2026-10-15: Removed: action from each page of GET /v1/scans/{scan_id}/audit and MCP get_audit with scan_id, and from improve_pages and cited_strong_pages in GET /v1/shared/scans/{share_id}. Work wording comes from actions.
  • 2026-10-15: GET /v1/brands/{brand_id}/overview and MCP get_brand_overview gain competitor_rank, your position among your tracked competitors by Heralded Score and the number of scored brands it is of; lean=true leaves it out. GET /v1/brands/{brand_id}/scores and MCP get_scores with group_by=competitor carry the same competitor_rank. See Figures in the API.
  • 2026-10-15: Score v9.1 weights Search keywords within their countries, gives keywords without positive volume a small fixed weight, and keeps countries with unfinished research unknown. Stored v9.0 reports keep their frozen weights and version. Comparisons break between v9.0 and v9.1; AI-only reads stay on v8.0. API and MCP figures use the same weights. See The Search side and Versioning.
  • 2026-10-14: Action reads and MCP list_actions and get_action add grounds.targets, the prompt or keyword results the work targets. Each carries kind, uid, engine and metric. Work with grounds but no targets returns an empty list; actions predating structured grounds keep grounds: null. See Action fields.
  • 2026-10-14: Topics in /v1/brands/{brand_id}/topics and MCP get_topics add pieces, every non-failed piece for the topic and segment, newest first. piece keeps the newest for compatibility. Studio orders can request a similarity warning and confirm another order; a topic can have several pieces. See Content.
  • 2026-10-14: GET /v1/brands/{brand_id}/topics/{topic_id} and MCP get_topics with topic_id add problems, wins, unmeasured and value. Problems include prompt results by engine and keywords outside your top three positions, over four weekly reports regardless of period. See Topics.
  • 2026-10-14: Overview, scores and competitor figures add state: "pending" for Search while awaiting its first measurement. Values remain null; All keeps the AI figures. The Command Center shows Calculating, and MCP returns the same state. See Headline figures.
  • 2026-10-14: Content action reach uses the demand value frozen with its topic verdict. Keyword check dates now match the report period’s rank results.
  • 2026-10-14: GET /v1/brands/{brand_id}/audit/map, GET /v1/scans/{scan_id}/audit/map and MCP get_site_map add host and unread to each page. host names the host of a page outside the site you entered, subdomains included, and is null on the site’s own pages. unread is true for a page the site lists that the report never read. Changed: in reports frozen from now on, http and https spellings of one address are one page, and only the entered site’s homepage has type home; other hosts’ homepages and language homepages have type other. See Website.
  • 2026-10-14: Each fact in profile.facts of GET /v1/brands/{brand_id}/settings and MCP get_settings adds source, the Content Studio piece a member saved it from, with its piece_id and title. It is null on a fact added in Brand settings or on Perception. See Brand facts.
  • 2026-10-14: Removed: rank, src_order, targets, category, effort_weight, perception_lift_pts and primary_lift_pts from report moves, and total_lift_pts from GET /v1/shared/scans/{share_id}. The report’s claims no longer include top_move or owned_content_move.
  • 2026-10-13: Scheduled actions in GET /v1/brands/{brand_id}/actions and MCP list_actions move from group scheduled to new, with their start date in scheduled_for. scheduled now marks only Heralded’s own scheduled jobs. The Actions board hides dismissed actions when dismissed is omitted, and its old empty stacks field is removed. See Action fields.
  • 2026-10-13: GET /v1/actions/{action_id} and MCP get_action return only settled text in content_piece. During writing or checking, the previous settled version remains available, or draft fields are null before the first settles. content_piece.stage uses ordering, preparing_brief, questions, brief_review, writing, checking, your_review, applying, rewriting, approved, publishing, published, stopped, failed and paused. See Content Studio.
  • 2026-10-13: Service tokens can start Full audits for one workspace scan credit through POST /v1/service/audits, then read progress, Website results, the brief, collections, pages, key pages, maps and retained page text. Audit and Snapshot idempotency keys share the workspace’s namespace; reusing a key across products answers 409 idempotency_key_reused. Customer API keys cannot start or read service audits. See Service audits.
  • 2026-10-13: GET /v1/shared/audits/{share_id} reads a delivered Quick’s frozen Website, key pages and map without a credential. Base and Full results stay owner-only. GET /v1/scans/{scan_id} and MCP get_scan now read an Audit you ran with kind: audit and audit_progress, also returned by GET /api/scans/{scan_id}. See Audit reads.
  • 2026-10-13: GET /v1/account/free-audit and MCP get_free_audit return your Base audit allowance and its renewal time, separately from Snapshot. Quick audits start without an account and expire 30 days after delivery. See Free Base audit allowance.
  • 2026-10-13: New GET /v1/brands/{brand_id}/audit/pages, GET /v1/scans/{scan_id}/audit/pages and MCP list_site_pages list the crawl’s pages with filters by category, language, findings, access, status and changed, sort by findings and clicks, and facets counting every category and language under the filters. New GET /v1/brands/{brand_id}/audit/key-pages, GET /v1/scans/{scan_id}/audit/key-pages, their /{path} reads and MCP get_key_page read the key pages with their above-the-fold read, last four weeks and history. Changed: each page in pages of GET /v1/brands/{brand_id}/audit adds category, language, findings, worst, claims_stated, claims_asked and change, and the read takes the same filters. See Website.
  • 2026-10-13: New GET /v1/brands/{brand_id}/audit/competitors, /audit/competitors/{key} and GET /v1/scans/{scan_id}/audit/competitors, and MCP get_competitor_sites, read competitor websites. Weekly reads carry the table, homepages, pricing, categories, activity and a paged feed filtered by competitor key and change type. An Audit’s owner reads its policy’s comparison: Base homepage screens, with Full adding proof and copy similarity. Unreadable pricing has null plans.
  • 2026-10-13: GET /v1/brands/{brand_id}/audit and MCP get_audit add website, the Website score of the newest weekly report that finished reading your site, named in meta.data_as_of: groups and areas with bands, every finding with its state, share, points off the score, fix steps and open action, fix_first, coverage, versions, changes since the last report, the weekly series and next_read_at. finding, finding_pages_limit and finding_pages_offset page a finding’s pages. Changed: meta.data_as_of on this read names that report once one exists. GET /v1/scans/{scan_id}/audit and get_audit with scan_id add an Audit’s own website, null on a Snapshot, the brief it was judged against and the brand’s look. New GET /v1/brands/{brand_id}/audit/map and GET /v1/scans/{scan_id}/audit/map, and MCP get_site_map, read the report’s site map in one language, whole or one folder at a time. GET /v1/brands/{brand_id}/pages/{page_id} and get_page with a page_id add findings, above_the_fold, against_brand and copy_and_proof. See Website.
  • 2026-10-12: GET /v1/brands/{brand_id}/settings and MCP get_settings add profile.profile.tone, how the brand’s pages sound: formality is formal, conversational or null, and complexity is technical, plain or null. Both are null until set.
  • 2026-10-12: failure_reason on scan rows of GET /v1/scans and GET /v1/brands/{brand_id}/scans, on GET /v1/scans/{scan_id} and in MCP get_scan adds service_unavailable: a service Heralded relies on kept a Snapshot’s profile from drafting for 24 hours. The OpenAPI document now declares those values with x-extensible-enum, so treat one you do not know as other. See Scans.
  • 2026-10-12: GET /v1/brands/{brand_id}/prompts, /prompts/{prompt_uid} and MCP list_prompts and get_prompt add evidence, the stored evidence behind each prompt followed by the questions your team added to its topic, and synthesised. Each evidence item in these reads and in a suggested topic’s evidence adds id, set on a question your team added, impressions and searches_mo. See Prompts.
  • 2026-10-12: GET /v1/brands/{brand_id}/prompt-suggestions and MCP list_prompt_suggestions are deprecated and return a deprecation_notice and empty lists. Read suggested topics through /topics?view=suggested or get_topics with view=suggested.
  • 2026-10-11: GET /v1/scans/{scan_id}/audit and MCP get_audit with scan_id add moves, the scan’s priority actions, best first, with the fields of the shared read’s moves. A Snapshot’s are the ones its report shows. See Priority actions.
  • 2026-10-11: Each of the moves in GET /v1/shared/scans/{share_id} gains play, grounds and gain, read as on an action. Changed: moves are the work Heralded’s plays would file for the scan: up to five, best first, at most two of one play and none with a low expected gain. perception_lift_pts, primary_lift_pts and total_lift_pts are always 0, rank and src_order give each move’s place, and a new report’s claims carry no top_move or owned_content_move. See Priority actions.
  • 2026-10-11: Each action in GET /v1/brands/{brand_id}/actions and GET /v1/actions/{action_id}, and in MCP list_actions and get_action, gains gain, its expected gain: band is high, medium or low, or null on work you asked for, and aims_at says what the work aims at. Changed: expected_impact_pts is always null there and on a competitor page’s queued actions. With group=new, this week’s work comes first, then the backlog, each with the actions you placed ahead of Heralded’s ranking, which no longer orders by severity. See Expected gain and ranking.
  • 2026-10-11: GET /v1/actions/{action_id} and MCP get_action add trail, what happened since the action was delivered: one entry per signal in tracking, then the measured result. Each entry has a signal, a state of good, no_change, couldnt_check or pending, a summary, a reason and an at date. Changed: tracking on the site_fix play no longer lists cited. The page_access play keeps live, crawled and cited. Tracking on outreach and correction requests no longer lists live; on a site positioning fix it lists only moved. See What happened since.
  • 2026-10-11: Each placements row and best_three row of a brand read of GET /v1/leaderboards and MCP get_leaderboards gains sides: the brand’s rank and score on the ai leaderboard and on the search leaderboard of the same panel and month. sides.search is null where that month has no search leaderboard, and on a Europe placement unless all seven country reads have a Search side. sides is null on a brand page Heralded has not rebuilt yet. See Brand and source pages.
  • 2026-10-11: Each action in GET /v1/brands/{brand_id}/actions and GET /v1/actions/{action_id}, and in MCP list_actions and get_action, gains grounds, done_when and tracking. grounds carries its kind, cause, dated evidence and, for best practice, the publisher guidance. It is null on an action filed before actions carried their grounds. GET /v1/actions/{action_id} and get_action also gain checklist, the steps you follow where Heralded drafts and applies nothing. See Action fields.
  • 2026-10-11: GET /v1/actions/{action_id} and MCP get_action add dismissal_reason, why a member put the action away: not_now, too_much_work, not_relevant or already_done. It is null when no reason was given and once the action is restored. See Actions.
  • 2026-10-10: Brand and source reads of GET /v1/leaderboards and MCP get_leaderboards list Europe placements. A placements row can have filters.country set to europe, with the brand’s place and score on that Europe leaderboard, or the source’s place and citations there. Questions, highlights, sources, history, engine places and a source’s pages, engines and brands count the country leaderboards only, so Europe adds nothing to them. See Brand and source pages.
  • 2026-10-10: Changed: a Europe leaderboard compares with the previous month’s. GET /v1/leaderboards and MCP get_leaderboards with country=europe now return previous_month, previous_rank, rank_change, movers, dropouts and score_series, and a brand’s change is no longer always a first reading. See Europe.
  • 2026-10-10: GET /v1/leaderboards and MCP get_leaderboards accept country=europe. An industry’s Europe leaderboard pools its leaderboards in the United Kingdom, Germany, France, Spain, Italy, the Netherlands and Romania for each month all seven published, and the Europe hub lists brands across industries with their Europe places. origin_country still takes ISO codes only. Facets pages list Europe pages at /leaderboards/<industry>/europe/. Changed: facets.countries lists a country only once it has a published panel, and never lists europe. See Europe.
  • 2026-10-10: GET /v1/leaderboards and MCP get_leaderboards take side: all, ai or search. The default is all. Changed: a leaderboard month whose run read Google scores on v9.0, and its heralded_score, Mentioned, Recommended, places, movers and history are then the weighted score of both sides, not the AI side alone. A month that did not read Google reads as before. Month-over-month comparison breaks at v9.0: for all and search, the first v9.0 month has no previous_month, previous_rank or rank_change, and its score_series starts there. The ai side continues unbroken. search returns an empty read for a month without Google results, and engine always reads the AI side. Brand and source pages read all. See Leaderboards and Score versions.
  • 2026-10-09: GET /v1/brands/{brand_id}/overview accepts lean=true, which leaves out rivals, sources, actions, attribution and readiness and reads none of them. Every other field is unchanged, and the default response and MCP get_brand_overview are unchanged. See Figures in the API.
  • 2026-10-09: GET /v1/brands/{brand_id}/overview, /scores, /competitors and /topics, and MCP get_brand_overview, get_scores, list_competitors and get_topics, take side: all, ai or search. The default is all. Changed: heralded_score, mentioned and recommended follow side, so a brand with search observations gets the figures of both sides weighed together unless it passes side=ai. Without them, all equals ai. Each of those reads gains sides_available, which lists search when a report in the period checked keywords, and the overview gains sides, the three figures on each side. A topic’s scores gain all and search beside ai, and leader and winners follow side. See Sides.
  • 2026-10-09: New GET /v1/brands/{brand_id}/keywords and /keywords/{keyword_id}, and MCP get_keywords, read the keywords you track: monthly searches, your best rank, the results that name you, each keyword’s figures with their range, the top 10 of the latest check, the prompts that make AI search it and the actions about your pages. See Keywords and Search visibility.
  • 2026-10-09: On agency plans and custom offers, a brand no longer reserves prompts and the prompt ceiling ends: segments are the allocation, each holding 15 topics. prompts_reserved in /v1/brands/{brand_id}/settings, /v1/organizations/{organization_id}/usage and MCP get_settings and get_usage is null for every brand, and prompts.pool is three for each topic the live segments can hold. Fields stay the same. See Topics and prompts.
  • 2026-10-09: GET /v1/brands/{brand_id}/reviews and /reviews/{review_id}, and MCP get_reviews, return platform ratings and counts, reviews and reply state. Core receives platform ratings and counts; Plus also receives its review list and work. features states which Plus features are available. See Reviews.
  • 2026-10-09: /v1/brands/{brand_id}/sources and MCP list_sources include Google ranking and monitoring sites, found_via, recommends_you, read_by_searchers, recommending and channels. Filter by found_via and sort by either new measure. See Source measures.
  • 2026-10-09: Brand leaderboard reads and MCP get_leaderboards remove the individual-point history module and its paging parameter. history_series keeps monthly rank, score, Mentioned and Recommended values per placement. Board months stays available. See Brand and source pages.
  • 2026-10-09: Each competitor in GET /v1/brands/{brand_id}/competitors, list_competitors and the overview’s rivals gains most_said_for and most_said_against, its positive and negative opinion with the most holders. See Reputation.
  • 2026-10-09: GET /v1/brands/{brand_id}/reputation gains opinions, what voices think about the brand, each with held_by, kinds, engines, change and action_id. GET /v1/brands/{brand_id}/reputation/opinions/{opinion_id} returns one with its holders and their passages, and MCP get_reputation with opinion_id returns it as opinion. See Reputation.
  • 2026-10-09: GET /v1/brands/{brand_id}/reputation, /reputation/claims/{claim} and MCP get_reputation read Understood and Praised from AI answers and from the pages AI cites and Google ranks that name the brand. They carry understood and praised as 0.63 × the AI part + 0.37 × the web part, parts with each, and facts, the perception claims with ai verdict counts and elsewhere counts of pages that agree or contradict, and the claim read adds documents. Under ten pages the two figures are the AI part alone. In /overview and MCP get_brand_overview, understood and praised now carry the same blend, while /scores keeps the AI part. See Reputation.
  • 2026-10-09: Score v9.0 adds the Search side. A weekly report that checked your tracked keywords on Google is v9.0, and every other read stays v8.0. Trend instrument keys add nullable sides, the sides a report observed, and keyword_set_hash, which changes when the keywords a report checked change without breaking the series. Served scores stay the AI side’s. See The Search side and Versioning.
  • 2026-10-09: /v1/brands/{brand_id}/topics/{topic_id} and MCP get_topics with a topic_id add buyer_questions, the questions buyers ask within the topic, up to 12 for each segment it is tracked in. Each has its text, asked_by with kind, engines and often, google_rank and answered_by_page. See Topics.
  • 2026-10-09: On a suggested topic in /v1/brands/{brand_id}/topics, /topics/{topic_id} and MCP get_topics, actions are those of the segment segment names, or the Default segment without one. Fields stay the same. See Topics.
  • 2026-10-09: /v1/brands/{brand_id}/topics, /topics/{topic_id} and MCP get_topics add archived_at on archived topics, the latest topic_segments.status_since across archived segments, and engines[] on suggested-topic evidence from AI background searches. Other evidence has an empty engines list; archived_at is null on tracked and suggested topics. See Topics.
  • 2026-10-09: GET /v1/brands/{brand_id}/topics and MCP get_topics list the topics you track instead of the content check’s topics, and /topics/{topic_id} reads one. A topic’s id is its UUID, and a suggested topic’s is s: and its suggestion id. view selects tracked, the default, suggested or archived. Rows keep topic, status, page, demand, citations, search_clicks, ai_visits, action and piece, now null on a suggested topic, and add state, need, segments, scores, leader, prompts_count, keywords_count, why_labels, best_to_track and, on a suggested topic, demand_measured, evidence, coverage, actions and adds. The list adds sides_available. One topic adds pages, keywords, winners, by_segment, tasks and sides_available. Earlier topic ids stop resolving, and content_topic on answers and sources takes a topic’s UUID. group_by=topic in /scores and MCP get_scores returns tracked topics, and a prompt adds topic_detail. See Topics.
  • 2026-10-08: On Core and Plus, prompts in /v1/organizations/{organization_id}/usage and MCP get_usage counts by topic. used is the active prompts of tracked topics your reading brands read, pool is three for each topic their live segments can hold, and free is the pool less used. prompts_reserved is null for every brand there and in /v1/brands/{brand_id}/settings. Agency and custom-offer workspaces keep their allocation figures. Fields stay the same. See Topics and prompts.
  • 2026-10-08: Leaderboards and MCP get_leaderboards carry the modules their pages use. Board history, brand competitors, engines, won, missed and evidence, and facets combinations are removed. Brand and source reads are current only, without month; hubs with an engine or month return an empty read. Cited-page rows appear only on all-engine panels and source pages, capped at 20 positions per source before withholding. Source pages combine those capped panel lists. Page counts and the board’s months remain available. See Leaderboards.
  • 2026-10-08: On /v1/leaderboards and MCP get_leaderboards, origin_country and audience narrow a leaderboard’s lists without ranking the selection again. Each brand keeps its panel place, rank change and score series, and movers, drop-outs and history narrow to the selected brands. The leader, questions and their winners, each engine’s top three, sources’ brand mentions, the answer population and months stay those of the whole leaderboard under any filter. Curated lists read their leaderboard under their filters. Routes, fields and paging are unchanged. See Scores and places.
  • 2026-10-08: GET /v1/brands/{brand_id}/prompt-suggestions and MCP list_prompt_suggestions now return Search Console and recurring engine-search evidence phrases, including those assigned to tracked topics. Suggestions are no longer drafted before adoption. Response fields stay the same. Clicks and position come from Search Console where available, otherwise they are null. See Prompts.
  • 2026-10-08: Brand overview adds nullable attribution, with a UTC calendar month, total classified contacts and counts by voice and named platform. Plus brands with a HubSpot attribution property receive this projection in the API and the overview assistant tool. See HubSpot.
  • 2026-10-07: Leaderboard facets add origins, sorted ISO-2 brand-origin codes for brands with a measured score in at least one current published panel. See Leaderboards.
  • 2026-10-07: The leaderboard facets combinations field now lists the same panel, hub and curated-list pages as pages. It no longer lists computed filter combinations. See Leaderboards.
  • 2026-10-07: Leaderboard facets add pages, with panel, hub and curated-list paths, titles, indexing status, featured positions and leaders. Matching leaderboard filters serve saved hub and curated-list results, refreshed after publication, included-panel corrections and reducer version changes. MCP get_leaderboards returns the same results and catalogue. See Leaderboards.
  • 2026-10-07: Panel brand rows add previous_rank, rank_change, entry state and monthly score_series. Boards add previous_month, paged movers.risers and movers.fallers, and dropouts that distinguish unranked brands from roster departures. Brand placement history adds monthly rank and availability state, including missing readings and roster gaps. MCP get_leaderboards returns the same fields. See Monthly change and history.
  • 2026-10-07: Leaderboard facet combinations add nullable leader, the brand that leaderboard ranks first, with brand_id, name, slug and domain. The filtered leaderboard read adds months, every month its history covers, oldest first. MCP get_leaderboards returns the same fields. See Leaderboards.
  • 2026-10-07: Score v8.0 uses engine usage weights and a refit calibration. Stored reads and issued Snapshot reports with frozen per-answer facts serve v8.0. Reports issued on v6.0 and v7.0 remain available. See Versioning.
  • 2026-10-06: Placements on cross-industry leaderboard rows add score, the brand’s Heralded Score on that industry’s leaderboard, and ranked, the number of brands that leaderboard ranks. Their rows add strength, the best such score on a leaderboard ranking at least five brands. A list orders by best place, then by how many industries share it, then by name, and filtered to one brand origin, by strength first. MCP get_leaderboards returns the same fields. See Leaderboards.
  • 2026-10-06: Only score version v7.0 is served. A shared scan on v6.0 now returns 410 with code scan_version_unsupported, as older versions already did. See Versioning.
  • 2026-10-06: The legacy /public/categories routes are removed. Read public leaderboards through /v1/leaderboards, including facets and brand and source details. See Leaderboards.
  • 2026-10-05: Public leaderboard sources, cited pages, brand sources, questions and quotes withhold a stable sample keyed by entity kind, identity and measurement month. The bottom 70% of the SHA-256 range is withheld, with position 1 always sent and positions beyond 20 omitted. The existing withheld field reports the withheld positions in the full list. Totals and response shapes stay unchanged. REST and MCP use the same sample, including brand and source pages. See What the public leaderboards show.
  • 2026-10-05: The brand leaderboard read and MCP get_leaderboards add questions with per-question place and named competitors, engine_ranks with average rank, ranked leaderboard count and best rank, highlights with selected sentence quotes and their question and leaderboard context, and history_series with monthly score, Mentioned and Recommended values per placement. Each new module has its own paging offset. Existing won, missed, competitors, engines, history and their paging parameters remain available. evidence keeps its row shape and selects the same quotes as highlights. See Brand and source pages.
  • 2026-10-05: Leaderboard sources, cited pages, a brand’s sources and questions won and missed, and evidence quotes add withheld and send only positions 1–2 and 7–20, with positions 3–6 withheld on the server. Totals count the full list, offsets keep their original positions, and these modules stop paging at position 20. Rankings, engine lists, placements, competitors and history keep ordinary paging. MCP get_leaderboards follows the same rule. See What the public leaderboards show.
  • 2026-10-05: Leaderboard facet combinations add nullable featured_position, the curated display order for measured combinations. MCP get_leaderboards returns the same field. See Leaderboards.
  • 2026-10-05: Leaderboard brand rows add engines, each engine’s Mentioned and Recommended for the filter, with null values where the engine did not read the brand. Source rows add answers, the answers in the filter citing the source, beside citations. Question rows add language. MCP get_leaderboards returns the same fields. See Leaderboards.
  • 2026-10-05: Public leaderboard reads add GET /v1/leaderboards, /leaderboards/facets, /leaderboards/brands/{slug} and /leaderboards/sources/{domain}, with published measurements, independently paged modules, IP and site-key limits, caching and revalidation. MCP adds token-authenticated get_leaderboards over the same reads. See Leaderboards.
  • 2026-10-05: Trend instrument keys add nullable passes. A recorded pass-count change prevents comparison; a missing count keeps comparisons unchanged. See Change.
  • 2026-10-05: Single pages and MCP get_page add funnel_series, the funnel on each weekly report’s 28-day window, oldest first, back as far as your plan’s history reads. Each point carries start, end, search_clicks, crawled, fetched_live, cited and ai_visits, with null for a measurement the report did not record. See Pages, topics and Audit.
  • 2026-10-05: One page and MCP get_page add takes, with with_takes, takes_limit and takes_offset: the passage each answer lifted from the page and the claim it supported, one per prompt and engine. Takes are kept with each scan, so as_of returns the same takes after a page edit, a later scan or answer-text expiry. unavailable counts citing answers whose take could not be kept. See Pages, topics and Audit.
  • 2026-10-04: Page funnel windows add history_days and clamped. Crawler, Visits from AI and Search Console measurements read back 90 days on Core and 13 months on Plus, as_of pins included, and a funnel on an older report has null for them. See History.
  • 2026-10-04: Shared scans add source_tier_rollups[].citation_share_pct and brand_citation_summary.owned_share_pct, competitor_share_pct and independent_share_pct. Race rows add gap_pts, the row’s Heralded Score minus the subject’s. See Scans.
  • 2026-10-04: Segment engine rows add figure, and engine-screen Mentioned and Recommended cards add kpis[].figure, in the API and MCP get_segments. They share the answer-based values, ranges and measurement states of scores filtered to the segment and grouped by engine over 1w. See Segments in the API.
  • 2026-10-04: GET /v1/brands/{brand_id}/scores and /competitors, with MCP get_scores and list_competitors, accept cursor and return next_cursor for the Engines table, engine pane competitors and Competitors leaderboard they page. GET /v1/organizations/{organization_id}/brands rows add data_as_of, the scan their figures read, to pass as as_of to that brand’s reads. MCP list_portfolio serves the workspace’s portfolio. See Errors and limits and Connect an assistant.
  • 2026-10-04: Audit page rows and MCP get_audit add a fifth access gate, ai_crawler_refused. It fails where Cloudflare verified that an AI crawler was refused on the page or got not found from a live page. Changes and MCP list_changes add the insight kind ai_crawler_refused, whose work is a technical_fix action. See Page stats.
  • 2026-10-04: Page funnels add crawler_bots, counting served requests per bot with verification true or unknown, including search engines. Known-unverified AI requests remain in funnel.unverified; existing all-served bot totals keep their meaning. See Pages, topics and Audit.
  • 2026-10-04: Owned page lists, single pages, Audit page rows and MCP get_page add funnel, with one dated window for search clicks and impressions, AI crawls, live fetches, citations, Visits from AI, blocked, not-found and unverified requests, search-engine crawls and crawler sources. Unmeasured counts are null; WordPress requests with unknown verification count toward AI crawls and live fetches. See Pages, topics and Audit.
  • 2026-10-04: Page crawler breakdowns add category, also served by MCP get_page. Counts use daily source precedence so a connection outside the plugin replaces overlapping plugin counts. See Pages, topics and Audit.
  • 2026-10-04: GET /v1/brands/{brand_id}/prompt-suggestions and MCP list_prompt_suggestions add suggestions, the picker’s list for tracking a new prompt, with each entry’s text, intent_label and reason. It is not paged and does not change items. See Connect an assistant.
  • 2026-10-04: Single prompts and MCP get_prompt add each engine’s display name and the four measured states for its latest answer, including its answer id and read date. The facts follow the same latest-answer rule and as_of scan pin as the existing engine state. See Prompts.
  • 2026-10-04: One owned page, topic and competitor, including their MCP reads, add citation_evidence and unavailable_scans. Competitor-page panes add the same fields and measurement unavailable when the period has incomplete citations and no evidence for a known competitor’s page. See Figures in the API.
  • 2026-10-04: Sources and MCP list_sources accept sort=priority and return each site’s priority position and priority_reason. with_summary=true adds up to three actionable worth_pursuing suggestions and worth_pursuing_total. See Sources in the API.
  • 2026-10-04: GET /v1/brands/{brand_id}/changes, /prompt-suggestions and MCP list_changes and list_prompt_suggestions accept cursor and return next_cursor. See Errors and limits.
  • 2026-10-04: Work jobs and MCP get_work add holder, who holds the job’s action, with the same values as holder on actions. See Action fields.
  • 2026-10-04: Before launch, every answers_link drops its total: it carries the href or url of the answers alone, and the Answers page owns the count. This covers every /v1 read and MCP tool that returns one.
  • 2026-10-04: The overview and MCP get_brand_overview add heralded_score_band, score_bands, score_context, since_started and verified_actions, and with_diagnosis=true adds diagnosis. One action and MCP get_action accept as_of and add the action’s state, verbs, job, costs, impact, demand, schedule, assignee, current draft and its recipient, the application’s planned value and effect, and the weekly reports that raised it. Work jobs add action_id, action_kind, progress and current_step. The overview and Changes pin the latest completed scan by default, daily updates included, and name it in meta.data_as_of; the overview’s figures still describe the weekly reports in the period. Changes under that pin include the daily updates since the latest weekly report, as Home does. See Figures in the API and Action fields.
  • 2026-10-04: GET /v1/shared/scans/{share_id} can answer 410 with code report_retired, domain and rescan_url for a report retired with Heralded’s pre-launch data. See Errors and limits.
  • 2026-10-04: cited_page_key on the answers list and MCP list_answers: the document key of the page the cited_page filter matched. See Prompts and answers in the API.
  • 2026-10-04: Prompt list cursors issued before 4 October 2026 return 400 invalid_cursor; request the first page again.
  • 2026-10-03: Perception, scores, sources, cited pages, owned pages, topics and Audit add the labels, summaries, menus and evidence their pages and panes show. Scores add opt-in axis panes; owned pages add opt-in Search Console metrics. Lists add search, sorting and evidence paging. The existing MCP tools return the same fields and accept the same parameters. See Figures in the API.
  • 2026-10-03: Before launch, /v1 source ownership counts discovered competitors’ sites as competitor-owned. This includes non-channel brands discovered across the selected period with at least three naming answers, alongside the competitors you track today. Sources, cited pages, engine panes and MCP use the same ownership. See Sources.
  • 2026-10-03: Scores and MCP get_scores add optional Engines table and pane reads, with counts, sentences, prompt evidence and sources. Competitors and MCP list_competitors add filters and an optional page read with leaderboard, discovered cells, share-of-voice bar and brand roster capacity. One competitor and MCP get_competitor add measurement and comparison sentences, capacity, answers link and an optional competitor-page pane with its explanation, prompts and queued actions, including daily-only discoveries under the same scan pin. See Figures in the API.
  • 2026-10-03: Prompt lists add the composed status_note for paused and archived prompts and cells with their engine readings, answer ids and measured-day labels. MCP list_prompts returns the same fields. See Prompts.
  • 2026-10-03: Prompts add period scores, trends, engine marks, taxonomy, filter menus and table selection. Single prompts add the composed sentence, tiles, engine cards and linked work. Answers add four-axis states, highlights, citation titles, filter menus and table selection; single answers accept as_of. Scores add optional cards for the Prompts band. The existing MCP tools return the same additions. See Prompts and answers in the API.
  • 2026-10-03: Brand settings and MCP get_settings add prompts_used, the brand’s active prompt count, and prompts_reserved, its current reservation or null for the shared pool. Brand grants can read this meter. Workspace usage still requires workspace access. See Usage in the API.
  • 2026-10-03: Segment reads add the complete comparison table, a segment’s figures, trend and prompt evidence, and its selected engine’s prompt answers. Read them through GET /v1/brands/{brand_id}/segments, /segments/{segment_id} and /segments/{segment_id}/engines/{engine_id}, or MCP get_segments. See Segments in the API.
  • 2026-10-03: Read the Content read of a Snapshot or Audit you ran through GET /v1/scans/{scan_id}/audit: every audited page ranked best fix first with what it fails, the page checks, the site’s readability and the topics the site has no page for. Only the account that ran the scan reads it, and the shared read of a Snapshot never carries it. MCP get_audit takes scan_id in place of brand for the same read. See Scans in the API.
  • 2026-10-03: List the Snapshots you ran through GET /v1/scans, with the rows, paging and cursor of a brand’s scan list. Scan rows add domain, share_id, progress_pct and failure_reason, one of stuck_no_progress, brief_abandoned, insufficient_engine_signal, cost_cap_exceeded, report_inputs_missing or other on a failed scan, and GET /v1/scans/{scan_id} adds failure_reason. See Scans in the API.
  • 2026-10-03: Answers add an optional period to GET /v1/brands/{brand_id}/answers and MCP list_answers. Omitting it keeps all weekly and daily answers. Finished answers read frozen measurements. Brands named in answers now come from the detection frozen with each scan, not a text match: the names filter matches the brands detected in an answer and the tracked competitors it names, and rivals_named uses the frozen detection.
  • 2026-10-03: Read brand profiles, owned domains, tracked competitors, autonomy, connection status and segment configuration through GET /v1/brands/{brand_id}/settings and /segments, with MCP get_settings. Workspace members can read prompt and credit use through GET /v1/organizations/{organization_id}/usage and MCP get_usage. GET /v1/organizations/{organization_id}/brands returns portfolio rows with the last week’s figures, paired changes and actions waiting; managed=true selects the manager’s active managed accounts. Brand grants alone open neither workspace read.
  • 2026-10-03: List a brand’s weekly reports, daily updates and Snapshot through GET /v1/brands/{brand_id}/scans, and read one scan’s progress or issued Heralded Score, Mentioned, Recommended and readiness through GET /v1/scans/{scan_id}, with MCP get_scan. Read a delivered report as its link holders see it, with no API key, through GET /v1/shared/scans/{share_id}. See Scans in the API.
  • 2026-10-03: GET /v1/brands/{brand_id}/overview and MCP get_brand_overview add next_weekly_scan_at, next_daily_scan_at, daily_scans_since_weekly, open_action_count and readiness. See Figures in the API.
  • 2026-10-03: Read Perception’s statement, positioning rows, claims with their verdicts and trend, negative prompts and sources, and best quotes through GET /v1/brands/{brand_id}/perception. Read one claim through /perception/claims/{claim}. MCP get_perception serves either read with an optional claim key. Both accept the period, shared figure filters and as_of. See Perception in the API.
  • 2026-10-03: Sources adds read_pages_naming_you, citation share, answers citing, authority and opportunity score. Sources reads report citation evidence availability and how many reports lack it; unavailable counts and history points are blank. citations_naming_you is deprecated and keeps counting all citations naming you, including unread pages. Sources and cited-page rows accept shared filters, including engine. Read a site’s pane through GET /v1/brands/{brand_id}/sources/{domain} and get_source, and cited-page rows through GET /v1/brands/{brand_id}/cited-pages and list_cited_pages. Overview’s top sources add citation share and the read-pages naming-you count.
  • 2026-10-03: Read one action’s steps, thread, drafts, application state and evidence through GET /v1/actions/{action_id} and MCP get_action. Read agent jobs, the next scan, weekly tallies and the Herald’s week through GET /v1/brands/{brand_id}/work and MCP get_work. See Action fields.
  • 2026-10-03: Read one competitor through GET /v1/brands/{brand_id}/competitors/{key} and MCP get_competitor, with score, trend, head-to-head figures, prompts won and lost, engines, cited pages and tracked since. Competitor lists include discoveries across the selected period and add a separate channels list.
  • 2026-10-03: GET /v1/brands/{brand_id}/scores and get_scores take engine, type, intent, topic, segment and prompt filters and a group_by of engine, intent, type, topic, segment, prompt or competitor. A grouped read adds groups, each with its group and its five figures. See Figures in the API.
  • 2026-10-03: Read your own pages through GET /v1/brands/{brand_id}/pages and /pages/{page_id}, Content’s topics through GET /v1/brands/{brand_id}/topics and /topics/{topic_id}, and Audit through GET /v1/brands/{brand_id}/audit, with MCP get_page, get_topics and get_audit. AI visits read the newest weekly report in the period that read the GA4 property connected now.
  • 2026-10-03: Read one prompt’s period score and trend, each engine’s latest answer, competitors, top sources, tracking date and status through GET /v1/brands/{brand_id}/prompts/{prompt_uid} and MCP get_prompt.
  • 2026-10-03: In GET /v1/brands/{brand_id}/competitors and list_competitors, share_of_voice_pct and a share_of_voice row’s pct are null for a tracked competitor that no answer in the period asked about or named, where they read 0.
  • 2026-10-03: Computed reads add normalized query metadata and an as_of scan pin. Prompts, answers, sources, AI visits and actions add cursor pagination. MCP tools accept the same parameters and return the same metadata. Authenticated responses state their rate limit, 429 bodies carry its numbers, and REST problems include the request id. See Errors and limits.
  • 2026-10-03: Read Home’s Changes through GET /v1/brands/{brand_id}/changes and MCP list_changes. Read Discover recommendations, provenance, form and demand through GET /v1/brands/{brand_id}/prompt-suggestions and MCP list_prompt_suggestions.
  • 2026-10-02: Every response has Cache-Control: private, no-store.