BuzzSumo tells a content team what already worked: the articles, the shares, the links. Trends API tells it what to write next. Send a topic and get weekly demand on a 0-100 scale, growth over named windows, and the live boards for today. The two tools look at the same internet from opposite ends of the publishing date. This page is for the planning half of the job. The workflow version sits on Content calendar API.

Backward records, forward scores

A share count is a verdict on a finished piece. Useful for outreach and for copying formats that travelled. It says nothing about next month's topic, because the audience may already be bored. A demand series answers the calendar question directly: the topic over google search, youtube, tiktok, and reddit, one POST per source, one scale for all four. Rising topics get slots. Flat ones get skipped before the brief costs a day.

The weekly planning pull

get_top_trends reads the boards (Google Trends, TikTok Trending Hashtags, YouTube Trending) for the spikes of the day. get_growth checks whether a spike has a quarter behind it or only a weekend. That two-call screen replaces the gut-feel agenda meeting, and the rows it returns can sit in the same sheet as the calendar. The creator-side version of this routine sits on Creator trends API.

Where BuzzSumo still wins

Backlink prospecting, author research, and audits of a competitor's archive need an index of published content with engagement records. No demand score substitutes for that. Keep the seat that owns the archive. Only successful 200 responses count against quota here; caps sit on pricing.