Bazaar Visibility Snapshot

Name: Bazaar Visibility Snapshot
Price: 0.01 USDC

Live 0.01 USDC

Give the machine one HTTPS x402 resource identifier, one merchant payTo address, and 1–3 buyer-job search strings. After payment it reports whether that exact resource is present in Coinbase Bazaar merchant discovery, the public metadata Coinbase currently shows, and the 1-indexed position in the first 20 search results. It does not score quality, recommend changes, or fetch the resource.

PURPOSE

Plain-English job

Sellers often need a factual look at whether a paid resource is currently listed in Coinbase Bazaar and whether buyer-language searches surface it in the first 20 results. This machine observes the public CDP discovery APIs after settlement. It is a point-in-time snapshot, not a ranking product and not a guarantee of future visibility.

WHEN TO CALL

Job-shaped selection

Call when you need a point-in-time factual observation of whether one x402 resource appears in Coinbase Bazaar merchant discovery and where it sits in the first 20 results for 1–3 buyer-supplied job-language searches. Not a trust score, SEO score, rank beyond the observed top 20, or remediation recommendation. Sibling first-party machines are listed on GET /v1/catalog.

INPUT

Exact JSON object

Required resource (absolute HTTPS URL identifier, never fetched), pay_to (0x-prefixed 20-byte EVM address), and queries (1–3 buyer-job strings, each 2–400 characters). Fragments, credentials, non-HTTPS, non-443 ports, extra fields, and empty queries are rejected before payment.

{
  "resource": "https://api.example.com/v1/paid",
  "pay_to": "0x0000000000000000000000000000000000000001",
  "queries": ["example paid json api"]
}

OUTPUT

Factual structured JSON

Merchant presence is FOUND, NOT_FOUND when one page proves absence, or UNKNOWN_TRUNCATED when the first page cannot prove absence. Search visibility is IN_TOP_20 with a 1-indexed position, or NOT_IN_TOP_20 with position null. Missing optional Coinbase fields are omitted or null. No score is invented.

HOW DATA IS PROCESSED

Terms-relevant facts

AFTER SETTLEMENTCoinbase discovery is called only after successful x402 settlement. At most one merchant lookup and three searches.
PUBLIC DISCOVERYCalls go only to https://api.cdp.coinbase.com/platform/v2/x402/discovery/ GET merchant and GET search. No API key is introduced.
NO RESOURCE FETCHThe submitted resource URL is an identifier. It is never fetched or proxied.
GLOBAL SEARCHSemantic search is not filtered by payTo or urlSubstring, so the observed top-20 position is global.
NO SCOREThis is factual evidence. It is not a trust score, quality score, SEO score, or remediation recommendation.

LIMITATIONS

Known bounds

POINT IN TIMEBazaar ranking and merchant pages can change. This is not proof of future visibility.
TOP 20 ONLYAbsence means not in the returned first 20, not rank 21+.
ONE MERCHANT PAGEMerchant lookup uses limit 20 offset 0. A truncated first page cannot prove absence.
AVAILABLEVM05 is a bounded pay-per-call product. This page does not start a payment.

CONTRACT

Intended routes

Public API origin:

POST https://api.agentmercantile.com/v1/bazaar-visibility

GET https://api.agentmercantile.com/openapi.json

This page does not start a payment. Public contact: contact@agentmercantile.com.

Developer / API page Open live catalog