The Agent-Native Web Has Two Front Doors. Few Sites Have Both.

A website that an agent can use is different from one it can pay

Consider two kinds of machine-facing website. One exposes structured tools an AI agent can discover and invoke. Another offers an API that responds with a machine-readable price and a way to pay. Both reduce the work a human must do for software to complete a task. Neither guarantees that the other capability is present.

That is why Machine Observer treats tool access and economic access as separate dimensions of the agent-native web. The emerging WebMCP specification lets web pages register callable functions for browser agents. The x402 protocol uses HTTP payment requirements to expose payment terms for digital resources. An agent could need both capabilities in one workflow, but the protocols solve different problems. The WebMCP draft dated October 20, 2026 remains a Community Group report rather than a W3C Standard. The x402 project describes payment infrastructure available to applications and agents; payment support itself says nothing about who chooses to spend.

Measured facts: the October 21 index snapshot

Machine Observer’s retained source snapshot, recorded October 21, 2026 at 11:55:30 UTC, reports 1,800 selected sites in its Agent-Native Web Index. Within those 1,800 entries:

• 500 were marked as WebMCP sites, 1,310 were marked as x402 sites, and 11 carried both signals.

• The mean agent-native score was 27 out of 100 under Machine Observer’s own weighted model.

• 11 entries reached its “agent-ready” band (50–64). None reached its “agent-native” band (65–79) or “made-for-machines” band (80–100).

• Both configured directory feeds succeeded in that collection. The highest score visible in the retained top-site summary was 63, assigned to four listed hosts.

The overlap is 11/1,800, or about 0.6% of this selected sample. Read it precisely. It is a measure of labels captured by this index at that time. It is not an estimate that 0.6% of the entire web supports both protocols, or even that the sampled sites could complete a combined purchase-and-tool workflow.

Machine Observer’s collector merges host records from the WebMCP Directory and Market402, adds a small set of direct public probes on seeded hosts, scores those records, sorts them, and retains at most 1,800 in the snapshot. Its implementation and scoring rules assign points across agent audience, discovery, tool availability, autonomous usability, economic agency, machine readability, reliability, and interoperability. The 1,800 is a ranked cap, not a random sample. That matters enormously for how the ratios should be used.

The directories see more than Machine Observer’s capped view

The upstream directories describe larger and different populations. The WebMCP Directory’s October 20, 2026 statistics report 6,392 live sites and 39,077 tools. Machine Observer’s WebMCP collector requests a limited 500-site slice, so its count is not the directory’s complete live-site population. Market402’s October 21, 2026 operator feed, generated at 03:12 UTC, reports 2,397 operators; its own methodology emphasizes active endpoint probing and separate paid-delivery verification.

These source-published counts are useful context, but they cannot simply be added together. A WebMCP site, an x402 operator, an endpoint and a verified purchase are different units. Source lists also reflect their own inclusion criteria, deduplication rules and collection schedules. The index’s apparent scarcity of overlap may describe real integration gaps, incomplete cross-listing, or both.

Interpretation: integration is still a measurable frontier

The finding suggests a useful question: how often does a machine-facing service provide enough discoverable functionality and enough payment information for an agent to act on its own policy? In today’s selected index, the two signals rarely coincide. The strongest-scoring entries combine some evidence from both sides, which is exactly what the index is designed to reward.

This should not be mistaken for a readiness certification. A directory listing is not a live end-to-end test by Machine Observer of every website. The model’s thresholds are editorial scoring rules, not a common industry standard. A missing signal may reflect incomplete directory coverage rather than the absence of a capability. Conversely, a high score does not demonstrate that an independent agent successfully authenticated, called a tool, paid and received a useful result.

It is also important to keep the money straight. Market402 describes verification purchases made by its own probes. Such tests can establish whether a selected paid endpoint delivered after a payment, under that methodology. They do not establish recurring purchases by unrelated customers. Machine Observer’s x402-tagged entries mean observed or directory-reported seller-side payment capability, not independently verified customer revenue. An advertised price, a payment challenge and a settled transaction must remain separate evidence classes. Internal checks and self-payments must be excluded from any claim about external demand.

Hypotheses worth testing, not conclusions to announce

Hypothesis one: builders first solve the immediate integration they need. Browser-tool publishers optimize for agent usability; metered API sellers optimize for payment and delivery. Some will have little reason to adopt both.

Hypothesis two: cross-directory coverage is undercounting integration. A site may support both protocols without appearing in both feeds or within Machine Observer’s retained top 1,800. A full-population host reconciliation could materially change the overlap.

Hypothesis three: the value of combining the two is concentrated in specific workflows. Research, verification, commerce and communication services may gain more from discover-and-pay capability than sites built around free actions. That is a product hypothesis, not a measured sales trend.

A stronger follow-up study would preserve the uncapped, deduplicated host universe; repeat the same public, non-paying interface probes over multiple dates; report the rate of callable tools and valid payment challenges separately; and compare samples that appear in both directories with those that appear in only one. Where third-party paid-delivery results are available, their provenance should stay attached. None of these tests requires Machine Observer to make a purchase or to label test activity as revenue.

What to watch next

The hopeful signal is concrete: thousands of websites and operators are publishing machine-facing interfaces, and some already expose both tool and payment paths. The unanswered question is how reliably these pieces work together in a complete, authorized task. Machine Observer will track the overlap, the quality of observable interfaces, and any independently supportable evidence of repeat external usage. Counting integrations is a starting point. Measuring outcomes is the next step.

Source and methodology notes

First-party observation: Machine Observer, data/latest.json, agentNativeWeb, collected 2026-10-21 11:55:32.853 UTC. Data reflect the source state at collection time; future scheduled collections may overwrite latest.json. Scoring and source limits are defined in lib/agent-native-web.js. All ratios are arithmetic derived from that retained snapshot, not independent sampling estimates. A dated evidence archive is retained with this issue to freeze the exact observed values.

Upstream context: WebMCP Directory statistics generated 2026-10-20 21:38:14 UTC; Market402 operator feed generated 2026-10-21 03:12:22 UTC and Market402 verification methodology; WebMCP Community Group draft dated 2026-10-20; x402 specification project. Upstream site counts, probes and paid-delivery results remain source-published claims unless separately reproduced.