LLPROBeta

Home / Agents / HTTP Cache Freshness Check

HTTP Cache Freshness Check

Work out whether a cached HTTP response is fresh or stale from its headers, per RFC 9111: freshness lifetime and its source, current age step by step, heuristic freshness flagged, and a signed record.

Testing

What it does
Work out whether a cached HTTP response is fresh or stale from its headers, per RFC 9111: freshness lifetime and its source, current age step by step, heuristic freshness flagged, and a signed record.
Who it is for
Agents and their builders.
Start in one step
Ask your agent to call http_cache_freshness at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

HTTP Cache Freshness Check is for agents and developers that tune CDN or browser caching, debug stale content, or decide whether a stored API response can be reused without asking the server again. Work out whether a cached HTTP response is still fresh, per RFC 9111 (HTTP Caching). Send the response header text (Cache-Control, Expires, Date, Age, Last-Modified, ETag; a status line is read if present) and optionally now, response_time and request_time, the status code and whether the cache is private (a browser) or shared (a CDN or proxy). Get back the freshness lifetime and where it came from (s-maxage, max-age, Expires or the heuristic, flagged), the current age worked step by step, fresh or stale with the seconds left or over, whether the response may be stored and reused without revalidation, and the validators available. Nothing is fetched. It is one of the developer department tools LLPRO builds for the work agents do across business software (Cloudflare, Fastly, Aws, Vercel, Nginx). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents and developers that tune CDN or browser caching, debug stale content, or decide whether a stored API response can be reused without asking the server again.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not fetch the URL or read the request (Authorization, request Cache-Control, Vary and the cache key are not considered; a shared cache must not reuse a response to a request with Authorization unless allowed, RFC 9111 3.5). Does not model a particular browser or CDN: their heuristics and limits differ (some cap the 10% heuristic, some ignore no-cache field names); this follows the RFC text. Qualified no-cache="..." and private="..." are reported, not applied field by field. Pragma is ignored for responses (RFC 9111 5.4). Works in whole seconds, as HTTP dates do.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "http_cache_freshness", "arguments": {"headers": "Date: Thu, 19 Nov 2026 10:00:00 GMT\r\nCache-Control: public, max-age=3600\r\nAge: 100", "now": "2026-11-19T10:30:00Z"}}}

For agents

Tool http_cache_freshness on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:5ojl4wbts457nppwz43mu3wwfy): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): wW2oQsP+GpU3YLvny20fmTGcxEcsXkyme8tY92g9Cis=

For agents that search MCP registries for HTTP caching, Cache-Control, RFC 9111 tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card