AI agent discovery, marketplaces and offers

On this page

Chapter 11 of The Hitchhiker's Guide to the Agentic Economy

Report hub · Previous: evaluation, observability and security · In this chapter: six discovery gates · market map · AE-JOB-001 · Discovery and Offer Record · Next: commerce protocols and checkout

The transition from technical discovery to commercial quote

Before an autonomous agent can purchase a service, it must locate a candidate endpoint, verify compatibility, and obtain a binding, time-stamped price.

In current developer tooling, discovery is often treated as a simple database query against a public index. However, finding a directory listing is merely the beginning of the commercial qualification funnel. A registry listing indicates that an endpoint exists. An actionable offer establishes a legally bounded, priced proposition that an enterprise buyer can evaluate, authorize, and hold a counterparty accountable to.

The gap between technical listings and actionable offers is substantial. Marketplaces like x402 Bazaar index over 23,000 payment-gated resources, while the Model Context Protocol (MCP) Registry, A2A Agent Cards, and Agentic Resource Discovery (ARD) specifications publish thousands of server names, endpoints, tool schemas, and authentication methods. Yet virtually none of these raw catalog entries contain current tax-inclusive pricing for a specific corporate buyer, verifiable legal counterparty identities, explicit deliverable acceptance tests, or contractual dispute remedies.

Transforming an unverified discovery record into a binding commercial transaction requires traversing six sequential qualification gates: visibility, reachability, buyer eligibility, version freshness, commercial suitability, and counterparty trust.

Key Takeaways

• A public registry, enterprise registry, marketplace, app store and merchant catalogue make different promises. Choose the surface by required evidence, not listing count.
• Listing, endpoint, seller and payee identities may differ. Namespace verification establishes control or provenance, not a solvent counterparty or good result.
• Discovery metadata is a dated lead. Recheck the live offer, buyer entitlement and terms before an agent requests a quote.
• A count, score, health badge, call metric or promoted placement needs a named denominator. None measures accepted jobs or repeat customers by itself.
• Preserve the decision in the Commercial Job Record so later order, payment, delivery and acceptance records reference the candidate and quote.

Discovery requirements across operational risk profiles

Enterprise procurement does not ask which registry contains the largest inventory. It establishes what evidence is legally and operationally required before an agent is permitted to request a quote or commit capital:

Consequence tier	Operational discovery policy	Minimum verification evidence required
Supervised internal research	Public catalogs or internal registries provide initial candidates for human review	Pinned provider name, endpoint URL, input/output JSON Schemas, active reachability ping, and designated owner
Metered data API ingestion	Services must expose deterministic unit pricing, currency, and hard spend caps	Buyer plan eligibility, cryptographic quote timestamp, overage fee schedule, rate limits, and failure refund policy
Client-facing deliverable	Candidates must define the final business deliverable rather than exposing raw tools	Explicit acceptance criteria, data freshness boundaries, delivery turnaround SLA, and identified corporate counterparty
Remote sub-agent delegation	Registries serve as initial routing indexes; multi-hop security boundaries apply	Provider legal identity, workload instance verification, mTLS/OAuth path, data processing regions, and dispute forum
Merchant physical purchase	Merchant catalogs must return real-time inventory and shipping constraints	Stock availability, landed tax and duties, buyer eligibility, return policies, and formal checkout hand-off
Regulated corporate transaction	Mandatory human sign-off on both the vendor candidate and binding quote	Exportable audit records, data residency certifications, corporate KYB verification, and contractual indemnification

Public registries are valuable for exploratory development. However, relying on an open directory for unattended corporate transactions creates unacceptable balance-sheet exposure unless counterparty identity, pricing, and error remediation are verified independently.

Staged commercial adoption gates

Organizations govern autonomous purchasing through four progressive operational stages:

Stage	Permitted agent actions	Explicitly prohibited actions	Mandatory governance requirement
1. Explore	Search directories, inspect metadata, request non-binding price quotes without sensitive data	Accepting commercial terms, presenting payment credentials, creating binding commitments	Business owner logs candidate; verifies identity and baseline reachability
2. Attended pilot	Execute a single bounded, reversible transaction under manual human approval	Automated retries on failed payments; inferring acceptance from HTTP status codes	Business owner approves transaction; procurement vets vendor; finance owns payment
3. Bounded delegation	Repeat pre-approved transactions within strict supplier, action, time, and budget ceilings	Altering vendors, widening scope, changing payment rails, or waiving dispute remedies	Enterprise sponsor signs off; idempotency keys enforced; ambiguous writes halt execution
4. Recurring supplier trade	Transact continuously under established enterprise contracts and negotiated master terms	Continuing execution after master service agreements, budget caps, or data approvals expire	Procurement, legal, and finance link accepted deliverables directly to three-way matched ERP invoices

Pilot exit criteria are unambiguous: the enterprise must successfully reconstruct a standard transaction alongside its failure paths: price changes, dropped connections, duplicate requests, and rejected deliveries. Workflows expand only within the parameters that passed testing.

Consumer protection and commercial transparency gates

Before authorizing an autonomous agent to execute transactions affecting consumers or committing unattended capital, systems must enforce seven disclosure and compliance gates:

Governance gate	Required buyer-visible evidence	Mandatory blocking condition
Algorithmic steering	Explicit disclosure of ranking criteria, affiliate commissions, and alternative vendor options	Sponsored placement or paid steering is concealed, or viable alternatives are artificially suppressed
Counterparty identity	Legal vendor entity, Merchant of Record (MoR), payee identity, support desk, and dispute forum	The underlying legal seller, merchant entity, or formal complaint channel cannot be identified
Total commitment	Itemized product/service cost, platform fees, statutory taxes, currency, and cancellation rules	Total financial liability is uncapped, or critical renewal/cancellation terms are concealed
Authority enforcement	Designated principal, delegate identity, authorized budget cap, and expiration timestamp	Mandate exists only as natural-language text and is not enforced by a deterministic policy engine
Abuse & fraud controls	Automated supplier screening, KYB/sanctions validation, and transaction velocity limits	Vendor fails identity verification, account behavior deviates from normal patterns, or alerts lack owners
Data privacy & access	Disclosed data elements, processing jurisdiction, retention limits, and sub-processor lists	Sensitive corporate or customer data would cross unauthorized geographic or corporate perimeters
Portability & exit	Exportable transaction logs, receipts, and acceptance records; instant credential revocation	The enterprise cannot export complete audit trails or exit without abandoning unresolved financial obligations

The Australian Taxation Office maintains the eInvoicing Ready product register, certifying that software products satisfy technical data standards for Peppol eInvoicing. This certification confirms technical document compatibility; it does not endorse vendor commercial solvency, service quality, or payment reliability. Enterprise discovery requires evaluating labels with identical precision.

The six qualification gates of commercial discovery

A candidate capability moves from an unverified directory listing to an actionable commercial offer across six gates:

1. Visible     -> Candidate record published in accessible registry, catalog, or manifest
2. Reachable   -> Protocol endpoint, package, and authentication resolve for this buyer
3. Eligible    -> Account tier, geographic market, network asset, and compliance checks pass
4. Available   -> Version history, API health, and endpoint status verified current
5. Suitable    -> Parameter schemas, latency targets, and commercial pricing fit task scope
6. Trusted     -> Identifiable counterparty, contractual terms, and dispute remedies confirmed

• Agent registry: A metadata directory indexing agent capabilities, endpoints, and schemas.
• Service marketplace: A commercial platform adding pricing tiers, checkout workflows, and developer payouts around API services.
• Capability card: A machine-readable document describing an agent's technical interface and modalities (e.g., A2A Agent Card).
• Actionable offer: A time-stamped, binding commercial proposition specifying scope, pricing, delivery deadlines, and dispute remedies that an enterprise can evaluate and order.

1. Visible: publication in a discoverable index

Publication confirms that an endpoint or metadata record is indexed. A search result, server.json file, A2A Agent Card, or UCP profile proves discoverability; it does not confirm that the index is comprehensive, up to date, or applicable to a specific corporate buyer. The MCP Registry, A2A Agent Cards, and Agentic Resource Discovery (ARD) establish technical publication, not commercial availability.

2. Reachable: resolving connectivity for a specific buyer

Reachability requires that network routing, protocol handshakes, and transport authentication resolve successfully for the specific buyer. The Google Cloud Agent Registry and Gemini Enterprise A2A guide decouple discovery permissions from runtime invocation permissions. An endpoint can be publicly indexed while remaining inaccessible to a specific corporate VPC or firewall configuration.

3. Eligible: meeting jurisdictional and platform constraints

Eligibility verifies that the buyer satisfies regulatory, commercial, and geographical criteria: corporate account tiers, tenant permissions, regional data residency, KYC verification, and shipping destinations. Shopify's UCP catalog exposes explicit parameters like ships_to and available. Google’s Merchant Center UCP documentation documents pilot agent checkout restricted to US merchants. While Microsoft regional availability includes Australia, specific Copilot Store agents remain restricted by tenant licensing.

4. Available: validating freshness and active maintenance

Freshness is an active operational verification, not a static timestamp. Platforms enforce different refresh intervals: MCP registry aggregators scrape periodically (MCP aggregator guidance); directories like Glama run scheduled probes while disclaiming real-time accuracy (Glama methodology; terms); RapidAPI allows deprecated API versions to persist for existing subscribers (RapidAPI versioning); and Coinbase CDP documents automated health checks and removal criteria for x402 Bazaar (Coinbase CDP seller documentation). There is no global freshness clock; client agents must verify that candidate endpoints are actively maintained.

5. Commercially suitable: aligning capability and pricing

Capability alignment confirms that input schemas, output structures, and latency profiles satisfy the task. Commercial alignment verifies currency, pricing units, spend ceilings, overage tiers, and acceptance criteria. Developer platforms like Shopify, RapidAPI, Apify, and Coinbase Developer Platform expose catalog pricing metadata, but converting metadata into an enterprise transaction requires a binding quote covering statutory taxes and support terms.

6. Sufficiently trusted: establishing legal accountability

Commercial trust requires identifying the legal entity standing behind the deliverable. Domain namespace control or a verified GitHub organization confirms technical administration; it does not confirm balance-sheet solvency, insurance coverage, or willingness to remediate errors. Apify’s marketplace terms establish direct contracts between the actor creator and user; RapidAPI’s finance documentation details dispute procedures and its 25% marketplace fee; OpenAI’s platform terms place third-party checkout liability directly on the external developer.

The six gates are cumulative. An endpoint can be visible, reachable, and eligible while remaining unquoted or lacking clear dispute recourse. Until all six gates pass, the candidate remains an unverified lead.

The commercial qualification funnel

The progression from discovery to recurring trade follows an operational funnel:

Funnel stage	Definitive milestone event	Authoritative verification evidence	What the stage does not prove
1. Listed	Index, store, or directory returns a named metadata record	Catalog URL, listing ID, publisher namespace, crawl timestamp	Global supply completeness, active demand, or service reachability
2. Reachable	Endpoint, package, or socket resolves under buyer network conditions	Automated non-destructive ping, TLS certificate, protocol version match	Output accuracy, data handling compliance, or commercial terms
3. Eligible	Buyer passes platform, tenant, geographic, KYC, and asset filters	Enterprise IAM entitlement check, merchant policy match, residency validation	Legal contract enforceability, inventory reservation, or export compliance
4. Quoted	Provider returns a binding, time-stamped pricing offer for the specific job	Signed quote payload specifying currency, unit cost, spend cap, and expiration	Order acknowledgement, payment authorization, or deliverable acceptance
5. Ordered	Buyer authorizes offer and seller issues formal order confirmation	Order ID, payment mandate reference, and contractual delivery deadline	Financial settlement, task delivery, or business outcome quality
6. Delivered	Seller transmits final deliverable, file artifact, or database write	Cryptographic artifact hash, delivery receipt, fulfillment webhook	Deliverable accuracy, buyer acceptance, or three-way invoice matching
7. Accepted	Buyer inspects deliverable and formally verifies compliance with scope	Signed acceptance record, inspection sign-off, or rework notice	Broader market demand, long-term vendor reliability, or profitability
8. Repeated	Client issues subsequent task order within a defined observation window	Multi-job customer audit log, renewed spending mandate, volume expansion	Platform popularity metrics or unverified vendor retention marketing

Comparing discovery surfaces

The market contains five distinct discovery architectures, each serving different commercial functions:

Discovery surface	Target buyer and supplier	Information exposed to client	Business model and governance	Primary evidence and critical gap
Public protocol registry	Developers discovering MCP tools and A2A services; open-source publishers	Namespaces, endpoint URLs, transport bindings, tool JSON Schemas, capability cards	Open-source publication, decentralized hosting, community aggregation	MCP Registry, A2A Discovery, ARD; lacks shared schemas for pricing, eligibility, acceptance, and recourse
Enterprise app store / registry	IT administrators and enterprise users; internal developers and vetted partners	Agent identities, enterprise scopes, communication channels, administrative review status	Enterprise platform subscriptions (Google Cloud, Microsoft Entra/Foundry, OpenAI Teams)	Google Agent Registry, Microsoft Copilot Store, OpenAI Terms; publication confirms administrative vetting, not real-time task pricing or performance SLAs
Merchant commerce catalog	Consumer shopping agents; retail merchants and e-commerce platforms	Product schemas, SKU variants, real-time inventory availability, shipping rules, tax calculations	Attributed referral commissions (Shopify Developer Preview documents 0.3% base last-click commission), promoted merchant placement	Universal Commerce Protocol, Shopify Catalog, Shopify Promoted Placement; product listings do not guarantee stock allocation or automated dispute handling
Payment-gated service marketplace	Autonomous agents buying digital services; developers monetizing APIs	Pay-to addresses, accepted crypto assets, HTTP 402 challenge parameters, per-call price ceilings	Per-call micropayments, stablecoin settlement fees, automated facilitator cuts; Coinbase CDP reports >23,000 resources	Coinbase CDP Bazaar, CDP Seller Rules, Apify x402; resource counts reflect publisher registrations, not verified commercial demand; lacks enterprise tax invoicing
API developer marketplace	Engineering teams subscribing to managed APIs; software vendors	Published rate limits, latency percentiles, historical uptime metrics, tiered subscription plans	Monthly subscriptions, tiered usage quotas, overage billing; RapidAPI documents a 25% marketplace fee	RapidAPI Monetization, RapidAPI Consumer Guide, RapidAPI Finance; platform metrics reflect synthetic telemetry, not verified task deliverable quality
Connector directory & aggregator	Developers locating third-party integrations; community indexers	Scraped tool catalogs, community popularity scores, automated uptime probe results	Aggregator advertising, hosted proxy tiers, community sponsorships; directories index tens of thousands of endpoints	Glama MCP, PulseMCP, Smithery; health badges and server counts confirm endpoint reachability, not business task reliability or legal standing

Decoupling directory listings from binding commercial offers

An autonomous agent requires an unbroken chain of commercial identities:

discovery source and listing ID
  -> provider namespace and declared version
  -> endpoint/package/channel identity
  -> seller or merchant identity
  -> buyer eligibility and current offer
  -> order and payment references
  -> delivered artefact or product
  -> acceptance, remedy and repeat relationship

Technical identifiers must not be conflated with commercial counterparties:

• The discovery alias provides directory navigation.
• The network endpoint is the technical URL where bytes are transmitted.
• The legal seller is the corporate entity that enters the commercial contract.
• The payee is the financial account or crypto address receiving funds.

A verified reverse-DNS string or GitHub organization confirms control over a technical namespace; it does not confirm corporate solvency, tax compliance, or legal accountability.

The actionable offer establishes the current commercial terms: exact endpoint version, quote timestamp, purchasing tenant ID, unit of sale, currency, spend ceiling, overage rates, platform fees, expiration deadline, and governing terms of service. An agent must never populate a new commercial quote with stale, cached catalog data.

Marketplace telemetry metrics require similar analytical rigor. Historical uptime percentages, transaction counts, and community popularity stars reflect platform-specific activity. Promoted search placements represent paid advertising. None of these indicators provide an auditable guarantee of business deliverable quality.

Applied walkthrough: procuring AE-JOB-001

The reference competitor briefing (AE-JOB-001) illustrates the qualification process:

Operational task: A Perth corporate advisory firm delegates an autonomous research workflow to gather public data across five named competitors and ten approved web sources, delivering a structured briefing within one business day for mandatory human analyst review.

Acceptance criteria: Explicit competitor names, approved URL domains, designated time zones, and standardized financial metrics. Every extracted figure must cite a primary source URL, retrieval timestamp, and unit of measurement; hallucinated figures constitute immediate failure.

Evaluating candidate discovery surfaces

An agent evaluating candidate capabilities encounters distinct operational trade-offs across surfaces:

1. Specialized scraping platforms (e.g., Apify Store): Actors expose granular usage pricing, container runtimes, and agentic adapters. Apify’s x402 integration supports prepaid USDC spending caps with 14-day expiration windows. The enterprise must verify corporate data handling terms, actor code maintenance history, and output schema consistency.
2. Machine-payment registries (e.g., x402 Bazaar): Endpoints expose direct HTTP 402 challenge parameters, price ceilings, and on-chain pay-to addresses. The service can be called immediately without an enterprise account, but the transaction lacks statutory tax invoicing and contractual dispute channels.
3. API marketplaces (e.g., RapidAPI): Listings document historical latency, availability scores, and tiered monthly subscriptions. Procurement requires establishing corporate account credentials, auditing overage pricing, and accounting for the platform’s 25% marketplace fee.

Traversing the six qualification gates

1. Listed: Capture directory source URL, publisher namespace, endpoint path, and timestamp. Missing pricing is recorded as an explicit unknown; paid search placement is flagged as advertising.
2. Reachable: Execute an automated non-destructive ping, verifying protocol version compatibility and active network connectivity without transmitting sensitive client data.
3. Eligible: Confirm that Australian corporate entities can legally transact, that payment methods are supported, and that vendor data retention policies comply with client confidentiality agreements.
4. Available: Verify that the service version is current, confirming that the provider has not issued deprecation notices or altered parameter schemas within the operational window.
5. Quoted: Request a binding, itemized quote for fulfilling the briefing: pricing units, maximum financial exposure (capped at A$25 for external data), platform fees, delivery turnaround, and tax treatment.
6. Trusted: Verify the legal counterparty, terms of service, support response targets, error remediation procedures, and formal dispute mechanisms.

If an endpoint fails any gate—for instance, if a candidate connector shows a "Last Tested" timestamp from 30 days prior—the system rejects the candidate for live procurement until re-tested. Rejection protects the enterprise from committing capital or sensitive data to abandoned infrastructure.

The Discovery and Offer Record

Production procurement requires capturing an explicit operational record for each evaluated candidate:

Governance category	Operational data required
Counterparty identity	Provider legal name, directory surface, listing ID, canonical endpoint URL, protocol version, and publisher/payee corporate relationship
Technical capability	Supported task scope, input/output JSON Schemas, data access boundaries, and deliverable formatting rules
Version freshness	Publisher release date, last automated probe timestamp, deprecation policy, and active maintenance status
Binding commercial offer	Itemized quote, currency, unit of sale, maximum spend ceiling, overage rates, platform commissions, and expiration timestamp
Eligibility & residency	Buyer corporate tier, IAM role permissions, geographic residency boundaries, and sanctions/KYB screening clearance
Contractual terms & recourse	Legal seller entity, terms of service version, support SLAs, cancellation rules, refund policies, and formal dispute arbitration forum
Platform reputation	Signal type (health badge, historical call volume, unique payers, community reviews), measurement window, and paid placement disclosure
Decision governance	Qualification gate status, identified operational risks, next re-evaluation date, approving manager ID, and downstream order cross-references

Every field maintains an explicit evidence classification: specified, documented, observed, verified, or not established. A missing price field is recorded as unknown; it must never be assumed to be zero.

Retaining denominators in market metrics

Evaluating discovery infrastructure requires matching metrics to the exact populations they measure:

Operational metric	Defensible denominator	Legitimate analytical conclusion	Unsubstantiated extrapolation
Listed count	Total records returned by a named index at a specific timestamp	The specific index contains N published records	Total global market supply, vendor quality, or real customer demand
Reachable count	Listed endpoints passing automated network connectivity pings	N endpoints responded successfully under test conditions	Endpoints are secure, legally compliant, or accessible across all corporate networks
Eligible count	Reachable endpoints meeting explicit corporate policy and geographic rules	N endpoints satisfy policy requirements for a specific buyer	Universal global availability or general regulatory compliance
Quoted count	Eligible candidates that return binding, time-stamped commercial quotes	N providers submitted actionable pricing for this specific task	Order commitment, payment execution, or commercial value
Ordered count	Quoted offers formally approved and acknowledged by merchant systems	N binding commercial purchase orders were formed	Payment settlement finality, successful fulfillment, or client satisfaction
Delivered count	Purchase orders accompanied by verified fulfillment artifacts	N tasks produced a deliverable output	Factual accuracy, client acceptance, or balance-sheet profitability
Accepted count	Delivered artifacts formally verified against contract acceptance criteria	N deliverables fulfilled contractual business requirements	General vendor reliability across unrelated business workflows
Repeat count	Unique corporate buyers issuing subsequent orders within a defined window	N clients demonstrated recurring commercial demand	Broad platform retention claims lacking defined cohort parameters

Published platform metrics—Bazaar transaction counts, RapidAPI success percentiles, Apify store rankings—measure activity within specific software tools. They do not constitute cross-marketplace evidence of accepted economic work.

What current discovery infrastructure establishes

Market evidence confirms substantial development across discovery infrastructure:

• Open protocol registries publish machine-readable schemas, capabilities, and transport endpoints.
• Enterprise application directories enforce administrative review, tenant security, and channel routing.
• Merchant catalogs expose structured e-commerce product inventories and pricing feeds.
• Service and API marketplaces provide callable routes, subscription tiers, and developer billing pipelines.
• Ecosystem aggregators maintain automated health monitors, scraping pipelines, and community directories.

What the market currently lacks is a standardized, cross-platform protocol for generating binding, time-stamped commercial quotes that integrate statutory taxes, buyer-specific entitlements, and legal dispute recourse prior to credential presentation. Connecting technical discovery to binding commercial contracts remains an active integration frontier.

Chapter 12 examines the next commercial transition: the commerce protocols that take an approved offer and convert it into a binding purchase order.

Sources and method

• Primary sources: Developer documentation, terms of service, and public registry interfaces from Model Context Protocol, A2A, Agentic Resource Discovery (ARD), Google Cloud (Agent Registry), Microsoft (Copilot Store), OpenAI, Shopify (UCP), Coinbase Developer Platform (x402 Bazaar), Apify, RapidAPI, Glama, PulseMCP, and the Australian Taxation Office checked as of 13 September 2026.
• Analytical frameworks: The Six Qualification Gates, the eight-stage commercial funnel, and the Discovery and Offer Record are original analytical structures developed to evaluate agentic commerce discovery.
• Evidence boundaries: Provider documentation establishes declared platform features, pricing schedules, and administrative terms. Endpoint reachability, uptime reliability, and deliverable quality require empirical testing on live customer workloads.
• Institutional references: Australian eInvoicing standards and product registers maintained by the Australian Taxation Office provide the regulatory framework for structured business document exchange.
• Editorial record: Published by Agentic Economy, Perth, Western Australia. Updates and corrections are logged via the editorial record.

Back to the report hub · Previous: evaluation, observability and security · Next: commerce protocols and checkout.