fledgify proof v0 An outside-in check, run from a stranger's vantage on nothing but a public URL, that a stranger can actually pay for an offer. It never buys, never enters a card, never submits a form, and never writes to anyone's system. A proof attests to what was observed, at a time, from a vantage. It never attests to the seller's honesty. GET /v0/proof?url=https://example.com/offer the report as JSON GET /v0/proof.txt?url=https://example.com/offer the same report as text GET /p/.json a stored proof, exactly as observed POST /mcp MCP, one tool named proof GET /openapi.json /v0/schema.json /llms.txt the contracts Verdicts are PROVEN, NOT_PROVEN and NOT_CHECKED. NOT_CHECKED always names what blocked the check and is never a pass. Every HTTP answer that carries a proof (/v0/proof, /v0/proof.txt, /p/, and the redirect from /prove) has the verdict in the x-fledgify-verdict header. A proof that could be stored also carries its permanent record in x-fledgify-record and in report.record; when it could not be stored the report says so in its notes and has no record and no permanent link, so branch on the field rather than assuming it. Over MCP the same facts are in the structured content. The url parameter must parse, must be http or https, must carry no credentials, must name the default port, and must be a public host name that is not private or loopback. Anything else answers 400 with the reason. A proof asks the site for its offer page twice (once as an anonymous visitor, once as a declared prover), its robots.txt, up to 3 policy pages, up to 3 same site scripts and up to 2 checkout candidates, and asks its DNS, its registry and a public resolver for the rest. Redirects count. The whole run is capped at 40 HTTP requests and 20 seconds, and it stops early when the page or the host does not answer. So this endpoint is limited to protect the sites it is pointed at: 10 proof requests a minute per caller, 6 a minute per site, and 30 a minute for the whole service, each counted exactly across every Cloudflare location. At most 3 of a site's 6 go to any one caller, so no caller can hold a site's minute, and every request past the door counts as one of the caller's 10, including one served from cache and one a site limit refuses. Over a caller or site limit answers 429, over the service limit answers 503, both with a retry-after header. A recent report for the same URL is served from cache (header x-fledgify-cache: HIT); the report's own startedAt and finishedAt say when it was actually observed.