Scanning live. A first-ever scan of a domain runs against the site and takes about ten seconds.
0.0s elapsedAgentSpeed tests how easily automated agents can discover, understand, and act on picpay.com. The score weights five categories of machine-readability; the ticks on the arc are the 37 individual checks behind it.
Send this to whoever edits the site. The link shows the score and grade as a preview card, and it stays current: it re-reads the latest scan rather than freezing today’s number.
No HTTP Link: response headers. Emit canonical/alternate/describedby relations so HEAD-only or stream-rendering agents get them without parsing HTML.
Show me exactly what to doHTTP responses can carry a Link header: the same canonical and alternate-language information your HTML declares, but delivered in the response envelope itself. Agents that only send a HEAD request, or that decide what to do while the page is still streaming, read the header without parsing any HTML. Yours is missing (or carries none of the relations agents use: canonical, alternate, describedby).
An agent triaging fifty URLs doesn’t want to download and parse fifty pages to learn which are duplicates of which. The Link header answers at the cheapest possible layer. Sites that provide it get correctly de-duplicated and correctly language-routed even by the most minimal fetchers.
Get it in your inbox now, plus a heads-up whenever picpay.com’s agent-readiness score changes. Free, unsubscribe anytime.
Prefer we just watch it for you? Monitor rescans weekly and emails what changed, $29/mo. Start monitoring →
Weakest on this scan: discoverability, 50/100 — the signals agents use to find and navigate this site are thin or missing.
This graded your homepage. Your pricing, docs, and checkout live on other pages: the ones assistants actually quote when they recommend you. A 74/100 here means agents are already missing things on the page you polish most. The $29 Deep Scan grades your homepage plus up to 10 more pages we discover, against all 37 checks, then emails a PDF with every failing check and its exact fix, ranked by what costs you the most visibility. One-time, delivered in minutes, no subscription.
Right now, only you know this score. Your buyers ask AI before they buy, and certification is how you show them, and anyone comparing you to a competitor, that assistants can actually read, quote, and use your site.
Sites under 70 can’t buy this at any price. That’s what makes displaying it mean something.
Embed this badge on your site. It links back to this live scan and updates on every rescan.
<a href="https://agentspeed.com/scan/picpay.com"><img src="https://agentspeed.com/badge/picpay.com" alt="AgentSpeed agent-readiness score" height="56"></a>Get this report by email, then a heads-up when picpay.com’s agent-readiness actually changes: a check regressing, or the composite dropping.
Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.
Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.
This score says whether an AI agent could read picpay.com. AI traffic analytics says whether one actually came, and which pages turned it away.
Running AI agents of your own? AgentSpeed also monitors them in production: every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.
Run reports like this for every client: white-label PDFs and weekly monitoring for up to 15 domains, $149/mo. AgentSpeed for Agencies →
This score is a measurement of machine-readability for automated agents under the published rubric 2026.11.0. AgentSpeed does not assess security, legitimacy, privacy, or financial trust.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
Consent modal detected (cookielaw.org); content still visible. Verify the modal does not block first-paint for screenshot agents.
Show me exactly what to doWe found a cookie-consent banner in your page’s HTML. On a fail, there is so little page text alongside it that the banner is likely most of what an agent receives; on a warn, your content is present but the banner may still block the first paint for agents that render.
Agents can’t click Accept. When the banner is all the page serves, summaries come out as "this site asks for cookie consent" while your actual pitch sits behind a click that never happens.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
No lang attribute on <html>. Agents cannot tell what language this document is in without guessing from the content. Declare it: <html lang="en">, <html lang="de-DE">.
Show me exactly what to doThe lang attribute on <html> declares what language the page is written in, and hreflang link tags list where your translations live. The finding above says which part is broken here: a missing or malformed lang declaration, or translation alternates written in a format machines reject (and therefore ignore).
Language routing happens early: assistants serving a German user prefer German sources, translators pick models per language, screen readers pick pronunciation. A missing declaration adds a guess at the base of all of it, and an ignored hreflang alternate makes that translation invisible to agents routing users by market.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
1 recommended-field warning(s). First: WebSite recommends "potentialAction" (improves agent comprehension).
Show me exactly what to doYour page HAS structured data, but it is malformed: broken JSON syntax, or types and fields that don’t exist in the schema.org vocabulary. Machines can see the block but can’t parse it.
Invalid JSON-LD is worse than it looks. The agent spends its attention budget on the block, fails to parse it, and falls back to guessing from prose anyway. You pay the cost of structured data without getting the benefit.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
Visible text is 14.1% of HTML weight (3931/27953 bytes). 7% of the document is inline script, 79% is markup.
Show me exactly what to doOf everything your server sends for this page, very little is actual readable text. The rest is code, styling, and markup wrapper. Agents fetched a lot of bytes and found few words.
Agents work with retrieval budgets. A page that is 2% text either gets skimmed (and mis-summarised) or skipped. More signal per byte means more of your actual message survives into the agent’s summary.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
Heading issues: no <h1>.
Show me exactly what to doHeadings (H1, H2, H3…) are the page’s outline. Yours skip levels, repeat H1s, or use styled text instead of real heading tags, so the outline machines extract is scrambled.
Agents use the heading tree to navigate long pages and to decide which section answers a question. A broken tree means quotes get attributed to the wrong section, or sections are missed entirely.
Paste into Claude Code, Cursor, or any assistant with your repository open. It carries this finding, the steps, and the shortcuts to avoid.
One prompt covering the fixes above that have a step-by-step plan, in the same priority order, with the same guardrails.
This scan shows whether an agent can read the site. One free probe asks a real assistant a real buying question and records who it cited.