Real-time access to X with native search. The signal Perplexity and Claude can't reach. Bundled with X Premium+ at $30/mo, so if you already have the X subscription, the research add-on is free.
Live trend research
The web's lag and the chat-LLM's training cutoff make 'what's happening this week' research painful. Grok pulls live X chatter, Perplexity grounds in cited sources, Claude turns the two streams into a 5-bullet brief you can hand a colleague. 30-min weekly habit replaces 4 hours of tab-switching.
Grok tells you what people are saying; Perplexity tells you what actually happened (with links). Pair them: catch the wave from Grok, verify from Perplexity.
Long-context turn that takes both feeds and outputs a 5-bullet brief. Same prompt every week makes the briefs comparable.
- grokFree with X Premium+ if you have it
- perplexityFree tier
- claudeFree tier
- grok$30 X Premium+
- perplexity$20
- claude$20
- grok$40 SuperGrok
- perplexity$20
- claude$70 (Pro + API top-up)
Fast mode for Claude Opus 4.8 deprecated with November 30 removal date
Fast mode for Claude Opus 4.8 is being deprecated and will be removed on November 30, 2026. Developers using fast mode with Opus 4.8 must migrate to Claude Opus 5.5 to continue using the feature.
Usage and Cost Analytics API launched in beta to track token consumption and costs
Anthropic released the Usage and Cost Analytics API in beta, enabling organizations to monitor token usage and costs across Claude API consumption with filtering and grouping by dimensions like model, workspace, and API key. The API provides /v1/organizations/analytics/usage and /v1/organizations/analytics/cost endpoints. Legacy usage reporting endpoints remain supported.
Messages API and Token Counting API maximum request size increased to 128 MB
The maximum request size for the Messages API and Token Counting API doubled from 32 MB to 128 MB on the first-party Claude API, allowing developers to process significantly larger payloads in single requests. This change takes effect immediately and applies to both APIs.
Claude Tag API released in beta for Claude Enterprise organizations on Slack
The Claude Tag API is now available in beta for Claude Enterprise organizations, providing endpoints to read and configure Claude Tag settings on Slack channels and workspaces with Access bundle support. The API requires Admin API keys with read:claude_tag or write:claude_tag scope. This feature is exclusive to Claude Enterprise.
- 1Live pulse from GrokGrok
Ask Grok what people are saying about your topic this week, with a real-time anchor.
Prompt · Live trend pulse on GrokWhat is X actually saying about {{topic}} in the last 7 days? Output, in this order: 1. **Three angles** people are arguing about — what's the disagreement, who's on each side, ~2 representative posts each (with handles). 2. **One contrarian read** — a post from a credible voice that pushes against the consensus this week. 3. **Two under-radar things** — observations from accounts under 50k followers that the larger accounts haven't picked up yet. 4. **Volume signal** — is this topic trending, holding, or decaying compared to last week? Cite handles and post links. No paraphrased filler. No "experts say". - 2Verify with PerplexityPerplexity
For each angle from Grok, pull the underlying primary source. Don't synthesize on rumor.
- 3Synthesize with ClaudeClaude
Both outputs into Claude. One brief out the other side.
Prompt · 5-bullet weekly trend briefSynthesize the two inputs below into a brief I can read in 90 seconds. Live pulse (Grok output): """ {{paste Grok output}} """ Cited sources (Perplexity output): """ {{paste Perplexity output with links}} """ Output (in this order, ready to paste into a doc or Slack): 1. **TL;DR** — one sentence, the single thing I should know this week. 2. **What's actually happening** — 2 to 3 bullets, each with a date and a primary-source link. 3. **What people are arguing about** — 1 to 2 bullets, each with a representative quote. 4. **The under-radar story** — 1 bullet on something the big outlets missed. 5. **What changed since last week** — 1 to 2 bullets, comparison to the prior brief. Constraints: - Every bullet has a name, date, or number. - No "in the rapidly evolving landscape", no "experts say", no "could have implications for". - No em dashes. Output as Markdown.
Replaced ~4 hours of tab-switching with a 30-min Friday habit. The Grok step caught a sentiment shift on a portfolio company 2 days before the public-news cycle. The combined brief now circulates internally; partners who used to skim Twitter manually skip that pass entirely.
X-trending isn't reality. The Perplexity step exists to ground the noisy signal. Skipping it means publishing rumor.
The value compounds when briefs are comparable across weeks. Lock the prompt + the structure; only change after a quarter.
What changed in AI tools and the stacks that ship. One email a week.