Global Payments

Last scanned developer.globalpayments.comCustom platform15 pages tested

AI agents can find, read and use these docs well. Global Payments scores 93 out of 100 (grade A), passing 19 of 25 checks. 6 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

19/25

Checks passed

0

Partly passed

6

Failed

Access

Content discoverability7 passed
  • llms.txt exists

    llms.txt found at https://developer.globalpayments.com/llms.txt

  • llms.txt follows the standard structure

    llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)

  • llms.txt fits in an agent's context

    llms.txt is 24,547 characters (under 50,000 threshold)

  • llms.txt links work

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

  • llms.txt links point to Markdown

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

  • Pages point agents to llms.txt

    llms.txt directive found in HTML of all 15 sampled pages, near the top of content

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of all 15 sampled pages, near the top of content

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://developer.globalpayments.com/api/access-token returns content-type: text/markdown.

  • Pages are available as Markdown

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

Page size and truncation3 passed1 failed
  • Markdown pages fit in context

    1 of 15 pages exceed 100K chars (max 401K)

    1 of 15 markdown pages exceed 100K characters and will be truncated by agents. Break these into smaller pages or restructure serialized tabbed content.

  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 864K HTML โ†’ 8K markdown (99% boilerplate))

  • Content starts near the top

    Content starts within first 10% on all 15 sampled pages (median 0%)

Content structure2 passed1 failed
  • Code blocks are well-formed

    2 unclosed code fences found across 16 pages

    2 pages have unclosed code fences. Everything after an unclosed fence is interpreted as code, causing agents to misread documentation as literal content. Ensure every opening ``` or ~~~ has a matching closing delimiter.

  • 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

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 health1 passed1 failed
  • Cache headers allow timely updates

    1 of 16 endpoints have aggressive caching or missing cache headers

    1 endpoints have aggressive caching (>24h) or missing cache headers. Set max-age under 3600 or add must-revalidate with ETag/Last-Modified so content updates reach agents promptly.

  • llms.txt covers the whole site

    No sitemap found; cannot assess llms.txt coverage without a sitemap as ground truth

  • Markdown matches the HTML page

    All 15 pages have equivalent markdown and HTML content (avg 0% missing)

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 access1 passed1 failed
  • Sitemap lists the docs pages

    The sitemap at https://developer.globalpayments.com/sitemap.xml lists 0 of the 168 docs pages found through llms.txt and page links.

    Generate the sitemap from the same source as the docs, so every page is listed. Agents and crawlers use it to find pages that navigation does not link.

    Check your fix: curl -s https://developer.globalpayments.com/robots.txt | grep -i sitemap names a sitemap, and that sitemap lists the pages the report names as missing.

  • Crawlers and AI assistants may read the docs

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

Freshness

Maintenance1 passed1 failed
  • Pages say when they were last changed

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

    Publish a last-modified date on every page: as article:modified_time or dateModified in the page, a visible "Last updated" line, or a Last-Modified header. Agents can then tell how current a page is; the date itself is not judged.

    Check your fix: curl -sI https://developer.globalpayments.com/api/access-token | grep -i last-modified returns a date, or the page carries article:modified_time or a visible "Last updated" line.

  • Sitemap entries still exist

    No sitemap entries for these docs to check.

  • Links and section anchors work

    All 33 links checked on the sampled pages work. 5 more could not be verified (timeouts or blocked requests) and are not counted.

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

Not part of the score: optional extras that help agents use your docs.

  • 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://developer.globalpayments.com/llms-full.txt (7,678,620 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 24, 2026
Pages tested
15 of 167 found
Platform
Unknown
Kind of site
Developer docs
AFDocs score, on its own
96 (A), 17 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://developer.globalpayments.com/api/access-token
  • https://developer.globalpayments.com/api/definitions/overview
  • https://developer.globalpayments.com/api/merchants
  • https://developer.globalpayments.com/docs/3DS-validation
  • https://developer.globalpayments.com/docs/getting-started/overview
  • https://developer.globalpayments.com/docs/integration-options/plugins/prestashop
  • https://developer.globalpayments.com/docs/integration-options/sdk/sdk-reference/configuration-code
  • https://developer.globalpayments.com/docs/operations/disputes-management-guide
  • https://developer.globalpayments.com/docs/payments/manage-payments/capture-guide
  • https://developer.globalpayments.com/docs/payments/online/hosted-fields-overview
  • https://developer.globalpayments.com/docs/payments/payment-methods/bank-payment/cz-overview
  • https://developer.globalpayments.com/docs/payments/payment-methods/dynamic-currency-conversion-guide
  • https://developer.globalpayments.com/docs/payments/payment-methods/qr-codes-overview
  • https://developer.globalpayments.com/docs/reporting/overview
  • https://developer.globalpayments.com/docs/risk-management/fraud-management/address-verification-service

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: 93 (A)](https://documentation.ai/agent-score/badge/globalpayments.svg)](https://documentation.ai/agent-score/globalpayments)

HTML

<a href="https://documentation.ai/agent-score/globalpayments"><img src="https://documentation.ai/agent-score/badge/globalpayments.svg" alt="Agent Readiness Score: 93 (A)" 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