Phinq
Intercepts AI agent tool calls, classifies them by risk, and holds dangerous actions for human approval before execution.
≈ 2visits/mo
Emerging · estimate, read 2026-09-18
- For
- Teams deploying AI agents who need to prevent dangerous tool calls and maintain audit trails.
- Price
- Price not read
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- APISDK
- Approve or deny agent tool calls before execution
- Record tamper-evident audit logs of all agent decisions
- #77
CodeRabbit
Automatically reviews pull requests, prioritizes them by risk, and scans for security vulnerabilities.
24.4knot readFrom $24/user/mo2023 - #127
Greptile
Reviews pull requests and tests code changes using agent swarms to catch bugs and style violations across codebases.
8.5knot readFrom $30/user/mo - #132
Fluid Attacks
Scans applications for vulnerabilities using automated analysis and human penetration testing, prioritizes findings by exploitability, and generates remediation guidance.
4.3knot readFree plan - #139
Hacktron AI
Analyzes pull requests to find exploitable vulnerabilities and generates working proofs of concept before code ships.
68not readFrom $40/user/mo - #145
Whisper Internet Infra AI Context
Resolves IP addresses and domains to real owners, networks, and jurisdictions to block unauthorized connections.
65Active— - #178
KushoAI
Generates API tests from specifications, scans for security vulnerabilities, and validates complete workflows across services.
906not readFree plan
What is Phinq?
Intercepts AI agent tool calls, classifies them by risk, and holds dangerous actions for human approval before execution.
Who is Phinq for?
Teams deploying AI agents who need to prevent dangerous tool calls and maintain audit trails.
Do people use Phinq?
Emerging: ≈ 2 visits a month · estimate, 2026-09.
Is Phinq still maintained?
Maintained.
What are alternatives to Phinq?
In Developer tools, by use: CodeRabbit, Greptile, Fluid Attacks, Hacktron AI, Whisper Internet Infra AI Context, KushoAI.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.