VetAgent · last updated 2026-09-04
No accounts, no cookies, no browser tracking. VetAgent has no user database and serves no third-party scripts.
Our analytics never records the token address. That query is the most sensitive thing you send us — it can reveal what you are about to trade — so it is used to fetch public data and then discarded with the response. This is a deliberate trade: it means we cannot tell you which tokens are popular, and we consider that the correct side of the trade for a tool whose only asset is trust.
We do keep aggregate usage counts, so we can tell whether anyone is using the service. Each call records: which method and tool was invoked, the resulting risk level, whether it errored, a coarse client name taken from the user agent, and the country code Cloudflare attaches at the edge. No IP addresses, no full user agents, no token addresses, nothing that identifies a person or a request.
The line above is about what we record, and it is enforced in code. It is not
a claim about the internet. The convenience route GET /assess/<address>
carries the address in the URL, and URLs are visible to the platform serving the request
and to anything between you and it. We do not control those logs and neither do you.
If that matters for what you are looking up, use a route that keeps the address out of
the URL: the MCP endpoint at /mcp is a POST and carries it in the body, and
POST /assess accepts {"address": "0x...", "chain_hint": "..."}
for the same reason. Same answer, same code path.
To answer a request we query these public APIs, sending only the token address:
eth_getCode to read the contract's own bytecode and see which
powers it holdsThat last line was missing until 2026-09-09. The three RPC endpoints have received
the token address on every EVM assessment since the owner-powers check shipped, and this
page listed four recipients as though the list were complete. It is corrected here rather
than quietly, and tests/test_http_telemetry.py now fails the build if the
engine gains an outbound host this list does not name.
These are third-party services with their own privacy policies. We never send them wallet addresses, identities, or anything about who is asking.
Cloudflare, which serves this Worker, keeps standard edge request metadata (IP, timestamp, path) for operational and abuse-prevention purposes under its own policy. We do not export, retain, sell, or analyse it, and we do not join it to anything else.
VetAgent reports observable on-chain risk. It is not investment advice, does not
size positions, and cannot detect off-chain risk. A low verdict means
"no fatal signal found in the checks that ran" — never "safe to buy". A verdict
of unknown means a critical check could not be completed and must not be
read as low risk.
Questions about any of the above, or about data this service holds on you (it holds none, and this page explains why): hello@vetagent.dev. Anything public — bugs, a verdict you disagree with — is better as an issue at github.com/jakegu1/vetagent.