Яндекс.Метрика

Saby CRM (SBIS): is the website ready for AI agents

saby.ru·checked November 11, 2026
54.5out 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: 92
  • Discoverability: 73
  • Content for models: 8
  • AI bot rules: 50
  • API and protocols: 46

Fix these first

First, what gets in agents’ way the most.

  1. 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://saby.ru/
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://saby.ru/"
  2. 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://saby.ru/index.md
    Response code
    404

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://saby.ru/index.md"
  3. 03

    An API description (OpenAPI) is published

    Failed

    Publish an OpenAPI file (openapi.json or openapi.yaml) at a public URL and link to it from the docs.

    A file listing every API method in a machine format. An agent builds requests from it.

    API and MCP →
    ›What the site returned
    URL
    https://saby.ru/openapi.json
    Response code
    404

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/openapi.json"
  4. 04

    An MCP server exists

    Failed

    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 →
    ›What the site returned
    URL
    https://saby.ru/.well-known/mcp/server-card.json
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/.well-known/mcp/server-card.json"
  5. 05

    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://saby.ru/llms.txt
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://saby.ru/llms.txt"
Other issues13
  1. 06

    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://saby.ru/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://saby.ru/robots.txt"
  2. 07

    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://saby.ru/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://saby.ru/robots.txt"
  3. 08

    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://saby.ru/tariffs
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/tariffs"
  4. 09

    The site points agents to its machine-readable files

    Failed

    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://saby.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"
  5. 10

    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://saby.ru/llms-full.txt
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin
    Found
    page size, KB: 258

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://saby.ru/llms-full.txt"
  6. 11

    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://saby.ru/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://saby.ru/robots.txt"
  7. 12

    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://saby.ru/.well-known/oauth-authorization-server
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/.well-known/oauth-authorization-server"
  8. 13

    A clear heading structure

    Partial

    Keep a single h1 on the homepage, add h2 headings, do not skip levels (h3 follows h2, not h4) and wrap the main content in a <main> tag.

    One main heading, subheadings in order and a marked main area. An agent uses them to split the page into parts.

    Access without CAPTCHA or JS →
    ›What the site returned
    URL
    https://saby.ru/
    Found
    H1 headings: 1
    H2 headings: 0
    has <main>: no

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"
  9. 14

    Homepage metadata is filled in

    Partial

    Add title, meta description and link rel="canonical" to the homepage <head>, and a lang attribute to the html tag.

    Title, description, canonical URL and language. They tell an agent what the site is.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://saby.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"
  10. 15

    The homepage links to API docs

    Partial

    Link to your API docs from the homepage, for example in the footer or a developers menu.

    When asked to set up an integration, an agent looks for docs starting from the homepage.

    sitemap and JSON-LD →
    ›What the site returned
    URL
    https://saby.ru/

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"
  11. 16

    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://saby.ru/.well-known/api-catalog
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/.well-known/api-catalog"
  12. 17

    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://saby.ru/.well-known/agent-skills/index.json
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/.well-known/agent-skills/index.json"
  13. 18

    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://saby.ru/.well-known/oauth-protected-resource
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/.well-known/oauth-protected-resource"
What already works10

  • Homepage opens without a CAPTCHA

    ›What the site returned
    URL
    https://saby.ru/
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"

  • Text is visible without JavaScript

    ›What the site returned
    URL
    https://saby.ru/
    Found
    words of text: 1,051

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"

  • A missing page returns 404

    ›What the site returned
    URL
    https://saby.ru/agent-readiness-check-c45a013d23
    Response code
    404
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/agent-readiness-check-c45a013d23"

  • A short path from http to https

    ›What the site returned
    URL
    https://saby.ru/
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin
    Found
    redirects: 1

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"

  • The homepage is light and fast

    ›What the site returned
    URL
    https://saby.ru/
    Found
    page size, KB: 609
    response time, s: 1.003

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"

  • robots.txt exists

    ›What the site returned
    URL
    https://saby.ru/robots.txt
    Response code
    200
    Headers
    content-type: text/plain; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/robots.txt"

  • A sitemap exists

    ›What the site returned
    URL
    https://saby.ru/sitemap.xml
    Response code
    200
    Headers
    content-type: text/xml; charset=utf-8
    vary: Accept-Encoding, Origin

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/sitemap.xml"

  • Company or product markup is present

    ›What the site returned
    URL
    https://saby.ru/
    Found
    JSON-LD types: ContactPoint, Organization, PostalAddress

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/"

  • Agents and AI search are allowed

    ›What the site returned
    URL
    https://saby.ru/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://saby.ru/robots.txt"

  • Open API docs or an MCP server exist

    ›What the site returned
    URL
    https://saby.ru/help/integration/api/all_methods
    Response code
    200
    Headers
    content-type: text/html; charset=utf-8
    vary: Accept-Encoding, Origin
    Found
    API markers: 10

    Repeat the check yourself

    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://saby.ru/help/integration/api/all_methods"
Not scored1

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

  • The API reports errors in a machine format

Check your own site

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

Check a site →

Other checked sites