Twitch Data for AI Agents: Query Streams Charts in Claude Code

Loading

Getting viewership statistics from Streams Charts is straightforward: open the website, select your filters, and find the channels or rankings you need. This works well for a quick lookup. Deeper analysis takes more steps, especially when you need to compare creators, switch reporting periods, or check additional metrics. Each follow-up adds more navigation and more figures to collect.

As these requests build up, you start looking for a faster, simpler way to get the data without searching the website manually each time.

Every follow-up sends you back to the website

Your colleague asks for the most-watched Twitch channels over the past week. You open Streams Charts, select the period, and put together a table. Then comes the follow-up: “Which of these channels had the highest Average Viewers?” You sort the results again. “And how did the leaders perform last month?” Now you need another period and another comparison.

Each question is straightforward, but answering the full sequence means moving between rankings, channel pages, and your working document. You also need to keep track of which figures belong to which period. As the brief changes, more of your time goes into collecting and arranging the numbers.

You already know where to find the data. What you need is a way to ask the next question without repeating the search - and to see which source, reporting period, and metrics support the answer.

How you assemble the answer manually

Start in the Channels ranking: select Twitch, set the reporting period, and sort by Hours Watched. Copy the relevant channels into your working table alongside Hours Watched, Peak Viewers, and Average Viewers. Record the dates and source URL so your colleagues know what the comparison covers.

If the next question concerns those same channels and dates, use the figures you already collected. A request for last month’s performance sends you back to Streams Charts: change the period, find the selected channels, and add their results to your table. Check that both rows cover the same dates before calculating differences.

The Claude Code skill brings that sequence into one conversation. You specify the question, and the agent retrieves and formats the data. Your role shifts from navigating pages and copying figures to checking the request and interpreting the result.

Twitch data for AI agents: three steps in Claude Code

Start with a free Twitch ranking, then ask follow-up questions about the results. This walkthrough uses Claude Code on your computer, not the regular claude.ai chat.

Step 1. Install the skill and connect your API account

Download the skill from the setup page. Extract the streamscharts-api folder into ~/.claude/skills/, or into .claude/skills/ inside your project. Start a new Claude Code session and enter /streamscharts-api.

Load the Streams Charts skill after configuring your API credentials

Step 2. Ask your first question with the free request

Enter a request that specifies the platform, period, and ranking metric:

“Get the top 100 Twitch channels by Hours Watched for the last seven days using the free request. Do not add filters or fetch additional pages. Show the top 10 with Hours Watched, Peak Viewers, and Average Viewers.”

The underlying request retrieves the first 100 channels; your instruction limits the displayed table to ten. Under these conditions, the API request costs 0 credits.

“Check the platform, reporting window, column labels, and reported cost before using the figures.”

Retrieve 100 channels at zero API credits and display the ten leaders by Hours Watched

Step 3. Look closer at a channel

Move from the ranking to a creator you want to explore. Ask for their performance over a specific period:

“Show shroud’s Twitch statistics for the previous calendar month: Hours Watched, Peak Viewers, Average Viewers, Airtime, and Followers Gain”.

This standard channel request costs 1 API credit. The answer gives you a closer look at the creator’s performance beyond their position in a ranking.

Continue with a comparison:

“Get the same metrics for the month before that. Put both months side by side and calculate the percentage change in Hours Watched and Average Viewers.”

Retrieving the second month costs 1 additional API credit. The two requests cost 2 credits in total; calculating the changes from those results requires no further API calls. Check the reported usage in API access history.

Explore a creator’s performance and compare reporting periods in the same conversation

Check the answer against the source

Before using the results, check one channel against the original API response. Confirm that the channel, platform, dates, and figures match.

Keep in mind that Claude Code follows your instructions closely, so be specific in your prompts and follow-up requests. For example, if you retrieve the top 100 channels by Hours Watched for a given period and then want to sort them by another metric, explicitly ask Claude Code to use those same 100 channels. Otherwise, it may generate a new ranking instead of reordering the existing results.

What the skill does - and what you still need to check

The skill translates your question into an API request and formats the response. You still need to check that it selected the right platform, reporting period, metrics, and filters. State these explicitly in your prompt, especially when comparing channels or asking for a ranking.

The skill runs in Claude Code on your computer. It does not work in the regular claude.ai web or mobile chat. Streams Charts API credits and Claude Code usage are separate costs.

A follow-up question is not automatically free. Sorting an existing response needs no new API call; requesting another period, platform, or page does. Ask the agent to state the expected cost before retrieving more data, then check the recorded usage.

Testing mode returns synthetic records for checking the integration. Those records are not evidence of a creator’s performance. Metric availability and historical coverage also differ by platform, so an unavailable value must not be treated as zero.

For a quick lookup on one channel, the website remains a straightforward option. Use the skill when several questions build on each other and you want to keep the analysis in one conversation. For a recurring dashboard, use a scheduled API integration rather than relying on someone to repeat prompts.

Run your first free query

Your first request costs 0 API credits: retrieve the top 100 Twitch channels by Hours Watched for the last seven days, without additional filters. Set up the Streams Charts skill and run the query in Claude Code. Claude Code access and usage costs are separate.