Agent Verifier reference
Every field of the answer and every fault, generated from the code that answers.
On this page
Response reference
The tables on this page are generated from the code that builds the answer, so they match what you receive. The same contract in machine-readable form is at /openapi.json.
How to call it
GET https://fp.packet.guru/api/v1/connection with no body, no parameters and no credential. Send the ordinary request, signed the way you sign requests to anyone else. A signed request carries three standard headers:
Signature-Agent: where your keys are published, as a dictionary member keyed to your signature label per RFC 9651. The current draft makes the value the address of the key set itself, such assig1="https://example.com/.well-known/http-message-signatures-directory". The bare origin of earlier revisions,sig1="https://example.com", is read too. Cover that member in the signature as"signature-agent";key="sig1".Signature-Input: the RFC 9421 parameters. Thetagmust be"web-bot-auth", or the signature is not read as an agent signature at all.Signature: the signature itself.
Without them you still get an answer: plain facts about the address you came from are read for every caller, signed or not.
What comes back
A block marked varies is described rather than enumerated: its members depend on what you sent. A field that does not apply to a request is left out instead of being sent as null, so a missing key always means the field does not apply.
All 37 faults, and how to fix each
When a signature does not hold, the answer names one of these in signals.agent.webBotAuthDetail.reason and carries the remedy beside it. The full list is public so that every fault can be fixed from this page alone. The names are this check's own, grouped by subject. A public set of negative test vectors, webbotauth-negative-vectors, exercises the same names, and anyone building a verifier can run it against their own.
The table leaves out two things. The sentence in an answer is sometimes more specific than the row: where the situation allows it the remedy names the case rather than the family, so a directory answering a redirect is told about redirects, and a signature base assembled in a known-wrong shape is told which line to change. The row is the general answer for that fault. And bad-tag never arrives as a reason at all. A signature tagged for another profile was not addressed to this check, so the answer reports signature.present: false and carries the same advice as a note.
The outcome column places each fault in one of the three outcomes the draft's deployment guidance describes. invalid means a proof was presented and does not hold. unverified means the check could not reach a decision, for example because the key directory could not be read or did not list the key.
The signature itself
Faults in the signature headers themselves: the bytes, the parameters, or what they cover, including parts this check does not support.
The Signature-Agent header
The header that says where your keys are published could not be read, or does not point at one usable place.
Your key directory
The key directory the header points at could not be fetched, or no usable key directory came back from it.
The key you signed with
The directory was read, and the specific key your signature names is not usable from it.
What this does not claim
- A verified signature proves identity. Trust is separate. It proves the request was signed with a key the named domain publishes. Anyone can publish keys at their own domain, so a valid signature from an unknown name says who sent the request and nothing about whether to serve it.
- A directory that could not be reached costs nothing. An unreachable directory is a gap on this side, not a fault on yours, and the answer says so rather than counting it against the signature.
- Nothing unseen is reported as seen. When the request did not arrive directly,
provenancesaysunavailable, and no finding in that answer rests on something that was never read.
Further reading
- Agent Verifier: See Your Signed Request the Way a Server Sees It What breaks a setup in practice, from a signature base built a character differently to a directory a CDN refuses to serve.
- Replay Attacks: Why a Valid Signature Is Not a Fresh Request What a valid signature proves, what it leaves open, and why the created and expires window matters.
The standards behind this
For machines
- API catalog Every API here, each with its description and its documentation. Standard address, RFC 9727.
- AI catalog The AI artifacts this domain offers, for an agent discovering them on its own. It points to the MCP server card.
- openapi.json The response contract, machine-readable. The same source the reference page is built from.
- MCP server card What an MCP client reads before it connects: name, version, transport, and protocol versions.
- MCP registry entry What the official MCP registry publishes about this server: address, transport, and the tool it exposes.
- packet.guru key directory The public keys this site signs its own outbound requests with. A working example of the file you publish.
- packet.guru agent card What the fetcher on this site promises about itself, including the exact User-Agent it sends.