ARI-100 report · scanned 2026-11-11T23:16:11.400Z · 4855 ms · engine ARI-100

Agent readiness — squishy-finder.com

https://squishy-finder.com/us · 112 checks scored of 120 · 47 pass, 18 partial, 47 fail, 8 not applicable, 0 inconclusive

Domains

Crawler reachability

Each agent was fetched with its own user-agent string and matched against robots.txt with RFC 9309 longest-match rules. A verdict is one of allowed, blocked, challenged, rate limited or unverifiable.

Failing checks, most recoverable first

65 checks are not passing. The first 3 fix prompts are free; the rest are part of the paid pack. Every prompt is written to be pasted into a coding agent verbatim.

Server-render the homepage of https://squishy-finder.com: ship at least 500 characters of real text and an H1 in the initial HTML response rather than after hydration (SSR/SSG, or prerender). Evidence: 53 chars of text, 0 H1 in raw HTML.

Server-render the inner pages of https://squishy-finder.com (0/2 sampled inner pages carry 400+ chars without JS): move the primary copy into the HTML response for each template, not only the homepage.

Publish /openapi.json on https://squishy-finder.com (OpenAPI 3.1) describing every public endpoint, with operation summaries and example responses. Evidence: openapi.json HTTP 404.

Ensure exactly one non-empty H1 on https://squishy-finder.com/us that states the page subject; demote extra H1s to H2. Evidence: 0 H1: "".

Make the MCP endpoint advertised by https://squishy-finder.com actually answer: respond to initialize and tools/list at the URL in the card, and keep the card in sync with the deployed tool set. Evidence: MCP endpoint answered no endpoint in card.

Publish a commerce profile at /.well-known/ucp on https://squishy-finder.com declaring the merchant, the catalogue, and the endpoints an agent may call. Evidence: HTTP 404.

Replace the add-to-cart div on https://squishy-finder.com/us with a real <button type="submit"> inside a <form>, with an accessible name that includes the product. Evidence: no add-to-cart control.

Convert the variant pickers on https://squishy-finder.com/us to real form controls (select or radio inputs) with a label per option, so an agent can set a value. Evidence: no variant form controls.

Name the AI crawlers explicitly in robots.txt for https://squishy-finder.com instead of relying on a wildcard, so each one has a deliberate policy. Evidence: 0 named user-agent groups.

Raise the text-to-markup ratio on https://squishy-finder.com/us to at least 5%: trim wrapper divs and inline styles, and put the copy in plain elements. Evidence: text/markup 0.2%.

Publish /AGENTS.md on https://squishy-finder.com describing how a coding agent should build against or use the site: install, configuration, and worked examples. Evidence: AGENTS.md HTTP 404.

Add a Content-Signal line to robots.txt on https://squishy-finder.com, e.g. "Content-Signal: search=yes, ai-input=yes, ai-train=no", so usage terms are machine-readable. Evidence: no Content-Signal line.

Publish /.well-known/api-catalog on https://squishy-finder.com as an RFC 9727 linkset pointing at the API, its OpenAPI description and its docs. Evidence: no linkset.

Publish /.well-known/oauth-protected-resource on https://squishy-finder.com naming the resource and its authorization server, so an agent can discover how to get a token without scraping docs. Evidence: HTTP 404.

Publish /.well-known/oauth-authorization-server on https://squishy-finder.com with issuer, authorization_endpoint, token_endpoint and grant types. Evidence: HTTP 404.

Replace all-or-nothing credentials on https://squishy-finder.com with named scopes (for example read:catalog, write:cart) declared in the OpenAPI security scheme and the authorization-server metadata. Evidence: no named scopes.

Publish /auth.md on https://squishy-finder.com telling an agent how to register, get a credential and revoke it, with the exact request/response shapes. Evidence: auth.md HTTP 404.

Publish a /.well-known/agent-card.json on https://squishy-finder.com describing the agent: name, description, capabilities, skills and endpoint. Evidence: HTTP 404.

Simplify the API surface on https://squishy-finder.com for function calling: flat named parameters, enums instead of free-text where possible, and a description on every field in the OpenAPI spec. Evidence: 0 described properties in the schema.

Link the developer docs from the homepage and main navigation of https://squishy-finder.com — one hop, not three. Evidence: no developer link.

Add a when-to-use block to https://squishy-finder.com (in llms.txt, the MCP card or the agent manifest) stating what the agent is for, what it must not do, and one worked call. Evidence: no when-to-use block.

Add a shareable cart/checkout permalink on https://squishy-finder.com that carries line items in the URL, so an agent can build a cart and hand the link to a person. Evidence: no cart permalink.

Put product name, price, currency and availability in the server HTML of https://squishy-finder.com/us — not fetched client-side — with the variants listed. Evidence: no price in HTML.

Link returns, shipping, terms, privacy and contact from the footer of every page on https://squishy-finder.com. Evidence: 0/5 policy pages linked.

Add outbound links to primary sources for the factual claims on https://squishy-finder.com/us — the operator documentation, study or specification, not another summary. Evidence: 0 outbound source link(s).

Publish a reachable About and Contact page on https://squishy-finder.com and link both from the footer. Evidence: no about or contact link.

Speed up the server response for https://squishy-finder.com/us: TTFB should land under 800 ms. Cache the HTML at the edge, and remove synchronous calls from the render path. Evidence: 823 ms to first byte.

Add a self-referencing rel=canonical to https://squishy-finder.com/us that matches the URL actually served (https, final host, no tracking params). Evidence: canonical https://squishy.build/us.

Add an Organization (or Person) JSON-LD node on https://squishy-finder.com with name, url, logo, and sameAs links to the profiles the brand actually owns. Evidence: entity without sameAs.

Expose at least one unauthenticated read endpoint on https://squishy-finder.com that returns the site's core facts as JSON, and document it in the OpenAPI spec. Evidence: no API declared.

Make site search on https://squishy-finder.com work over GET with a ?q= parameter that returns results in the server HTML, so an agent can construct a search URL. Evidence: no GET search form.

Show a named author or accountable publisher on https://squishy-finder.com/us, with a link to an about page that establishes who they are. Evidence: no author signal.

State a training policy on https://squishy-finder.com: either name CCBot / Google-Extended / Bytespider explicitly in robots.txt, or add a Content-Signal line (search=yes, ai-input=yes, ai-train=no). Evidence: no explicit training policy.

On https://squishy-finder.com set "max-snippet:-1, max-image-preview:large" in the meta robots tag or X-Robots-Tag so assistants can quote the page. Evidence: snippet directives incomplete.

Fix the heading outline on https://squishy-finder.com/us: no skipped levels (H2 to H4), and make each H2 describe its section. Evidence: 0 skipped level(s), 0 H2(s).

Add Open Graph tags to https://squishy-finder.com/us: og:title, og:description, og:image (1200x630 absolute URL), og:url, og:type. Evidence: og:title yes, og:description yes, og:image no.

Add datePublished and dateModified to the schema on https://squishy-finder.com/us, kept in sync with the visible date. Evidence: no dates in schema.

Add a BreadcrumbList to https://squishy-finder.com/us whose items match the visible breadcrumb. Evidence: no BreadcrumbList.

Add truthful <lastmod> values to the sitemap on https://squishy-finder.com from real content timestamps. Evidence: no lastmod.

Add <link rel="alternate" type="text/markdown" href="/<path>.md"> to the head of https://squishy-finder.com/us. Evidence: no <link rel=alternate type=text/markdown>.

Publish /sitemap.md on https://squishy-finder.com: a Markdown list of the site's pages as [title](url), one line each, so an agent gets the whole map in one cheap request. Evidence: HTTP 404.

Publish a DNS discovery record for https://squishy-finder.com (a TXT record listing the agent endpoints the site exposes) so an agent learns the surface before fetching a page. Evidence: no _agents TXT record.

Deepen /AGENTS.md on https://squishy-finder.com to include install steps, configuration, and at least one complete usage example. Evidence: 0/3 of install, configuration, examples.

Add a rel="describedby" link to the covering /llms.txt from every page on https://squishy-finder.com so an agent can widen from one page to the index. Evidence: rel=describedby to the index.

Complete the MCP server card on https://squishy-finder.com: transport, endpoint URL, auth requirement, and every tool with a declared input schema and description. Evidence: 1/4 required groups in the card.

Publish /.well-known/agent-skills/index.json on https://squishy-finder.com listing each skill document with name, description and URL. Evidence: HTTP 404.

Register the site's real actions (search, filter, add to cart) as WebMCP tools on https://squishy-finder.com so a browser agent can call them without guessing at the DOM. Evidence: no WebMCP registration.

Publish an ARD manifest at /.well-known/ard.json on https://squishy-finder.com listing every agentic artefact with its type and URL, and advertise it with rel="ard". Evidence: HTTP 404.

Publish /.well-known/agents.json on https://squishy-finder.com: a JSON document naming each agent or action the site accepts, with the URL to call and the input it expects. Evidence: HTTP 404.

Publish /.well-known/agent-permissions.json on https://squishy-finder.com mapping each action an agent may take to the scope it needs and whether a human must confirm it. Evidence: HTTP 404.

Expose a natural-language query endpoint at https://squishy-finder.com/ask that accepts ?query= and returns JSON (answer plus result URLs), so an agent can ask the site directly instead of crawling it. Evidence: /ask → HTTP 404, text/html; charset=utf-8.

Declare an agent-driven UI surface on https://squishy-finder.com: mark the page (or publish a manifest) as A2UI so a reviewing agent knows the controls are renderable from a declared schema rather than inferred from the DOM. Evidence: no A2UI declaration.

Publish /.well-known/personal-agent.json on https://squishy-finder.com describing how an agent acting for a signed-in person is identified and what it may do on their behalf. Evidence: HTTP 404.

Publish a signing-key directory at https://squishy-finder.com/.well-known/http-message-signatures-directory so another site can verify requests this site's bots send. Evidence: HTTP 404.

Return RFC 9457 problem-details JSON for every error on https://squishy-finder.com, including unknown routes, so an agent can recover instead of parsing an HTML error page. Evidence: unknown API path returned text/html; charset=utf-8.

Emit RateLimit-Limit / RateLimit-Remaining / RateLimit-Reset (and Retry-After on 429) from the API on https://squishy-finder.com. Evidence: no rate-limit headers.

Accept an Idempotency-Key header on mutating endpoints of https://squishy-finder.com and document it, so an agent can retry without duplicating work. Evidence: Idempotency-Key documented.

Make paid access discoverable on https://squishy-finder.com: return HTTP 402 with a machine-readable list of accepted payment options, or publish a machine-readable price list. Evidence: x402 discovery HTTP 404.

Accept machine payment on https://squishy-finder.com: answer with HTTP 402 and an x402 accepts array (asset, amount, network, payTo) on the paid resource. Evidence: no x402 accepts array.

Advertise delegated payment authorization on https://squishy-finder.com (AP2 extension on the agent card or commerce profile) with the mandate shapes you accept. Evidence: AP2 advertised.

Publish a checkout-protocol profile at /.well-known/acp.json on https://squishy-finder.com naming the checkout endpoint and supported payment methods. Evidence: acp profile HTTP 404.

Document the checkout terms an agent must know on https://squishy-finder.com: shipping cost and regions, return window, tax handling, and lead time. Evidence: checkout terms incomplete.

Show a visible publish or last-updated date on https://squishy-finder.com/us that matches dateModified in the schema. Evidence: no visible date.

Complete the Organization schema on https://squishy-finder.com with legalName, address, contactPoint, logo and sameAs. Evidence: legalName missing.

Enable Brotli/gzip compression for HTML and JSON on https://squishy-finder.com. Evidence: no compression header relayed.

Take the report with you

• /report/squishy-finder.com.json — cached JSON, 6-hour TTL
• /report/squishy-finder.com.md — Markdown mirror, text/markdown
• /badge/squishy-finder.com.svg — score badge
• /api/scan?url=… — the same number as JSON

A snapshot is not a guarantee: one scan is one request per surface at one moment. Re-scan after every deploy.