Comparison
api-relay-audit vs hvoy.ai vs cctest.ai
These tools answer related but different questions. API Relay Audit is a local, open-source, repeatable audit script. hvoy.ai is useful for relay reputation lookup and public relay observations. cctest.ai focuses on low-friction web checks and Claude channel fingerprinting.
Positioning
| Tool | Best fit | Trust tradeoff |
|---|---|---|
| API Relay Audit | Local audit reports, reproducible evidence, security review before production or wallet traffic. | You run the code locally and can inspect it; CLI use is less convenient than a web form. |
| hvoy.ai | Relay lookup, public observations, operator and user reputation signals. | Useful discovery surface; not a substitute for a local audit of your own route. |
| cctest.ai | Fast Claude-oriented web checks and channel fingerprinting claims. | Lower friction; users still need to decide whether to trust the web checker with sensitive inputs. |
Where API Relay Audit is intentionally different
- It runs locally, so the extra checker server is removed from the API-key path.
- It produces a Markdown report that can be reviewed, redacted, and attached to issues.
- It keeps `inconclusive` separate from `clean`.
- It maps important probes to relay supply-chain risks such as AC-1, AC-1.a, and AC-2.
Not a winner-takes-all claim
Use the tool that matches the question. If you want public relay discovery, a reputation surface may be useful. If you want a local report for your own key, route, and workflow, run API Relay Audit. If you need channel-fingerprint research, track the design memo before treating it as implemented here.