---
title: "Would AI Agents Shortlist Namespace? 90/100 AI Agent Readiness | VertoDigital"
description: "Namespace scored 90/100 (Shortlist-ready) on AI agent readiness. See whether buyers' AI agents would shortlist Namespace: can they research it, evaluate the product and reach sales? Evidence and fixes included."
url: "https://vertodigital.com/b2b-ai-visibility-checker/tool/namespace-so"
image: "https://vertodigital.com/b2b-ai-visibility-checker/tool/namespace-so/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 Namespace?

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

## Results for namespace.so

**90 out of 100** · Shortlist-ready

AI agents can research Namespace, evaluate the product and get buyers to the sales team.

- **Research** (Website readability): 96% · 33.5/35 pts · 7/8 passed
- **Evaluate** (Product access): 7% · 1/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 100% · 40/40 pts · 5/5 passed

## How a buyer's AI agent experiences Namespace

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

The agent read your site and understood what you do. It found your contact page at /contact and could see how to reach your sales team.

## What Namespace should fix first to make the shortlist

### 01 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.

### 02 Page essentials

Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.

### 03 Documented

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

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

### 1.1 AI search crawler access

**pass** · 7/7 pts

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

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

Evidence:

- `https://namespace.so/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://namespace.so/ · as browser · HTTP 200 · browser baseline 200`
- `https://namespace.so/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://namespace.so/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://namespace.so/ · 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 (581 words on the homepage, 577 on a typical key page).

Evidence:

- `https://namespace.so/ · homepage: pass (581 words) · key pages: pass (median 577 words across 5)`
- `https://namespace.so/ · 581 words of page content in raw HTML (720 including nav and footer)`
- `sampled pages: product /docs/solutions/github-actions (1315 words), customer /customers/zed (931 words), blog /blog/series-b (577 words), about /company (291 words), product /docs/solutions/docker-builders (321 words); median words: 577`

### 1.4 Accidentally hidden pages

**pass** · 4/4 pts

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

Evidence:

- `checked homepage + 5 key pages`

### 1.5 Page essentials

**warning** · 1.5/3 pts

3 of 6 pages we checked are missing a description / main heading.

**How to fix:** Give every key page a unique title, a one-sentence description, one main heading and a canonical URL.

Evidence:

- `https://namespace.so/ · title:true desc:true h1:1 canonical:true`
- `https://namespace.so/docs/solutions/github-actions · title:true desc:false h1:1 canonical:true`
- `https://namespace.so/customers/zed · title:true desc:true h1:1 canonical:true`
- `https://namespace.so/blog/series-b · title:true desc:true h1:1 canonical:true`
- `https://namespace.so/company · title:true desc:true h1:0 canonical:true`
- `https://namespace.so/docs/solutions/docker-builders · title:true desc:false h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

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

Evidence:

- `https://namespace.so/ · Organization: name=Namespace url=yes logo=yes sameAs=yes`

### 1.7 Sitemap

**pass** · 2/2 pts

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

Evidence:

- `https://namespace.so/sitemap.xml · valid:true linkedFromRobots:true urls:387 latestLastmod:2026-10-13T10:18:46.900Z (sitemap index with 2 sitemaps; checked 2, 2 valid)`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://namespace.so/ · median 16 ms across 5 requests`
- `https://namespace.so/ · as crawler · HTTP 200 · 639 ms to response headers`
- `https://namespace.so/ · as browser · HTTP 200 · 9 ms to response headers`
- `https://namespace.so/ · as ChatGPT-User · HTTP 200 · 32 ms to response headers`
- `https://namespace.so/ · as Claude-User · HTTP 200 · 16 ms to response headers`
- `https://namespace.so/ · as Perplexity-User · HTTP 200 · 12 ms to response headers`

### 1.9 AI guide files

**bonus** · +2 bonus

You publish an llms.txt file and markdown versions of your pages. Early, and a good signal.

Evidence:

- `https://namespace.so/llms.txt · HTTP 200 · valid llms.txt (markdown, starts with # heading)`
- `markdown alternate: /docs/solutions/github-actions.md`

## Evaluate: can AI agents try Namespace'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://namespace.so/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://namespace.so/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://namespace.so/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://namespace.so/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://namespace.so/.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

**warning** · 1/2 pts

We couldn't find an OpenAPI spec.

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

Evidence:

- `https://namespace.so/ · docs link: https://namespace.so/#`
- `no OpenAPI found (api-catalog service-desc or homepage link)`

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

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://namespace.so/contact · contact page found via homepage`

### 3B Let in

**pass** · 10/10 pts

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

Evidence:

- `https://namespace.so/contact · as browser · HTTP 200 · browser baseline 200`
- `https://namespace.so/contact · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://namespace.so/contact · as Claude-User · HTTP 200 · HTTP 200`
- `https://namespace.so/contact · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://namespace.so/robots.txt · robots disallow /contact for: none`

### 3C See the form

**pass** · 12/12 pts

Your contact form is in the page code, so AI agents can see it.

Evidence:

- `https://namespace.so/contact · as browser · HTTP 200 · contact form in page code with 4 fields (firstName, companyName, email, message)`

### 3D Understand the form

**pass** · 5/5 pts

Your form is clearly labelled with 4 required fields. An agent can fill it for its buyer.

Evidence:

- `https://namespace.so/contact · 4 fields, 0 unlabelled, 4 required, email type: true`

### 3F Agent-friendly route

**bonus** · +3 bonus

You give agents a direct route: visible email, ContactPoint data, contact API.

Evidence:

- `email:sales@namespace.so contactPoint:true llms.txt contact:true 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://namespace.so/customers/zed · HTTP 200 · 931 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 Namespace 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 (581 words on the homepage, 577 on a typical key page).
- None of your key pages are hidden from search and AI.
- Your site identifies Namespace with structured data, so AI can connect the website to the brand.
- Your sitemap is valid, linked and up to date (we checked 2 of the 2 sitemaps in your index).
- Your homepage responds quickly (16 ms, median of 5 requests).
- AI agents can find your contact page (/contact) from the homepage.
- Your contact page lets in requests that identify as ChatGPT, Claude and Perplexity.
- Your contact form is in the page code, so AI agents can see it.
- Your form is clearly labelled with 4 required fields. An agent can fill it for its buyer.
- 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%2Fnamespace-so)

### 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":"namespace.so"}`.

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":"namespace.so"}`.

[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=namespace.so&source=b2b-ai-visibility-checker)
