Flowlu: is the website ready for AI agents

flowlu.com·checked November 11, 2026

58.2out of 100

Has issues

Agents read the site but miss some important things.

Paste the task into Claude Code, Cursor or another agent with access to the site’s code.

Agent access: 93
Discoverability: 75
Content for models: 14
AI bot rules: 50
API and protocols: 41

Fix these first

First, what gets in agents’ way the most.

01
The site serves Markdown when an agent asks
Failed
When the homepage is requested with “Accept: text/markdown”, return Markdown with “Content-Type: text/markdown” and “Vary: Accept”. Keep serving HTML for ordinary requests.
An agent can ask for a page in Markdown instead of HTML and spend far less of its budget on markup.
Markdown for agents →
›What the site returned
URL
https://www.flowlu.com/
Response code
200
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://www.flowlu.com/"
02
Pages have Markdown versions
Failed
Serve a Markdown version of pages at the URL ending in .md and reference it with <link rel="alternate" type="text/markdown"> on the page itself.
The same page at a URL ending in .md: clean text with no menus or scripts.
Markdown for agents →
›What the site returned
URL
https://www.flowlu.com/index.md
Response code
403
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://www.flowlu.com/index.md"
03
Open API docs or an MCP server exist
Partial
Open your API docs without a login and link to them from the homepage. The landing page must show methods, endpoints and a sample request in the HTML.
To work with the product and not just read the site, an agent needs a programmatic interface documented without a login.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/api/
Response code
200
Headers
content-type: text/html
vary: accept-encoding
Found
words of text: 5
API markers: 0
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/api/"
04
llms.txt exists
Failed
Put an llms.txt in Markdown at the site root: a top-level heading with the product name, a short description and a list of links to key pages. The links must resolve.
A short file for language models: what the product is and where the key pages are.
llms.txt →
›What the site returned
URL
https://www.flowlu.com/llms.txt
Response code
404
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://www.flowlu.com/llms.txt"
05
robots.txt has rules for AI bots
Failed
Add separate User-agent groups for AI bots to robots.txt: GPTBot, ClaudeBot, OAI-SearchBot, PerplexityBot, YandexAdditional. Naming two is enough.
AI bots are listed by name. Whether you allow or block them, it shows the choice was made.
robots.txt for AI →
›What the site returned
URL
https://www.flowlu.com/robots.txt
Response code
200
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/robots.txt"

Other issues19

06
Alice AI robots are allowed
Partial
Add a group to robots.txt with “User-agent: YandexAdditional” and “User-agent: YandexAdditionalBot” and an “Allow: /” rule.
The YandexAdditional robots bring a site into Alice AI answers. Best to allow them with a rule of their own.
robots.txt for AI →
›What the site returned
URL
https://www.flowlu.com/robots.txt
Response code
200
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/robots.txt"
07
Prices are visible without JavaScript
Partial
Link to the pricing page from the homepage and put the prices in that page’s HTML, not in a script that fills them in after load.
Agents are often asked to compare pricing. If a script fills in the prices, the agent never sees them.
Access without CAPTCHA or JS →
›What the site returned
URL
https://www.flowlu.com/pricing/
Response code
200
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/pricing/"
08
llms-full.txt exists
Failed
Put an llms-full.txt at the site root with the full text of the site or docs in Markdown.
The full text of the site or docs in one file. An agent reads it in a single request.
llms.txt →
›What the site returned
URL
https://www.flowlu.com/llms-full.txt
Response code
404
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://www.flowlu.com/llms-full.txt"
09
Content use is declared
Failed
Add a “Content-Signal: search=yes, ai-input=yes, ai-train=yes” line to robots.txt. Choose yes or no for each value yourself.
The Content-Signal line says whether your text may be used for search, AI answers and model training.
robots.txt for AI →
›What the site returned
URL
https://www.flowlu.com/robots.txt
Response code
200
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/robots.txt"
10
An MCP server exists
Partial
Publish an MCP server and state its address in the docs, or put a server card at /.well-known/mcp/server-card.json.
MCP is a way to plug a product into Claude, ChatGPT and other assistants as a set of ready-made tools.
API and MCP →
11
An agent can find how to sign in
Failed
Publish /.well-known/oauth-authorization-server (or /.well-known/openid-configuration) as JSON with an issuer field and the authorization endpoints.
A service file with OAuth endpoints. Without it an agent needs a person to explain where to get a token.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/.well-known/oauth-authorization-server
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/.well-known/oauth-authorization-server"
12
Company markup has a description and contacts
Failed
Add description, logo and contactPoint (address, email or telephone also work) to your Organization JSON-LD.
The description, logo and contacts in the markup let an assistant confirm this is a real company before recommending it.
sitemap and JSON-LD →
›What the site returned
URL
https://www.flowlu.com/
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
13
Pricing is available in Markdown
Failed
Serve the pricing page in Markdown: at the page URL ending in .md or at /pricing.md. The file must contain prices.
An agent comparing products reads pricing most easily from a plain text file.
Markdown for agents →
›What the site returned
URL
https://www.flowlu.com/pricing.md
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/pricing.md"
14
Company or product markup is present
Partial
Add JSON-LD markup of type Organization or SoftwareApplication with name and url to the homepage.
JSON-LD is company data in a machine format: name, site URL, product type.
sitemap and JSON-LD →
›What the site returned
URL
https://www.flowlu.com/
Found
JSON-LD types: AggregateRating, Offer, SoftwareApplication
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
15
The site points agents to its machine-readable files
Partial
Add a Link header or a <link> tag on the homepage pointing to llms.txt, the page’s Markdown version (rel="alternate" type="text/markdown") or the API description (rel="service-desc").
Links in the response header or page code lead to llms.txt, a Markdown version or an API description.
Markdown for agents →
›What the site returned
URL
https://www.flowlu.com/
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
16
The API reports errors in a machine format
Failed
Answer API requests without a token with 401 or 403 and a JSON body, not an HTML page.
A request without a token should return a JSON refusal, not an HTML page. Then the agent knows what went wrong.
API and MCP →
›What the site returned
URL
https://{your_company}.flowlu.com/api/v1/module/customfields/fieldsets/list
Response code
400
Headers
content-type: text/plain; charset=utf-8
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://{your_company}.flowlu.com/api/v1/module/customfields/fieldsets/list"
17
An API catalog exists
Failed
Publish /.well-known/api-catalog as application/linkset+json with links to your API descriptions (RFC 9727).
One file at a standard URL linking to all of the company’s APIs and their descriptions.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/.well-known/api-catalog
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/.well-known/api-catalog"
18
Agent skills are published
Failed
Publish /.well-known/agent-skills/index.json with a list of skills in the skills field.
Ready-made instructions for how an agent does common tasks in the product.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/.well-known/agent-skills/index.json
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/.well-known/agent-skills/index.json"
19
The API says which server grants access
Failed
Publish /.well-known/oauth-protected-resource as JSON with a resource field on the API domain (RFC 9728).
A service file: which authorization server issues tokens for this API.
API and MCP →
›What the site returned
URL
https://{your_company}.flowlu.com/.well-known/oauth-protected-resource
Response code
404
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://{your_company}.flowlu.com/.well-known/oauth-protected-resource"
20
Markup links to official profiles
Failed
Add a sameAs field to your JSON-LD with links to official profiles: GitHub, social networks, app stores.
sameAs links to GitHub, social networks and app stores. They tell an assistant that mentions elsewhere are about you.
sitemap and JSON-LD →
›What the site returned
URL
https://www.flowlu.com/
Found
sameAs links: 0
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
21
An agent-to-agent card exists
Failed
Publish /.well-known/agent-card.json in the A2A format: JSON with a name field, a description and the agent’s URL.
A file in the A2A standard: who you are, what you can do and how another agent reaches you.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/.well-known/agent-card.json
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/.well-known/agent-card.json"
22
There is a guide for how an agent gets access
Failed
Put an auth.md file at the site root with step-by-step instructions for how an agent gets a key or token.
An auth.md file walks an agent through getting a key or token without a person’s help.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/auth.md
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/auth.md"
23
A catalog of AI interfaces exists
Failed
Publish /.well-known/ai-catalog.json as JSON listing your MCP servers and other interfaces for agents.
One file at a standard URL listing the company’s MCP servers and other interfaces for agents.
API and MCP →
›What the site returned
URL
https://www.flowlu.com/.well-known/ai-catalog.json
Response code
403
Headers
content-type: text/html
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/.well-known/ai-catalog.json"
24
Content starts near the top of the page
Partial
Move the main content closer to the top of the HTML: the main heading should appear in the first quarter of the page text, before long menus.
If a long menu comes before the main text, the agent spends its budget on it and may never reach the point.
Access without CAPTCHA or JS →
›What the site returned
URL
https://www.flowlu.com/
Found
text before the heading, %: 30
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"

What already works17

Homepage opens without a CAPTCHA
›What the site returned
URL
https://www.flowlu.com/
Response code
200
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
Text is visible without JavaScript
›What the site returned
URL
https://www.flowlu.com/
Found
words of text: 2,548
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
A missing page returns 404
›What the site returned
URL
https://www.flowlu.com/agent-readiness-check-ddf5afda4f
Response code
404
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/agent-readiness-check-ddf5afda4f"
A short path from http to https
›What the site returned
URL
https://www.flowlu.com/
Response code
200
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Found
redirects: 2
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
The homepage is light and fast
›What the site returned
URL
https://www.flowlu.com/
Found
page size, KB: 323
response time, s: 1.021
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
robots.txt exists
›What the site returned
URL
https://www.flowlu.com/robots.txt
Response code
200
Headers
content-type: text/plain
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/robots.txt"
A sitemap exists
›What the site returned
URL
https://www.flowlu.com/sitemap.xml
Response code
200
Headers
content-type: text/xml
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/sitemap.xml"
Homepage metadata is filled in
›What the site returned
URL
https://www.flowlu.com/
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
The homepage links to API docs
›What the site returned
URL
https://www.flowlu.com/
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
A clear heading structure
›What the site returned
URL
https://www.flowlu.com/
Found
H1 headings: 1
H2 headings: 3
has <main>: yes
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
Agents and AI search are allowed
›What the site returned
URL
https://www.flowlu.com/robots.txt
Response code
200
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/robots.txt"
An API description (OpenAPI) is published
›What the site returned
URL
https://www.flowlu.com/api/json/openapien.json
Response code
200
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/api/json/openapien.json"
The homepage is not hidden from search
›What the site returned
URL
https://www.flowlu.com/
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
Homepage text fits an agent’s memory
›What the site returned
URL
https://www.flowlu.com/
Found
tokens, approx.: 5,680
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
ChatGPT and Claude get the same page people do
›What the site returned
URL
https://www.flowlu.com/
Response code
200
Headers
content-type: text/html; charset=utf-8
vary: accept-encoding
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
Page preview data is filled in
›What the site returned
URL
https://www.flowlu.com/
Found
found: og:title, og:description, og:image, og:type
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"
About, contact and policy pages are linked from the homepage
›What the site returned
URL
https://www.flowlu.com/
Found
found: about, contacts, privacy
Repeat the check yourself
curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://www.flowlu.com/"

Not scored5

These checks do not apply to the site and do not lower the score.

llms.txt is structured well enough to navigate
The Markdown version has a header with page data
The MCP server answers a connection
MCP tools have descriptions
An access refusal says where to sign in

Check your own site

Paste the address and get the same breakdown in half a minute.

Check a site →

Flowlu: is the website ready for AI agents

Fix these first

The site serves Markdown when an agent asks

Pages have Markdown versions

Open API docs or an MCP server exist

llms.txt exists

robots.txt has rules for AI bots

Alice AI robots are allowed

Prices are visible without JavaScript

llms-full.txt exists

Content use is declared

An MCP server exists

An agent can find how to sign in

Company markup has a description and contacts

Pricing is available in Markdown

Company or product markup is present

The site points agents to its machine-readable files

The API reports errors in a machine format

An API catalog exists

Agent skills are published

The API says which server grants access

Markup links to official profiles

An agent-to-agent card exists

There is a guide for how an agent gets access

A catalog of AI interfaces exists

Content starts near the top of the page

Homepage opens without a CAPTCHA

Text is visible without JavaScript

A missing page returns 404

A short path from http to https

The homepage is light and fast

robots.txt exists

A sitemap exists

Homepage metadata is filled in

The homepage links to API docs

A clear heading structure

Agents and AI search are allowed

An API description (OpenAPI) is published

The homepage is not hidden from search

Homepage text fits an agent’s memory

ChatGPT and Claude get the same page people do

Page preview data is filled in

About, contact and policy pages are linked from the homepage

Check your own site

Other checked sites