increase.com

AI agents can discover the site but lack an OpenAPI spec and broken llms.txt links, making programmatic integration difficult.

23 pass · 3 warn · 2 fail · 14 n/a

Watch a real agent use your site →

A live Claude Code run against increase.com, streamed step by step.

Test this with real agents →

An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.

Discovery

22.2/22.2

Accessibility

30.8/33.3

Usability

19.9/44.4

Payments

n/a

Discovery 22.2/22.2

API reference linked from the homepagedetailsPASS
3 API link(s), e.g. /documentation/api/overview
Canonical URL declareddetailsPASS
https://increase.com/
Documentation linked from the homepagedetailsPASS
5 docs link(s), e.g. /documentation
Homepage has a meta descriptiondetailsPASS
98 characters
Homepage has a descriptive titledetailsPASS
'Increase — Banking for ambitious technology companies' (53 chars)
Open Graph tags presentdetailsPASS
og:title and og:description present
robots.txt allows agent crawlersdetailsPASS
all 6 agent crawlers may fetch /
robots.txt existsdetailsPASS
HTTP 200, 150 bytes
robots.txt points at the sitemapdetailsPASS
robots.txt has a Sitemap: line
sitemap.xml exists and parsesdetailsPASS
1 URL(s) listed
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed

Accessibility 30.8/33.3

Links in llms.txt resolvedetailsFAIL
1 of 5 sampled links broken: https://increase.com/updates.md → 404
Fix: Fix the dead links in /llms.txt. Pointing an agent at a 404 is worse than not pointing it anywhere.
Docs are readable without JavaScriptdetailsPASS
2612 characters of text at /docs
Homepage responds to an agent requestdetailsPASS
HTTP 200 for / (agent UA)
Served over HTTPSdetailsPASS
https://increase.com/
Structured data (JSON-LD) on the homepagedetailsPASS
1 valid block(s)
llms-full.txt is publisheddetailsPASS
HTTP 200, 473095 bytes
llms.txt is publisheddetailsPASS
HTTP 200, 4263 bytes
llms.txt is structured markdowndetailsPASS
has headings and markdown links
Serves markdown when asked for itdetailsPASS
Accept: text/markdown → text/markdown; charset=utf-8
Same response for agents and browsersdetailsPASS
both User-Agents got HTTP 200
Homepage has readable text without JavaScriptdetailsPASS
8300 characters of text in the served HTML
Content-to-markup ratio is reasonabledetailsPASS
ratio 0.0592 (8300 chars of 140262)
No long redirect chain on the homepagedetailsPASS
0 redirect(s)

Usability 19.9/44.4

OpenAPI document publisheddetailsFAIL
/openapi.json is served but is not valid JSON
Fix: Serve a parseable OpenAPI document at /openapi.json. What is there now cannot be read by any tooling.
agents.md is publisheddetailsWARN
/agents.md not served (HTTP 404)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
Errors are machine-readabledetailsWARN
404 returns HTML, not a machine-readable body
Fix: Content-negotiate your errors: return a JSON body with a stable `code` (and a `next_action` where recovery exists) to clients that ask for JSON.
.well-known/mcp.json advertises an MCP serverdetailsWARN
/.well-known/mcp.json not served (HTTP 404)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
A documentation endpoint respondsdetailsPASS
/docs → HTTP 200
The /api root behaves predictablydetailsN/A
/api → HTTP 404 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document

Payments not applicable — excluded from the score

Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.

Badge

Shows the current scan score and grade for this domain, straight from the latest static pre-check.

[![agent ready](/api/badge/increase.com)](/score/increase.com)

<a href="/score/increase.com"><img src="/api/badge/increase.com" alt="agent readiness score" /></a>