Directory
Find public business profiles, ownership status and available verification evidence. A listing is separate from an ASG membership.
Discover businesses ↗WEBSDOCS / OFFICIAL AI ENTRANCE
Read the facts.
Find the right route.
Approved WebsDocs information for AI assistants, developers and people. Discover our products, read the public policy, and use the supported routes for questions and permitted requests.
Looking for a business? Search the Directory. Building your own AI-facing presence? Explore ASG.
—Published businesses
—Verified businesses
—Countries & territories
Directory coverage · scheduled snapshot.
ONE NETWORK / DISTINCT ROLES
The right entrance for each task.
This gateway publishes WebsDocs’ own approved information. Directory listings and client ASG gateways are separate public surfaces.
AI Sales Gateway
Give your business its own approved AI-facing profile, live answers and permitted buyer-intent routes. You control the public facts and commercial decisions.
Explore ASG ↗WebsDocs AI gateway
Read official WebsDocs information and follow its public interfaces. Private dashboards, credentials and customer records are outside this public information layer.
Read the public policy ↗INTERFACES / CAPABILITIES
Clear protocol boundaries.
A published route, configured capability and completed action are different things. Read discovery responses before attempting an integration.
Agent-to-agent requests
The gateway exposes handshake, session messaging, JSON-RPC message sending and permitted action-request intake.
Follow the agent card and handshake response. An accepted request is not proof of payment, publication or another completed business action.
Read the agent card ↗Seller-controlled checkout
The UCP discovery profile describes checkout services and a session endpoint. Signed, authorized session operations depend on the deployed configuration.
Delegated execution is conditional. AIG routes to the owning product checkout; it does not independently set prices or take custody of funds.
Read UCP discovery ↗Check the manifest first
The gateway manifest currently declares MCP readiness false. Use the published HTTP and A2A routes for this gateway.
Public route JSON and an A2A JSON-RPC endpoint are not substitutes for an MCP server. Do not infer MCP support from a network status indicator.
Check advertised capabilities ↗FOR AGENTS & DEVELOPERS
Public route explorer.
Read-only links open in a new tab. Copy an endpoint for your integration. This explorer never submits an action or creates a checkout session.
GET
Discovery guide
/llms.txtStart here. Plain-text discovery instructions and official entry points.
GET
Agent manifest
/.well-known/websdocs-agent.jsonRead advertised gateway capabilities and public endpoints.
GET
A2A agent card
/.well-known/agent-card.jsonRead the A2A interfaces and supported interaction model.
GET
Business profile
/ai-room/profileRead approved public information about WebsDocs.
GET
Public policy
/ai-room/policyCheck permitted knowledge, requests and access boundaries.
GET
Public pricing
/ai-room/pricingRead the published machine-facing pricing information. Confirm actual charges in the selected checkout.
GET
Public routes
/ai-room/routesFind approved product, support and public information routes.
GET / POST
Public questions
/ai-room/askAsk from approved public knowledge, subject to gateway policy. Consult discovery before sending a question.
GET / POST
A2A handshake
/a2a/v1/handshakeGET reads interface guidance; POST starts a permitted handshake.
GET / POST
A2A messages
/a2a/v1/messageDiscover the interface, then send authorized session messages.
GET / POST
A2A JSON-RPC
/a2a/v1/message:sendRead interface guidance before sending JSON-RPC messages. This is A2A, not an MCP endpoint.
GET / POST
A2A action requests
/a2a/v1/action-requestSubmit permitted requests under session scope and policy. Intake does not guarantee execution.
GET / POST
Checkout door
/ai-room/checkout-doorGET describes the checkout door. POST is an action route; follow its authorization and product requirements.
GET
UCP discovery
/.well-known/ucpInspect checkout capability and configuration-dependent delegated support.
SIGNED OPERATIONS
UCP checkout sessions
/checkout/v1/checkout-sessionsCreate, read, update or complete/cancel sessions through supported paths. Authorization and idempotency requirements apply.
GET
Structured identity
/schema.jsonldRead WebsDocs structured public identity information.
No matching routes. Try “pricing”, “profile” or “checkout”.
Directory APIs belong to the Directory service: Directory OpenAPI ↗. Client business gateways have their own URLs and entitlements.
CHECKOUT / AUTHORIZATION
Read freely. Act with permission.
The public discovery layer explains what is possible. A valid checkout request still needs the required authorization, supported product and confirmed terms.
Inspect
Read the checkout door and UCP discovery response. Check which execution modes are available.
Authorize
Use the required signed request path. Mutating checkout-session requests require an idempotency key.
Continue
Follow the approved seller checkout URL or authorized delegated flow. Do not send raw card credentials to this gateway.
Confirm
Use the owning product’s verified result. A session URL or accepted intent is not a successful payment.
BUSINESS PRODUCTS
Connect discovery with useful service.
Each product has its own role. Choose the capability that fits the business; a Directory listing does not purchase an AI subscription.
Customer conversations
RTD combines Voice, Widget Chat and Human Inbox in one workspace. Human Inbox Free and paid AI plans have different usage and feature limits.
Explore RTD ↗
Working requests
Add booking, technical support, billing enquiries, sales quotes, ecommerce and escalation workflows to an eligible paid RTD plan.
Explore BizDesk ↗Clear plans and terms
Compare free entry, trials, introductory offers and standard renewal prices. Directory Presence, RTD and ASG are separate purchases.
Compare pricing ↗START WITH THE OFFICIAL SOURCE