Actor Quality Readiness Auditor avatar

Actor Quality Readiness Auditor

Pricing

Pay per usage

Go to Apify Store
Actor Quality Readiness Auditor

Actor Quality Readiness Auditor

Audit public Apify Actor pages for Store-readiness, quality signals, monetization fit, pricing advice, and concrete fixes.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

X L

X L

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Local prototype for the next Apify product candidate.

It audits public Apify Actor pages and returns:

  • PUBLISH, FIX, AVOID, or ERROR
  • readiness score
  • public stats
  • missing Store quality signals
  • maintenance/deprecation flags
  • monetization fit: HIGH, MEDIUM, or LOW
  • agentic/MCP fit: HIGH, MEDIUM, or LOW
  • x402/PPE readiness: READY_FOR_PRIVATE_TEST, FIX_FIRST, or NOT_READY
  • pricing advice for free, usage-cost-only, or later PPE testing
  • next actions before publishing or enabling paid PPE
  • Markdown report in key-value store record REPORT

Usage

cd D:\Project\SecurityAudits\actor-quality-auditor
node .\audit.js https://apify.com/thenetaji/apify-actor-monitor
node .\audit.js --json https://apify.com/apify/monitoring
node .\audit.js --out sample-output.json https://apify.com/thenetaji/apify-actor-monitor

Apify Actor

This directory is also an Apify Actor package.

cd D:\Project\SecurityAudits\actor-quality-auditor
npm install
npm start

Actor files:

  • .actor/actor.json
  • .actor/input_schema.json
  • .actor/output_schema.json
  • .actor/dataset_schema.json
  • assets/icon.svg
  • src/main.js
  • src/run-audit.js
  • APIFY_CONSOLE_PUBLISH_PACK.md
  • PPE_RELEASE_NOTES.md
  • STORE_LISTING_DRAFT.md
  • PUBLISHING_CHECKLIST.md

Before publishing:

npm test
npm pack --dry-run

Validation

cd D:\Project\SecurityAudits\actor-quality-auditor
npm test
node .\audit.js --out sample-audit-2026-07-02.json `
https://apify.com/thenetaji/apify-actor-monitor `
https://apify.com/apify/monitoring `
https://apify.com/artificially/github-repo-scraper

Current sample output:

  • thenetaji/apify-actor-monitor: PUBLISH 96/100, monetizationFit=HIGH
  • apify/monitoring: FIX 78/100, monetizationFit=MEDIUM, with stale-last-modified and missing-output-tab
  • artificially/github-repo-scraper: AVOID 58/100, monetizationFit=LOW, due to under-maintenance
  • sample artifact: sample-audit-2026-07-02.json
  • MCP/x402 fields are present in the sample: agenticFit, x402Readiness, x402Signals, and agenticNextActions

Current Actor validation:

  • unit/config/wrapper tests pass
  • npm pack --dry-run includes schemas, CLI, core, sample, and Actor source
  • local npm start with empty input initializes the Apify SDK and exits successfully
  • PPE-ready path exists: set PPE_EVENT_NAME=audited-actor only after configuring the same event in Apify Console

Actor outputs:

  • default dataset rows, one per audited Actor URL
  • SUMMARY key-value-store record with verdict counts and charge counters
  • REPORT key-value-store record with a human-readable scorecard, pricing advice, MCP/agentic readiness, x402/PPE readiness, and release next actions

Agentic / x402 Readiness

Apify's newer monetization and agent workflows make MCP, API, visible pricing, and clean paid-event units more important for Actor creators. This auditor now checks those public Store signals and emits:

  • agenticFit
  • x402Readiness
  • x402Signals
  • agenticNextActions

The intended paid boundary remains conservative: do not enable paid events on the first public release. Use x402Readiness=READY_FOR_PRIVATE_TEST as a signal for later private PPE/x402 testing after organic usage and run cost are measured.

Product Hypothesis

Apify builders need a low-friction way to check whether their Actor looks publishable before asking users to run it.

This product is better aligned with low-communication income than lead generation because the output is a self-contained scorecard, not a promise of fresh leads.

Pay-Per-Event Readiness

The Actor is wired for a future PPE event without enabling charging by default.

When Apify Console has a matching event configured, set:

$env:PPE_EVENT_NAME = "audited-actor"

With that environment variable present, each successful non-ERROR audit row is pushed with the audited-actor event name. Error rows are still stored but are not charged. The SUMMARY value records:

  • chargeEventName
  • chargeAttempts
  • chargedCount

Do not set PPE_EVENT_NAME until private Apify tests confirm the event is configured and the run budget behavior is acceptable.

Local Live Smoke Evidence

Latest local public-source smoke test:

  • source URLs:
    • https://apify.com/thenetaji/apify-actor-monitor
    • https://apify.com/apify/monitoring
    • https://apify.com/artificially/github-repo-scraper
  • result:
    • PUBLISH 96/100 for thenetaji/apify-actor-monitor
    • FIX 78/100 for apify/monitoring
    • AVOID 58/100 for artificially/github-repo-scraper
  • artifact: sample-audit-2026-07-02.json