Crossriver

Last scanned docs.crossriver.comCustom platform15 pages tested

AI agents can use most of these docs. A few fixes would make them reliable. Crossriver scores 80 out of 100 (grade B), passing 18 of 27 checks. 9 still need work.

Fix it with Documentation.AI

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

18/27

Checks passed

3

Partly passed

6

Failed

Access

Content discoverability3 passed3 failed1 partly
  • llms.txt fits in an agent's context

    llms.txt is 115,685 characters (exceeds 100,000 threshold; will be truncated by most agents)

    Your llms.txt is 115,685 characters and will be truncated by all major agent platforms. Split into a root index linking to section-level llms.txt files, each under 50,000 characters.

    Check your fix: curl -s https://docs.crossriver.com/llms.txt | wc -c prints less than 50000.

  • Pages point agents to llms.txt

    No llms.txt directive found in HTML of any of 15 sampled pages

    No agent-facing directive pointing to llms.txt was detected in the HTML of any tested page. Add a visually-hidden element near the top of each page (e.g., a div with CSS clip-rect) containing a link to your llms.txt. If your site serves markdown versions of pages, mention that in the directive too so agents know to request it.

    Check your fix: curl -s https://docs.crossriver.com/ | grep -n llms.txt finds the link near the top of the HTML.

  • Markdown pages point agents to llms.txt

    No llms.txt directive found in markdown of any of 15 sampled pages

    No llms.txt directive was detected in the markdown of any tested page. Add a blockquote near the top of each markdown page (e.g., "> For the complete documentation index, see [llms.txt](/llms.txt)").

    Check your fix: The Markdown version of https://docs.crossriver.com/ (its .md URL, or the page fetched with Accept: text/markdown) has the llms.txt line in its first few lines.

  • llms.txt follows the standard structure

    llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.crossriver.com/llms.txt: No blockquote summary found

    Your llms.txt contains parseable links but doesn't follow the standard structure. Add an H1 title as the first line and a blockquote summary (lines starting with >) to improve agent parsing.

    Check your fix: llms.txt starts with a # Title, then a > summary line, then ## sections of links.

  • llms.txt exists

    llms.txt found at 2 locations; using https://docs.crossriver.com/llms.txt as canonical

  • llms.txt links work

    All 15 same-origin sampled links resolve (505 total links)

  • llms.txt links point to Markdown

    15/15 same-origin sampled links point to markdown content (100%)

Markdown availability1 passed1 failed
  • Server returns Markdown when asked

    Server ignores Accept: text/markdown header (0/15 sampled pages return markdown)

    Your server ignores Accept: text/markdown and returns HTML. Some agents (Claude Code, Cursor, OpenCode) request markdown this way. Configure your server to honor content negotiation.

    Check your fix: curl -sI -H "Accept: text/markdown" https://docs.crossriver.com/ returns content-type: text/markdown.

  • Pages are available as Markdown

    15/15 sampled pages support .md URLs (100%)

Page size and truncation1 passed1 failed2 partly
  • Content starts near the top

    2 of 15 sampled pages have content starting past 50% (worst 97%)

    2 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.

  • Content is in the HTML without JavaScript

    2 of 15 sampled pages have server-rendered page structure but little substantive content; agents will see headings and navigation but not the page's actual documentation

    2 of 15 pages have sparse content that may rely on client-side JavaScript to populate. Verify that key content is present in the server-rendered HTML response.

    Check your fix: curl -s https://docs.crossriver.com/ contains the article text itself, not only navigation, without running JavaScript.

  • Markdown pages fit in context

    1 of 15 pages between 50K–100K chars (max 51K)

    1 of 15 markdown pages are between 50K and 100K characters. These may be truncated on some agent platforms or routed through summarization. Consider splitting large pages.

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 282K HTML → 4K markdown (98% boilerplate))

Content structure3 passed
  • Tabs don't bloat the page

    No tabbed content detected across 15 sampled pages

  • Headings inside tabs name their variant

    No tabbed content found; header quality check not applicable

  • Code blocks are well-formed

    All 40 code fences properly closed across 17 pages

URL stability2 passed
  • Missing pages return a real 404

    All 15 sampled pages return proper error codes for bad URLs

  • Redirects stay on the same host

    No redirects detected across 15 sampled pages

Content health2 passed1 failed
  • Markdown matches the HTML page

    3 of 15 pages have substantive content differences between markdown and HTML (avg 12% missing)

    3 pages have substantive content differences between markdown and HTML (avg 12% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline.

  • llms.txt covers the whole site

    llms.txt covers 95% of 530 sitemap doc pages

  • Cache headers allow timely updates

    All 17 endpoints have appropriate cache headers

Authentication and access1 passed
  • Gated docs offer another way in

    All docs pages are publicly accessible; no alternative access paths needed

  • Docs are readable without logging in

    All 15 sampled pages are publicly accessible

Crawler access2 passed
  • Crawlers and AI assistants may read the docs

    robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.

  • Sitemap lists the docs pages

    The sitemap at https://docs.crossriver.com/sitemap.xml lists 505 of the 507 docs pages found through llms.txt and page links.

Freshness

Maintenance3 passed
  • Pages say when they were last changed

    15 of 15 sampled pages state when they were last changed.

  • Links and section anchors work

    All 32 links and 15 section anchors checked on the sampled pages work. 7 more could not be verified (timeouts or blocked requests) and are not counted.

  • Sitemap entries still exist

    All 10 sitemap entries sampled still exist.

Consistency with the API specNot applicable
  • Endpoints in the docs exist in the API spec

    No OpenAPI description was found, so the docs could not be compared with a spec.

CurrencyNot applicable
  • Deprecated operations are marked as such

    No OpenAPI description was found, so deprecation notices could not be compared with a spec.

Additional checks

  • MCP server is discoverable

    No MCP server was found for these docs.

    Offer a read-only MCP server with a search tool over your docs, and link it from llms.txt, so agents in Cursor, Claude and ChatGPT can query your docs directly.

  • llms-full.txt is available

    llms-full.txt found at https://docs.crossriver.com/llms-full.txt (5,815,023 characters).

  • Agent skills are published

    No agent skills index was found at /.well-known/agent-skills/index.json.

    Publish an Agent Skills index at /.well-known/agent-skills/index.json with a SKILL.md for your main tasks, so agents can load task instructions without reading every page.

About this scan

Scanned
Oct 7, 2026
Pages tested
15 of 505 found
Platform
Unknown
Kind of site
Developer docs
AFDocs score, on its own
77 (C), 13 of 23 checks pass
  • Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
  • Pages were fetched without running JavaScript, the way most AI agents read the web.
  • Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.

Methodology 2026-09.6 · AFDocs 0.20.0

Pages we sampled (15)
  • https://docs.crossriver.com/
  • https://docs.crossriver.com/apis/cards
  • https://docs.crossriver.com/apis/cards/webhook-events-cards
  • https://docs.crossriver.com/apis/lending/hook-notifications
  • https://docs.crossriver.com/apis/onchain-payments/apis/create-external-beneficiary
  • https://docs.crossriver.com/apis/payments/checks/get-extended-check-data
  • https://docs.crossriver.com/apis/payments/instant-payments/apis/simulations/simulated-inbound-remit-advice
  • https://docs.crossriver.com/apis/webhooks/cos-webhooks/event-formats-cos
  • https://docs.crossriver.com/concepts/cards/card-lifecycle/integrated-card-actions
  • https://docs.crossriver.com/concepts/cards/reporting-and-compliance/quarterly-report-templates
  • https://docs.crossriver.com/concepts/payments/checks/send-and-receive
  • https://docs.crossriver.com/concepts/payments/xml-batch-payments
  • https://docs.crossriver.com/ops-and-admin/cos-explorer/first-time-access
  • https://docs.crossriver.com/tutorials/api/accounts
  • https://docs.crossriver.com/tutorials/cos-explorer/ach/cancel-an-ach

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 80 (B)](https://documentation.ai/agent-score/badge/crossriver.svg)](https://documentation.ai/agent-score/crossriver)

HTML

<a href="https://documentation.ai/agent-score/crossriver"><img src="https://documentation.ai/agent-score/badge/crossriver.svg" alt="Agent Readiness Score: 80 (B)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.

Live in under 5 min · No credit card required