Loading

Webex scores 28 out of 100 on the Agent Readiness Index

Webex reaches level 0, Closed. Discoverability is the strongest area at 95 out of 100. Identity and delegation is the weakest at 0.

Webex was scanned on October 23, 2026. Its score is 28 out of 100, level 0, Closed. Declared agents are blocked from the public website. To reach level 1, Tolerated: The home page must load for a declared agent and robots.txt must not block every agent.

Website: webex.com

Score by area

AreaScoreWhat it asks
Discoverability95 out of 100, worth 22 pointsCan an agent find and read your pages?
Protocol access51 out of 100, worth 14 pointsCan an agent connect to you through MCP or an API?
Identity and delegation0 out of 100, worth 12 pointsCan a customer give an agent limited access without sharing a password?
Web experience84 out of 100, worth 20 pointsDoes your site work when an agent uses it?
Voice and IVRNot measured yetWhat happens when an agent calls your phone line?
Policy and governance75 out of 100, worth 6 pointsDo your terms allow agents that act for customers?
Marketing readiness0 out of 100, worth 18 pointsCan an agent see what you sell, and buy or book it?

What is holding Webex back

  1. Home page for a declared agent, 38.6 points lost. The home page returned 403 to a declared agent. Fix: Allow declared agents through bot management on public pages, and verify them with signed requests.
  2. Product or service catalog with images, 20.5 points lost. No catalog of products or services with images was found: no feed, no catalog file and no structured data. Fix: Publish a product or service feed JSON or XML with an image and a price or plan for each item, and add structured data to the pages.
  3. OAuth and OpenID metadata, 4.9 points lost. No OAuth or OpenID metadata was found on the 7 hosts that answered. 7 other hosts did not answer the scanner and could not be checked. Agents cannot discover where to send a customer to approve access. Fix: Publish /.well known/oauth authorization server and /.well known/oauth protected resource for the customer facing APIs.
  4. MCP server, 4.3 points lost. Public documentation mentions MCP, but no server or card was found. Fix: Publish a remote MCP server with OAuth. Start with read only tools such as account status, orders or location search, and publish a server card at /.well known/mcp/server card.

What already works

  • Sign in page loads for a declared agent in a browser
  • llms.txt guide for agents
  • Content available without running scripts

How Webex compares

The average score for other is 42.6 out of 100 across 989 organizations. The average across all 2,353 scored organizations is 44.2 out of 100.

Similar organizations

More on this report