Skip to content

feat(cli): display actor usage stats in actors info command#1243

Open
MQ37 wants to merge 1 commit into
masterfrom
claude/apify-api-inconsistency-cszcfi
Open

feat(cli): display actor usage stats in actors info command#1243
MQ37 wants to merge 1 commit into
masterfrom
claude/apify-api-inconsistency-cszcfi

Conversation

@MQ37

@MQ37 MQ37 commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Adds actor usage statistics to the output of the apify actors info command, displaying total users, users in the last 30 days, and total runs.

Changes

  • Display actor stats (total users, users in last 30 days, total runs) in the actors info command output
  • Reuses the stats data already present in the actor GET API response, avoiding an extra API call
  • Mirrors the popularity metrics surfaced by apify actors search for consistency

Implementation details

The stats are extracted from the existing actorInfo response object and formatted with consistent styling (yellow labels, cyan values) to match the command's existing output format. The stats section is inserted before the builds section in the output.

https://claude.ai/code/session_01BM5nBJkiCY7wASaB29Xf65

`apify actors info <slug>` rendered pricing but no popularity numbers,
while `apify actors search` surfaces total users in the last 30 days.
The actor GET response already carries `stats`, so add an "Actor stats:"
section (total users, users in last 30 days, total runs) to the
human-readable output without an extra API call.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BM5nBJkiCY7wASaB29Xf65
@MQ37 MQ37 requested review from DaveHanns and l2ysho as code owners June 30, 2026 14:15
@MQ37 MQ37 changed the title Display actor usage stats in actors info command feat(cli): display actor usage stats in actors info command Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants