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

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

## Results for onyx.security

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

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

- **Research** (Website readability): 100% · 35/35 pts · 8/8 passed
- **Evaluate** (Product access): 13% · 2/15 pts · 0/5 passed
- **Reach out** (Agent conversion): 88% · 35/40 pts · 4/5 passed

## How a buyer's AI agent experiences Onyx Security

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

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

## What Onyx Security should fix first to make the shortlist

### 01 Readable proof

Publish customer proof as readable pages. Agents compare vendors on evidence.

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

### 03 Documented

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

## Research: can AI agents read and understand Onyx Security?

### 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://www.onyx.security/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.onyx.security/ · as browser · HTTP 200 · browser baseline 200`
- `https://www.onyx.security/ · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.onyx.security/ · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.onyx.security/ · 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 (662 words on the homepage, 682 on a typical key page).

Evidence:

- `https://www.onyx.security/ · homepage: pass (662 words) · key pages: pass (median 682 words across 4)`
- `https://www.onyx.security/ · 662 words of page content in raw HTML (789 including nav and footer)`
- `sampled pages: product /platform (700 words), blog /blog/onyx-113m-series-b-keeping-humans-in-control-as-ai-becomes-smarter (1287 words), about /about (570 words), product /platform/ai-roi (682 words); median words: 682`

### 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.onyx.security/ · title:true desc:true h1:1 canonical:true`
- `https://www.onyx.security/platform · title:true desc:true h1:1 canonical:true`
- `https://www.onyx.security/blog/onyx-113m-series-b-keeping-humans-in-control-as-ai-becomes-smarter · title:true desc:true h1:1 canonical:true`
- `https://www.onyx.security/about · title:true desc:true h1:1 canonical:true`
- `https://www.onyx.security/platform/ai-roi · title:true desc:true h1:1 canonical:true`

### 1.6 Company identity

**pass** · 3/3 pts

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

Evidence:

- `https://www.onyx.security/ · Organization: name=Onyx url=yes logo=yes sameAs=yes`

### 1.7 Sitemap

**pass** · 2/2 pts

Your sitemap is valid, linked and up to date.

Evidence:

- `https://www.onyx.security/sitemap.xml · valid:true linkedFromRobots:true urls:96 latestLastmod:2026-10-14T18:12:22.452Z`

### 1.8 Response speed

**pass** · 2/2 pts

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

Evidence:

- `https://onyx.security/ · median 33 ms across 5 requests`
- `https://onyx.security/ · as crawler · HTTP 200 · 621 ms to response headers`
- `https://www.onyx.security/ · as browser · HTTP 200 · 33 ms to response headers`
- `https://www.onyx.security/ · as ChatGPT-User · HTTP 200 · 28 ms to response headers`
- `https://www.onyx.security/ · as Claude-User · HTTP 200 · 31 ms to response headers`
- `https://www.onyx.security/ · as Perplexity-User · HTTP 200 · 41 ms to response headers`

### 1.9 AI guide files

**bonus** · +0 bonus

Opportunity: an llms.txt file and markdown page versions give AI agents a clean map of your site. Not yet confirmed as used by the major AI engines, but cheap to add.

Evidence:

- `https://www.onyx.security/llms.txt · HTTP 404 · no valid llms.txt`
- `no <link rel="alternate" type="text/markdown">`

## Evaluate: can AI agents try Onyx Security's product?

### 2.1 Discoverable

**warning** · 2/4 pts

Your website mentions an MCP server, but doesn't tell AI agents where it is in a way they can find on their own.

**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.

Evidence:

- `https://www.onyx.security/.well-known/mcp.json · HTTP 404 · HTTP 404`
- `https://www.onyx.security/.well-known/mcp/server-card.json · HTTP 404 · HTTP 404`
- `https://www.onyx.security/.well-known/ai-catalog.json · HTTP 404 · HTTP 404`
- `https://www.onyx.security/.well-known/api-catalog · HTTP 404 · HTTP 404`
- `https://www.onyx.security/.well-known/oauth-protected-resource · HTTP 404 · HTTP 404`
- `https://www.onyx.security/ · homepage mentions MCP: https://www.onyx.security/solutions/mcp-security, https://www.onyx.security/solutions/mcp-security`

### 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.onyx.security/ · 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 Onyx Security's sales team?

### 3A Find the way in

**pass** · 8/8 pts

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

Evidence:

- `https://www.onyx.security/get-a-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.onyx.security/get-a-demo · as browser · HTTP 200 · browser baseline 200`
- `https://www.onyx.security/get-a-demo · as ChatGPT-User · HTTP 200 · HTTP 200`
- `https://www.onyx.security/get-a-demo · as Claude-User · HTTP 200 · HTTP 200`
- `https://www.onyx.security/get-a-demo · as Perplexity-User · HTTP 200 · HTTP 200`
- `https://www.onyx.security/robots.txt · robots disallow /get-a-demo for: none`

### 3C See the form

**pass** · 12/12 pts

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

Evidence:

- `https://www.onyx.security/get-a-demo · as browser · HTTP 200 · contact form in page code with 4 fields (0-1/firstname, 0-1/lastname, 0-1/email, 0-1/company)`

### 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://www.onyx.security/get-a-demo · 4 fields, 0 unlabelled, 4 required, email type: true`

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

**fail** · 0/5 pts

We couldn't find customer stories or case studies.

**How to fix:** Publish customer proof as readable pages. Agents compare vendors on evidence.

Evidence:

- `no customers / case-studies link on homepage, sitemap or key pages`

### 3H Self-serve path

**N/A** · not scored

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

## What Onyx Security 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 (662 words on the homepage, 682 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 Onyx with structured data, so AI can connect the website to the brand.
- Your sitemap is valid, linked and up to date.
- Your homepage responds quickly (33 ms, median of 5 requests).
- AI agents can find your demo page (/get-a-demo) from the homepage.
- Your demo page lets in requests that identify as ChatGPT, Claude and Perplexity.
- Your demo 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.

## 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%2Fonyx-security)

### 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":"onyx.security"}`.

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":"onyx.security"}`.

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