# Aspro.Cloud: is the website ready for AI agents

> We checked the Aspro.Cloud website (aspro.cloud): can ChatGPT, Claude and Alice open it, does it have llms.txt, Markdown, an API and MCP. 25.9 out of 100. API: yes, MCP: no, llms.txt: no.

Источник: https://pachca.com/en/agent-ready/aspro-cloud

[aspro.cloud](https://aspro.cloud)·checked November 11, 2026

25.9out of 100

Critical

Agents struggle to read the site. Start with the first items on the list.

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

- Agent access:  39

- Discoverability:  18

- Content for models:  7

- AI bot rules:  50

- API and protocols:  20

### Fix these first

First, what gets in agents’ way the most.

1.  01

    #### Text is visible without JavaScript

    Failed

    Render homepage text on the server: SSR or a static build. The HTML must contain at least 300 words of visible text without running JavaScript.

    Most agents do not run JavaScript. Product text has to be in the page itself, not loaded by a script.

    [Access without CAPTCHA or JS →](https://pachca.com/en/agent-ready/guide/site-access)

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Found

    words of text: 28

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

2.  02

    #### 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 →](https://pachca.com/en/agent-ready/guide/markdown)

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Response code

    403

    Headers

    content-type: application/json

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://aspro.cloud/"
    ```

3.  03

    #### 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 →](https://pachca.com/en/agent-ready/guide/markdown)

    ›What the site returned

    URL

    [https://aspro.cloud/index.md](https://aspro.cloud/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://aspro.cloud/index.md"
    ```

4.  04

    #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

    ›What the site returned

    URL

    [https://aspro.cloud/api](https://aspro.cloud/api)

    Response code

    200

    Headers

    content-type: text/html; charset=utf-8

    vary: Accept-Encoding

    Found

    words of text: 28

    API markers: 0

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/api"
    ```

5.  05

    #### Homepage opens without a CAPTCHA

    Partial

    Allow non-browser requests in your bot protection (Qrator, DDoS-Guard, Cloudflare). The homepage must return 200 and the normal page, not a browser check or CAPTCHA.

    An agent is a program without a browser. If the site shows it a CAPTCHA or a “checking your browser” page, it reads nothing.

    [Access without CAPTCHA or JS →](https://pachca.com/en/agent-ready/guide/site-access)

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Response code

    200

    Headers

    content-type: text/html; charset=utf-8

    vary: Accept-Encoding

    Found

    CAPTCHA marker: Проверка браузера

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

Other issues26

1.  06

    #### Prices are visible without JavaScript

    Failed

    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 →](https://pachca.com/en/agent-ready/guide/site-access)

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

2.  07

    #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

    ›What the site returned

    URL

    [https://aspro.cloud/openapi.json](https://aspro.cloud/openapi.json)

    Response code

    403

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/openapi.json"
    ```

3.  08

    #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

    ›What the site returned

    URL

    [https://aspro.cloud/.well-known/mcp/server-card.json](https://aspro.cloud/.well-known/mcp/server-card.json)

    Response code

    403

    Headers

    content-type: application/json

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/mcp/server-card.json"
    ```

4.  09

    #### robots.txt exists

    Failed

    Put a robots.txt file at the site root, served as text/plain, with at least one User-agent group.

    It is the first file any robot reads: the rules for what it may open on the site.

    [robots.txt for AI →](https://pachca.com/en/agent-ready/guide/robots-txt)

    ›What the site returned

    URL

    [https://aspro.cloud/robots.txt](https://aspro.cloud/robots.txt)

    Response code

    403

    Headers

    content-type: application/json

    Repeat the check yourself

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

5.  10

    #### A sitemap exists

    Failed

    Generate a sitemap.xml listing your pages and reference it in robots.txt with a “Sitemap: https://your-site/sitemap.xml” line.

    sitemap.xml is the list of pages. An agent uses it to find sections it did not reach by links.

    [sitemap and JSON-LD →](https://pachca.com/en/agent-ready/guide/structured-data)

    ›What the site returned

    URL

    [https://aspro.cloud/sitemap.xml](https://aspro.cloud/sitemap.xml)

    Response code

    403

    Headers

    content-type: application/json

    Repeat the check yourself

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

6.  11

    #### Company or product markup is present

    Failed

    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 →](https://pachca.com/en/agent-ready/guide/structured-data)

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

7.  12

    #### 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 →](https://pachca.com/en/agent-ready/guide/llms-txt)

    ›What the site returned

    URL

    [https://aspro.cloud/llms.txt](https://aspro.cloud/llms.txt)

    Response code

    403

    Headers

    content-type: application/json

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://aspro.cloud/llms.txt"
    ```

8.  13

    #### 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 →](https://pachca.com/en/agent-ready/guide/robots-txt)

    ›What the site returned

    URL

    [https://aspro.cloud/robots.txt](https://aspro.cloud/robots.txt)

    Response code

    403

    Repeat the check yourself

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

9.  14

    #### 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 →](https://pachca.com/en/agent-ready/guide/robots-txt)

    ›What the site returned

    URL

    [https://aspro.cloud/robots.txt](https://aspro.cloud/robots.txt)

    Response code

    403

    Repeat the check yourself

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

10.  15

     #### A missing page returns 404

     Failed

     Configure the server so that a missing URL returns 404, not 200 and not a redirect to the homepage.

     If the site answers “OK” to any URL, the agent takes an empty page for a real one.

     [Access without CAPTCHA or JS →](https://pachca.com/en/agent-ready/guide/site-access)

     ›What the site returned

     URL

     [https://aspro.cloud/agent-readiness-check-a945d7b7dc](https://aspro.cloud/agent-readiness-check-a945d7b7dc)

     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://aspro.cloud/agent-readiness-check-a945d7b7dc"
     ```

11.  16

     #### The homepage links to API docs

     Failed

     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 →](https://pachca.com/en/agent-ready/guide/structured-data)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

12.  17

     #### 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 →](https://pachca.com/en/agent-ready/guide/markdown)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

13.  18

     #### 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 →](https://pachca.com/en/agent-ready/guide/llms-txt)

     ›What the site returned

     URL

     [https://aspro.cloud/llms-full.txt](https://aspro.cloud/llms-full.txt)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -H "Accept: text/markdown" -D - -o /dev/null "https://aspro.cloud/llms-full.txt"
     ```

14.  19

     #### 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 →](https://pachca.com/en/agent-ready/guide/robots-txt)

     ›What the site returned

     URL

     [https://aspro.cloud/robots.txt](https://aspro.cloud/robots.txt)

     Response code

     403

     Repeat the check yourself

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

15.  20

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/oauth-authorization-server](https://aspro.cloud/.well-known/oauth-authorization-server)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/oauth-authorization-server"
     ```

16.  21

     #### 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 →](https://pachca.com/en/agent-ready/guide/structured-data)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

17.  22

     #### About, contact and policy pages are linked from the homepage

     Failed

     Link to the About, Contact and privacy policy pages from the homepage, for example in the footer.

     An agent checks these pages to make sure the site can be trusted.

     [sitemap and JSON-LD →](https://pachca.com/en/agent-ready/guide/structured-data)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

18.  23

     #### 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 →](https://pachca.com/en/agent-ready/guide/markdown)

     ›What the site returned

     URL

     [https://aspro.cloud/pricing.md](https://aspro.cloud/pricing.md)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/pricing.md"
     ```

19.  24

     #### 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 →](https://pachca.com/en/agent-ready/guide/site-access)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Found

     H1 headings: 1

     H2 headings: 0

     has <main>: yes

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

20.  25

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/api-catalog](https://aspro.cloud/.well-known/api-catalog)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/api-catalog"
     ```

21.  26

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/agent-skills/index.json](https://aspro.cloud/.well-known/agent-skills/index.json)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/agent-skills/index.json"
     ```

22.  27

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/oauth-protected-resource](https://aspro.cloud/.well-known/oauth-protected-resource)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/oauth-protected-resource"
     ```

23.  28

     #### 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 →](https://pachca.com/en/agent-ready/guide/structured-data)

     ›What the site returned

     URL

     [https://aspro.cloud/](https://aspro.cloud/)

     Found

     sameAs links: 0

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
     ```

24.  29

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/agent-card.json](https://aspro.cloud/.well-known/agent-card.json)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/agent-card.json"
     ```

25.  30

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/auth.md](https://aspro.cloud/auth.md)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/auth.md"
     ```

26.  31

     #### 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 →](https://pachca.com/en/agent-ready/guide/api-mcp)

     ›What the site returned

     URL

     [https://aspro.cloud/.well-known/ai-catalog.json](https://aspro.cloud/.well-known/ai-catalog.json)

     Response code

     403

     Headers

     content-type: application/json

     Repeat the check yourself

     ```
     curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/.well-known/ai-catalog.json"
     ```

What already works6

- #### A short path from http to https

    ›What the site returned

    URL

    [https://aspro.cloud/?](https://aspro.cloud/?)

    Response code

    200

    Headers

    content-type: text/html; charset=utf-8

    vary: Accept-Encoding

    Found

    redirects: 1

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/?"
    ```

- #### The homepage is light and fast

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Found

    page size, KB: 14

    response time, s: 0.483

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

- #### Homepage metadata is filled in

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

- #### Agents and AI search are allowed

    ›What the site returned

    URL

    [https://aspro.cloud/robots.txt](https://aspro.cloud/robots.txt)

    Response code

    403

    Repeat the check yourself

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

- #### The homepage is not hidden from search

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    Repeat the check yourself

    ```
    curl -sSL -c /dev/null -A "agent-readiness-index/0.1" -D - -o /dev/null "https://aspro.cloud/"
    ```

- #### Page preview data is filled in

    ›What the site returned

    URL

    [https://aspro.cloud/](https://aspro.cloud/)

    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://aspro.cloud/"
    ```

Not scored9

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

- The API reports errors in a machine format
- Homepage text fits an agent’s memory
- Content starts near the top of the page
- ChatGPT and Claude get the same page people do
- 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 →](https://pachca.com/en/agent-ready)

## Other checked sites

- [Advanta](https://pachca.com/en/agent-ready/advanta)65.9
- [ELMA365 Projects](https://pachca.com/en/agent-ready/elma365)61.2
- [EvaTeam](https://pachca.com/en/agent-ready/evateam)62.8
- [Flowlu](https://pachca.com/en/agent-ready/flowlu)58.2
- [Kaiten](https://pachca.com/en/agent-ready/kaiten)61
- [LeaderTask](https://pachca.com/en/agent-ready/leadertask)68.7
- [Planfix](https://pachca.com/en/agent-ready/planfix)64.2
- [Platrum](https://pachca.com/en/agent-ready/platrum)74.1
- [Pyrus](https://pachca.com/en/agent-ready/pyrus)59.4
- [Shtab](https://pachca.com/en/agent-ready/shtab)90.3
- [SimpleOne SDLC](https://pachca.com/en/agent-ready/simpleone)54.1
- [TeamStorm](https://pachca.com/en/agent-ready/teamstorm)64.9
- [WEEEK](https://pachca.com/en/agent-ready/weeek)63.6
- [Yandex Tracker](https://pachca.com/en/agent-ready/yandex-tracker)54.9
- [YouGile](https://pachca.com/en/agent-ready/yougile)65.2