Connect your CLI and CI to a shared scan cache. Manage your team, usage, and billing in one place.
Continue with GitHub →$ perch login $ perch scan
Cached answers don't count toward your allowance.
Your team's scans, in one place.
Sign in, choose this organization, and register your repository.
$ perch login $ perch scan
Code is sent to the model when needed. The cloud cache stores request hashes and typed answers.
A repository groups shared answers and limits CI credential access. No GitHub installation is required.
Each member needs a paid seat. Invitations reserve an available seat.
Credentials can scan one repository. Save the token in your CI secret store as PERCH_TOKEN.
It is shown only once. Keep it out of source control and logs.
10,000 uncached analyses per paid seat, pooled across your organization.
Uncached scans pause at the limit. There are no automatic overage charges.
Seat changes and cancellations are managed in Stripe. Failed analyses do not consume scan units.
Each repository has its own cache inside your organization. Source code and question text are used transiently for inference; durable cache entries contain request hashes and validated answers.