Independent technical audit

docs.fractalpay.com

Overall AI readiness score

A combined result across all audit signals.

Excellent

AI readiness audit: 9/28/2026Public technical data

Overall AI readiness assessment

How ready docs.fractalpay.com is for AI systems

95/100

API Documentation (docs.fractalpay.com) received an AI-readiness score of 95/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was accessible, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 1 declared sitemap. Homepage markup completeness was 100%; Schema.org types included WebSite, Organization, WebPage, BreadcrumbList, Article and 8 OpenGraph tags were detected. Results reflect the public site response observed on 2026-09-28T04:19:44.734Z.

Audit context

llms.txt is accessible and contains 938 tokens. An expanded llms-full.txt is also available with 13,626 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. The homepage exposes Schema.org types WebSite, Organization, WebPage, BreadcrumbList, Article and others; 8 OpenGraph tags were found and markup completeness is 100%.

The mobile Lighthouse profile adds Performance 66/100, Accessibility 96/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt
Expanded llms-full.txt
1 sitemap declaration
Schema.org: WebSite, Organization
Complete social metadata
Strong Google agentic signals

Priority improvements

1Reduce mobile rendering delay and main-thread work.

llms.txt tokens938

llms-full.txt tokens13,626

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

100

Best Practices

100

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 66/100, with the largest visible content block appearing in 9.4 s and the browser main thread blocked for 90 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 96/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP2.6 s

First content

LCP9.4 s

Main content

CLS0

Layout stability

TBT90 ms

Blocking time

SI6.0 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

9/28/2026Lighthouse 13.5.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://docs.fractalpay.com/llms.txt

llms-full.txt

Full version is available

https://docs.fractalpay.com/llms-full.txt

ai.txt

ai.txt file was not found

robots.txt

File found

https://docs.fractalpay.com/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Types: WebSite, Organization, WebPage, BreadcrumbList, Article, TechArticle

OpenGraph100%

8 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned

OAI-SearchBotNot mentioned

ChatGPT-UserNot mentioned

Google-ExtendedNot mentioned

ClaudeBotNot mentioned

Claude-SearchBotNot mentioned

Claude-UserNot mentioned

BytespiderNot mentioned

CCBotNot mentioned

PerplexityBotNot mentioned

Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

https://docs.fractalpay.com/sitemap.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 100%

og:titleIntroduction - API Documentation

og:descriptionWelcome to the Fractal documentation

og:urlhttps://docs.fractalpay.com/introduction

og:site_nameAPI Documentation

og:imagehttps://fractal.mintlify.app/mintlify-assets/_next/image?url=%2F_mintlify%2Fapi%2Fog%3Fdivision%3DAPI%2BDocumentation%26title%3DIntroduction%26description%3DWelcome%2Bto%2Bthe%2BFractal%2Bdocumentation%26theme%3D56ac6db275232e827184fd32&w=1200&q=100

og:image:width1200

og:image:height630

og:typewebsite

Schema.org markup

Structured entities and properties exposed on the homepage.

Types found: 6 · Properties: 7

WebSiteOrganizationWebPageBreadcrumbListArticleTechArticle

nameAPI Documentation

urlhttps://docs.fractalpay.com

logohttps://mintcdn.com/fractal/aexZaynHTrRxjUql/logo/light.svg?fit=max&auto=format&n=aexZaynHTrRxjUql&q=85&s=6538bccda487e0afd4bdad2221825a51

publisher{"@id":"https://docs.fractalpay.com/#organization"}

descriptionWelcome to the Fractal documentation

dateModified2026-01-07T01:42:46.110Z

headlineIntroduction

# API Documentation

## Docs

- [Introduction](https://docs.fractalpay.com/introduction.md): Welcome to the Fractal documentation
- [Implementation Guide](https://docs.fractalpay.com/implementationguide.md): Integrations simplified
- [Webhooks](https://docs.fractalpay.com/Webhooks.md)
- [Low Code JS](https://docs.fractalpay.com/EmbeddedPayments.md): Fractal JS in depth
- [GooglePay™ Web Integration](https://docs.fractalpay.com/googlepay.md)
- [Full Merchant Submit](https://docs.fractalpay.com/api-reference/merchant-onboarding/full-merchant-submit.md): Full Merchant Submit
- [Get Merchants by Client](https://docs.fractalpay.com/api-reference/merchant-onboarding/get-merchants-by-client.md): Get Merchants by Client
- [Hosted Onboarding](https://docs.fractalpay.com/api-reference/merchant-onboarding/hosted-onboarding.md): SAML authentication and hosted merchant onboarding flow
- [Payment Request](https://docs.fractalpay.com/api-reference/payment-collection-methods/payment-request.md): Payment Request
- [Payment Request Customer](https://docs.fractalpay.com/api-reference/payment-collection-methods/payment-request-customer.md): Payment Request Customer
- [Create Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/create-payment-link.md): Create Link
- [Payment Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/qr-payment-link.md): Payment Link
- [Delete Pay Link](https://docs.fractalpay.com/api-reference/payment-collection-methods/delete-pay-link.md): Delete Pay Link
- [Remote Deposit Capture](https://docs.fractalpay.com/api-reference/payment-collection-methods/remote-deposit-capture.md): Submit a check image for remote deposit capture. Sends the front and back images of a check as a multipart/form-data upload.
- [Update Pre-Authorization](https://docs.fractalpay.com/api-reference/preauthorizations/increment-pre-authorization.md): Increases or decreases the authorized amount on an existing preauthorization. If new_authorized_amount is greater than last_authorized_amount, an incremental authorization is issued and a preauth.increment webhook fires. If new_authorized_amount is less, a partial reversal is issued and a preauth.de…
- [Capture Pre-Authorization](https://docs.fractalpay.com/api-reference/preauthorizations/capture-pre-authorization.md): Charges the customer for the currently authorized amount on an existing preauthorization. Converts the preauth into a completed transaction. Fires a preauth.charge webhook on success.
- [Charge Customer](https://docs.fractalpay.com/api-reference/customers/charge-customer.md): Charge Customer
- [Create Customer](https://docs.fractalpay.com/api-reference/customers/create-customer.md): Create Customer
- [Get Customer](https://docs.fractalpay.com/api-reference/customers/get-customer.md): Get Customer
- [Get Customers](https://docs.fractalpay.com/api-reference/customers/get-customers.md): Get Customers
- [Request Card](https://docs.fractalpay.com/api-reference/customers/request-card.md): Request Card
- [Get Transactions](https://docs.fractalpay.com/api-reference/transactions/get-transactions.md): Get Transactions
- [Get Transaction](https://docs.fractalpay.com/api-reference/transactions/get-transaction.md): Get Transaction
- [Return Sale](https://docs.fractalpay.com/api-reference/transactions/return-sale.md): Return Sale
- [Void Sale](https://docs.fractalpay.com/api-reference/transactions/void-sale.md): Void Sale

## OpenAPI Specs

- [openapi](https://docs.fractalpay.com/api-reference/openapi.json)
- [openapiOLD](https://docs.fractalpay.com/api-reference/openapiOLD.json)
- [openapiTEST](https://docs.fractalpay.com/api-reference/openapiTEST.json)

## Optional

- [Embedded Payments](https://fractalpay.com/)

Share or continue the analysis

Share this audit

Discuss with AI

Added 9/28/2026