Reads the ASP manifest (/.well-known/agent-shelter.json) of a host and summarises it: protocol version, compliance level (L1-static, L2-transactional, L3-observatory), ingress routes, transport envelope, receipt-signing key, resolution methods and recording rules. Default host: https://agent-shelter.org, the ASP reference node. The manifest is a discovery document: a node with discovery correlation records a terminal signal that follows from the same network within its correlation window, and a node with discovery counters counts the request in aggregate (per document and client class, no address).

Calls the header echo of the ASP reference node (GET https://echo.agent-shelter.org/headers). A first contact gets a local echo of the request's header fields; a repeated call within the ticket lifetime gets the ASP terminal signal instead. Nothing is forwarded. The node records pseudonymised telemetry (salted network hash, User-Agent and header names) when a signal follows a discovery request from the same network; see https://agent-shelter.org/privacy.

Asks the reader of the ASP reference node what it does with a target URL (GET https://reader.agent-shelter.org/v1/reader?url=<target_url>&envelope=200). The reader never fetches the target: it answers with the ASP terminal signal (RFC 9457 problem details, terminal true, success_probability 0) and a single-use ticket (48 characters, also in the header Agent-Ticket and in an absolute resolution_uri), carried with HTTP 200 because of envelope=200; the ticket maps to a signed receipt by POST or, where resolution_methods lists GET, by GET, and only that receipt is a proof. Its drop box takes one optional context report, by POST or, where listed, by GET with query parameters. The target URL is sent to agent-shelter.org, which records it (shortened, secrets scrubbed) with pseudonymised client data when the request follows a discovery request from the same network or the ticket is redeemed; see https://agent-shelter.org/privacy.

Fetches an http(s) URL with GET (public hosts only, at most 5 redirects, each hop checked, at most 256 KiB). An answer without an ASP signal is returned as data, its text cut at 20 000 characters. An ASP terminal-state signal (HTTP 429, or HTTP 200 with transport_envelope, header Agent-Ticket) states that the resource cannot be obtained through that host; the tool then redeems the single-use ticket at the origin that sent the signal (POST, out of band), reads that host's manifest (/.well-known/agent-shelter.json, a discovery request) and verifies the Ed25519 receipt against the public key published there. From then on, for the lifetime of this server process, every call for the same resource - the requested URL, each redirect hop and the URL the signal names - is answered from that receipt without a request. The redemption is recorded by the node like any receipt (on the reference node pseudonymised, see https://agent-shelter.org/privacy); the receipt documents a terminal state on that host, never that the original task was done.