Free tool 9 · Agent Stack Scan
How to find the vendor change that will break your agent's payments, and the key that will hit zero at 2am, before your users do, without reading a single changelog.
Point it at a public repo, or paste your package.json, lockfile, requirements or .env.example. It finds the vendors on your agent's money path and looks at them two ways: what can break without telling you (compromised or deprecated versions, retired hosts, protocol splits, single paths) and what needs a human to keep running (prepaid credit, KYC'd accounts, expiring tokens). Every finding links to its source and date.
Your code, lockfile contents and env values never leave your browser. Only the package names that match the rule pack, and the repo address if you give one, go from your browser to the public sources named on the result. Nothing else leaves your browser, and nothing comes to us.
Or try an example first
Or paste or drop your files
Want a second pair of eyes on one real workflow?
This tool checks which vendors on your agent's money path can break or need a human from what you typed. It can't see your code, keys, contracts or production traffic. If the result shows gaps, send me one real workflow. In my free 48-hour integration review I go through it end to end and send you a written report: fit, dependencies, permission risks, acceptance tests and a build or don't-build-yet call.
I take the hop or gate that breaks first and map that one workflow end to end: vendor contract tests in CI, the fallback plan (second facilitator, RPC or price source; stop, retry or pay again), per-agent keys and spend caps for prepaid vendors, and what the agent does at zero balance, 401, 402 and 429.
Contact: Shilpa Goel, [email protected]
This is an engineering checklist, not a security audit, legal, compliance or investment advice.