---
title: "Would AI Agents Shortlist Adaptive? 65/100 AI Agent Readiness | VertoDigital"
description: "Adaptive scored 65/100 (At risk) on AI agent readiness. See whether buyers' AI agents would shortlist Adaptive: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/adaptive-build"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/adaptive-build/og.png"
---

> For AI agents: an index of every page on this site is at https://vertodigital.com/llms.txt

Free B2B AI Visibility Checker

# Would an AI agent shortlist Adaptive?

Last checked 2026-10-15 · 21 checks · Read-only, no browser

## Results for adaptive.build

**65 out of 100** · At risk

AI agents consider Adaptive, but lose the way before buyers reach the sales team.

- **Research** (Website readability): 100% · 35/35 pts · 8/8 passed
- **Evaluate** (Product access): 0% · 0/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 57% · 23/40 pts · 3/5 passed

## How a buyer's AI agent experiences Adaptive

- Research: passed
- Evaluate: stuck
- Reach out: partly

The agent read your site and understood what you do. It found your demo page at /demo, but found no form there. Journey ended.

## What Adaptive should fix first to make the shortlist

### 01 See the form

Add a simple form, or at least a visible sales email address.

### 02 Discoverable

Tell agents where your MCP server is: publish /.well-known/mcp/server-card.json (or /.well-known/mcp.json) with its URL, and mention it in your developer docs and llms.txt. No MCP server yet? If your product has an API, it is the fastest way to let agents evaluate it.

### 03 Documented

Link developer docs from the homepage and publish your OpenAPI spec at a discoverable URL.

## Research: can AI agents read and understand Adaptive?

### 1.1 AI search crawler access

**pass** · 7/7 pts

AI search and assistant bots are allowed to read your site.

Training bots: GPTBot: blocked, ClaudeBot: blocked, Google-Extended: blocked, CCBot: blocked. Blocking these is a valid choice and doesn't affect this score.

Evidence:

- `https://www.adaptive.build/robots.txt · HTTP 200 · blocked from /: none; blocked on key paths: none`

### 1.2 Homepage access

**pass** · 7/7 pts

Your homepage lets in requests that identify as ChatGPT, Claude and Perplexity, and serves them the same page as a browser.

Evidence:

- `https://www.adaptive.build/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.adaptive.build/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.adaptive.build/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.adaptive.build/ · as Perplexity-User · HTTP 200 · HTTP 200`

### 1.3 Content without JavaScript

**pass** · 7/7 pts

Your pages carry real text in the page code (878 words on the homepage, 1165 on a typical key page).

Evidence:

- `https://www.adaptive.build/ · homepage: pass (878 words) · key pages: pass (median 1165 words across 4)`
- `https://www.adaptive.build/ · 878 words of page content in raw HTML (1070 including nav and footer)`
- `sampled pages: product /product-updates (10727 words), customer /success-stories/j7-services (1519 words), blog /blog/why-we-built-an-ai-project-accountant-and-raised-30m-to-build-more-of-it (1165 words), product /product/adaptive-vs (349 words); median words: 1165`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

None of your key pages are hidden from search and AI.

Evidence:

- `checked homepage + 4 key pages`

### 1.5 Page essentials

**pass** · 3/3 pts

Your pages clearly state what they are: titles, descriptions and headings are in place.

Evidence:

- `https://www.adaptive.build/ · title:true desc:true h1:1 canonical:true`
- `https://www.adaptive.build/product-updates · title:true desc:true h1:1 canonical:true`
- `https://www.adaptive.build/success-stories/j7-services · title:true desc:true h1:1 canonical:true`
- `https://www.adaptive.build/blog/why-we-built-an-ai-project-accountant-and-raised-30m-to-build-more-of-it · title:true desc:true h1:1 canonical:true`
- `https://www.adaptive.build/product/adaptive-vs · title:true desc:true h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

Your site identifies Adaptive with structured data, so AI can connect the website to the brand.

Evidence:

- `https://www.adaptive.build/ · Organization: name=Adaptive url=yes logo=yes sameAs=no`

### 1.7 Sitemap

**pass** · 2/2 pts

Your sitemap is valid, linked and up to date (we checked 1 of the 1 sitemaps in your index).

Evidence:

- `https://www.adaptive.build/sitemap-index.xml · valid:true linkedFromRobots:true urls:224 latestLastmod:2026-10-14T00:00:00.000Z (sitemap index with 1 sitemaps; checked 1, 1 valid)`

### 1.8 Response speed

**pass** · 2/2 pts

Your homepage responds quickly (101 ms, median of 5 requests).

Evidence:

- `https://adaptive.build/ · median 101 ms across 5 requests`
- `https://adaptive.build/ · as crawler · HTTP 200 · 797 ms to response headers`
- `https://www.adaptive.build/ · as browser · HTTP 200 · 79 ms to response headers`
- `https://www.adaptive.build/ · as ChatGPT-User · HTTP 200 · 136 ms to response headers`
- `https://www.adaptive.build/ · as Claude-User · HTTP 200 · 101 ms to response headers`
- `https://www.adaptive.build/ · as Perplexity-User · HTTP 200 · 80 ms to response headers`

### 1.9 AI guide files

**bonus** · +1 bonus

You publish an llms.txt file. Early, and a good signal.

Evidence:

- `https://www.adaptive.build/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Adaptive's product?

### 2.1 Discoverable

**fail** · 0/4 pts

We couldn't find an MCP server from your website. If you have one, AI agents arriving at your site can't find it either.

**How to fix:** Tell agents where your MCP server is: publish /.well-known/mcp/server-card.json (or /.well-known/mcp.json) with its URL, and mention it in your developer docs and llms.txt. No MCP server yet? If your product has an API, it is the fastest way to let agents evaluate it.

Evidence:

- `https://www.adaptive.build/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.adaptive.build/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.adaptive.build/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.adaptive.build/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.adaptive.build/.well-known/oauth-protected-resource · HTTP 404 · HTTP 404`

### 2.2 Working

**fail** · 0/4 pts

There is no MCP server to test.

### 2.3 Understandable

**fail** · 0/3 pts

There is no MCP server to evaluate.

### 2.4 Connectable

**fail** · 0/2 pts

There is no MCP server to connect to.

### 2.5 Documented

**fail** · 0/2 pts

We couldn't find developer docs linked from your homepage or an OpenAPI spec.

**How to fix:** Link developer docs from the homepage and publish your OpenAPI spec at a discoverable URL.

Evidence:

- `https://www.adaptive.build/ · no developer docs link on homepage`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

## Reach out: can an AI agent get a buyer to Adaptive's sales team?

### 3A Find the way in

**pass** · 8/8 pts

AI agents can find your demo page (/demo) from the homepage.

Evidence:

- `https://www.adaptive.build/demo · demo page found via homepage`

### 3B Let in

**pass** · 10/10 pts

Your demo page lets in requests that identify as ChatGPT, Claude and Perplexity.

Evidence:

- `https://www.adaptive.build/demo · as browser · HTTP 200 · browser baseline 200`
- `https://www.adaptive.build/demo · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.adaptive.build/demo · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.adaptive.build/demo · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.adaptive.build/robots.txt · robots disallow /demo for: none`

### 3C See the form

**fail** · 0/12 pts

We couldn't find a form on your conversion page.

**How to fix:** Add a simple form, or at least a visible sales email address.

Evidence:

- `https://www.adaptive.build/demo · as browser · HTTP 200 · no <form> element and no known form embed`

### 3D Understand the form

**fail** · 0/5 pts

Not scored: an agent can't understand a form it can't see.

### 3F Agent-friendly route

**bonus** · +0 bonus

Opportunity: a visible sales email, contact details in structured data, or a contact API gives agents a way in even when forms fail. Very few B2B sites do this yet.

Evidence:

- `email:none contactPoint:false llms.txt contact:false MCP contact tool:false`

### 3G Readable proof

**pass** · 5/5 pts

Your case studies are readable text, so agents can use them as proof.

Evidence:

- `https://www.adaptive.build/success-stories/j7-services · HTTP 200 · 1519 words of page content in raw HTML (nav and footer excluded)`

### 3H Self-serve path

**N/A** · not scored

No product-led signals (free trial, sign up) found, so self-serve was not scored.

## What Adaptive gets right

- AI search and assistant bots are allowed to read your site.
- Your homepage lets in requests that identify as ChatGPT, Claude and Perplexity, and serves them the same page as a browser.
- Your pages carry real text in the page code (878 words on the homepage, 1165 on a typical key page).
- None of your key pages are hidden from search and AI.
- Your pages clearly state what they are: titles, descriptions and headings are in place.
- Your site identifies Adaptive with structured data, so AI can connect the website to the brand.
- Your sitemap is valid, linked and up to date (we checked 1 of the 1 sitemaps in your index).
- Your homepage responds quickly (101 ms, median of 5 requests).
- AI agents can find your demo page (/demo) from the homepage.
- Your demo page lets in requests that identify as ChatGPT, Claude and Perplexity.
- Your case studies are readable text, so agents can use them as proof.

## Next steps

### Share with your team

Send the report to your web team, or post your score on LinkedIn.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fvertodigital.com%2Fb2b-ai-visibility-checker%2Ftool%2Fadaptive-build)

### Compare with a competitor

Agents can start one through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"competitor.com","mode":"compare","compare_with":"adaptive.build"}`.

Comparisons are private. Only people with the link can see them.

### Fixed something?

Agents can rescan through the API: `POST https://vertodigital.com/agent/readiness/checks` with `{"domain":"adaptive.build"}`.

[How we checked](https://vertodigital.com/b2b-ai-visibility-checker/tool/how-it-works)

[Is this your company? Request an update or removal](https://vertodigital.com/b2b-ai-visibility-checker/tool/request-update)

## The check shows where agents drop off. The Assessment shows what it's costing you.

Our Pipeline Readiness Assessment is a complimentary 5-day diagnostic across paid efficiency, organic and AI search visibility, and pipeline data, with a 30-minute debrief from a specialist.

[Book your Pipeline Readiness Assessment](https://vertodigital.com/assessment?domain=adaptive.build&source=b2b-ai-visibility-checker)
