AI agents read your site differently than people do, and most sites fail them. metaend Grade scans any URL and grades its agent readiness A to F: discovery files, content negotiation, A2A, ERC-8004, payments. Each fail comes with a fix. Free to scan.
No reviews yetBe the first to leave a review for metaend Grade ā Agent Readiness Checker
Maker
š
Hey Product Hunt š
For thirty years the web had one audience: people. That changed. AI agents (Claude, ChatGPT, Perplexity, and the autonomous ones that crawl, retrieve, and transact) now read the web too, and they read it completely differently. They do not look at your hero image. They look for machine-readable signals: llms.txt, content negotiation, structured data, an agent card, a way to pay. Most sites expose none of it, so the agent shrugs and moves on. You never even see the visit.
I kept hitting this while building agent tooling, so I built something to measure it.
metaend Grade scans any URL the way an agent would and hands back a grade from A to F across ~20 scored checks plus informational ones:
š Discovery files (llms.txt, robots, sitemap)
š Content negotiation (does your URL return JSON/Markdown when asked?)
š¤ A2A agent cards + ERC-8004 trustless-agent signals
šŖŖ Identity (DID, WebFinger, Nostr)
šø Machine-payment support
Every failed check comes with a plain-language fix. It is a to-do list, not a vanity score.
Two things I am proud of:
It dogfoods itself. The scanner serves its own llms.txt, agents.txt, agent card, security.txt, and JSON-LD, and content-negotiates its own root. If you grade the web on agent-readiness, the grader had better pass its own test.
It is built for agents to use, not just humans. GET /api/v1/scan?url=⦠returns a compact graded report as JSON. One agent can scan a site and act on the result in a single move.
Scanning is free up to a daily allowance. Beyond that, scans are paid over the open x402 standard: real EIP-3009 USDC payments settled on-chain on Base and Arbitrum, with replay protection and receipts. Humans can top up with the same rail to skip the per-site cooldown. No closed-vendor lock-in, by design.
Stack for the curious: Bun, Astro SSR with a React island, TypeScript strict with Zod, bun:sqlite, SSRF-hardened, on Fly.
Go scan your site and drop your grade in the comments. I will be here all day answering everything. Bonus points if you scan a site you think is "well built" and watch it get a D. š