Every check PolicyCodex records comes from one of three places. API usage breaks down how many, and which.
Reporting → API usage with checks-run and per-source tiles

​
Tiles

  • Checks run — total checks in the selected period.
  • via Action — checks reported by the GitHub Action running in a repository’s own workflow.
  • via App — checks run server-side by the GitHub App, with no workflow required.
  • via full scan — checks from a user-triggered full-repo scan, evaluating the whole repository rather than a diff.
Only sources that actually reported a check in the window appear — a quiet org running only the Action for a week sees one tile, not three empty ones.

​
What it’s for

This is an adoption and cost-shape signal, not a compliance one — pair it with Scope (which repos) and LLM cost (what each check costs) rather than reading it alone. A sudden jump in via full scan volume, for example, is worth knowing about before it shows up as a token-cost surprise.