Search demand map · updated 2026-09-02

128 questions agents, developers, and providers may ask.

This bank maps each question to an existing evidence or action page. It is designed for Search Console analysis, content gap decisions, internal linking, and agent-sourceability without manufacturing one thin page per query.

Open the machine-readable JSON bank

Search Console regex bank

Use Query → Custom (regex). Search Console uses RE2 and matches partial, case-insensitive strings by default.

Explicit question forms

(^|.* )(who|what|when|where|why|how|which|can|could|should|would|will|do|does|did|is|are|was|were|has|have)( |$).*

Find queries phrased as questions. Search Console matching is partial and case-insensitive by default.

Buyer and problem intent

(verify|check|validate|validator|scan|audit|inspect|registry|register|list|listing|listed|discover|directory|bazaar|cost|price|payment|pay|settlement|readiness|manifest|openapi|whitepaper|trust|reputation|security|endpoint)

Capture the concrete jobs Ontario can solve without requiring question grammar.

MCP Registry intent

(mcp.*(registry|register|listing|listed|server|tool|inspect|audit|verify|check|status)|(registry|register|listing|listed).*(mcp))

Isolate MCP Registry, server-readiness, and tool-inspection demand.

x402 verification intent

(x402.*(verify|verifier|check|checker|validate|validator|scan|readiness|security|manifest|openapi)|(verify|verifier|check|checker|validate|validator|scan|readiness).*(x402))

Find pre-payment verification and implementation-quality searches.

Bazaar and provider-listing intent

(bazaar|coinbase.*(listing|listed|discover|directory)|get listed|service listing|paid api directory)

Find providers trying to become discoverable and buyers looking for paid APIs.

Agent payment and preflight intent

(agent.*(pay|payment|spend|preflight|trust|reputation|discover|tool)|(pay|payment|spend|preflight).*(agent))

Find financially sensitive agent-payment and tool-selection demand.

Search impressions and matching queries are attention evidence. They do not prove a unique visitor, buyer, customer, or payment. Validate commercial outcomes against the settlement ledger and product attribution.

Question map

Ontario Protocol and category

Recommended destination: / · intent: entity_and_category

x402 and HTTP 402 basics

Recommended destination: /docs · intent: protocol_education

Endpoint readiness and verification

Recommended destination: /verify · intent: verify_endpoint

Reports, freshness, and signatures

Recommended destination: /reports · intent: inspect_evidence

x402 manifests and OpenAPI

Recommended destination: /answers/x402-manifest-validator · intent: implementation_validation

Agent payment preflight

Recommended destination: /docs/agent-payment-preflight · intent: authorize_agent_spend

MCP Registry and remote tools

Recommended destination: /tools/mcp-registry-readiness · intent: mcp_registry_readiness

Agent Tool Procurement Passport

Recommended destination: /tools/agent-tool-procurement-passport · intent: compare_and_procure_tool

Coinbase Bazaar discovery

Recommended destination: /tools/coinbase-bazaar-readiness · intent: bazaar_discovery

Provider listing and publication

Recommended destination: /docs/x402-service-listing-quickstart · intent: publish_service

Discovery and tool routing

Recommended destination: /discover · intent: find_paid_tool

Pricing and payment

Recommended destination: /pricing · intent: pricing_and_purchase

Security, privacy, and abuse

Recommended destination: /trust/what-ontario-does-not-check · intent: security_boundary

Agent trust and reputation

Recommended destination: /trust · intent: agent_trust

Troubleshooting

Recommended destination: /docs · intent: troubleshoot_integration

Comparison and selection

Recommended destination: /compare/x402-verification-tools · intent: compare_tools