Agent Bazaar

io.github.SaylorInnovations由 GitHub 账号 SaylorInnovations 发布v1.0.0更新于 Nov 2, 2026

Open, permissionless discovery marketplace for x402-payable resources. No account or KYC required.

已验证Streamable HTTP可网页运行网页搜索与抓取金融AI 与机器学习

概览

AI 生成的概览

以只读方式访问 Agent Bazaar:一个开放目录,可搜索并查看支持 x402 付费的 API、MCP 工具、数据集和 A2A 智能体卡片。

可以做什么
  • 按关键词或网络、资产、支付方案、payTo、最高价格等条件搜索市场
  • 获取单个资源的完整记录,或只取价格与可接受的支付方式
  • 分页列出全部已收录资源,或列出某个提供方主机发布的全部资源
  • 直接从实时清单列出 Saylor Innovations 已验证的 x402 端点
  • 搜索 A2A 智能体注册表并读取单个智能体卡片
  • 查看目录整体统计,如条目数、商户数和 30 天调用量
适用场景
适合在助手需要为某项任务寻找可付费的 API、工具或数据集时使用,也适合在调用前比较价格与支付网络,或查询其他智能体的 A2A 卡片。它只是发现层,用于购买决策之前,本身不完成支付。
运行要求
远程 streamable HTTP 端点;读取无需账号、API 密钥或环境变量。需要能访问该托管服务的网络。
安装前请注意
目录为无需审核的开放收录,且大部分镜像自另一市场,条目未经审核,描述与质量信号应视为不可信。价格和 payTo 钱包地址来自第三方清单,向所列资源付款会直接结算到该钱包,不经过本服务器。这些工具本身只读取数据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Agent Bazaar,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.SaylorInnovations%2Fagent-bazaar/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "agent-bazaar": {
      "type": "http",
      "url": "https://bazaar.saylorinnovations.com/mcp"
    }
  }
}

README

Agent Bazaar

by Saylor Innovations

An open, permissionless marketplace and discovery layer for AI agents — APIs, MCP tools, datasets, and x402-payable services that autonomous software can find, evaluate, and pay for per request. Repo/package name is still open-x402-bazaar for continuity; the product is Agent Bazaar.

Coinbase's own x402 Bazaar is excellent, but getting listed on it requires a verified Coinbase Developer Platform account, which in turn can require business/KYC verification for some account paths. That's a real barrier for a protocol whose whole point is permissionless, agent-to-agent commerce. This project is an attempt at an alternative: anyone with a valid x402 manifest can list here, with no account and no identity verification at all.

It's built to be wire-compatible with Coinbase's Bazaar discovery API, so any existing x402 client library that already knows how to query the CDP Bazaar can point at this instead with a config change, not a rewrite.

Live at: https://bazaar.saylorinnovations.com

Status

Live at bazaar.saylorinnovations.com, on Cloudflare Pages + D1. Submission, validation, storage, ranked discovery, resource/provider detail pages, and anti-spam basics are all working. The catalog is bootstrapped from a full mirror of Coinbase's public CDP Bazaar plus Saylor Innovations' own real endpoints — see below.

Seeded from Coinbase's Bazaar

Coinbase's discovery API itself requires no API key or account to read — only to list on it. So this project mirrors the whole public catalog (~15,600 resources across ~2,000 hosts, at last import) via scripts/import-cdp-bazaar.mjs, and layers permissionless listing on top:

  • Every mirrored listing is tagged source: 'cdp-mirror' internally.
  • Any owner can POST /submit their own manifest at any time — a self-submitted listing always overwrites the mirrored copy for that host and is tagged source: 'submitted'. The importer never touches a claimed host.
  • Mirrored resources carry Coinbase's own 30-day usage stats (calls30d, uniquePayers30d, lastCalledAt) as a quality field on each resource — a trust signal that matters more here than on a KYC'd catalog, since anyone can list anything.

Re-run the mirror periodically to pick up new resources Coinbase has indexed (safe to re-run — see script header):

bash
npm run seed:cdp-bazaar          # generates + applies against local D1npm run seed:cdp-bazaar:remote   # generates + applies against production D1

Saylor Innovations' own listings

scripts/import-saylor-official.mjs lists Saylor Innovations' real, live x402 endpoints (research/security/data utilities plus Solana on-chain intelligence, all served from saylorinnovations.com) as verified (source: 'submitted') resources — the same trust tier a self-submission gets, seeded directly since Saylor Innovations operates this bazaar. Nothing here is fabricated: pricing, descriptions and accepts[] come from the live /api/services endpoint and the public manifest at saylorinnovations.com/.well-known/x402.json.

bash
npm run seed:saylor-official          # localnpm run seed:saylor-official:remote   # production

How providers actually get paid

x402 payments settle peer-to-peer — agent to payTo wallet — never through this bazaar. So listing here doesn't change how you get paid, it changes how many agents find the endpoint to pay. There's no platform fee on the transaction itself today; the plan is to keep discovery free and, if/when it makes sense, monetize optional things like featured placement or verified-provider tooling rather than taxing the payment path.

How listing works

No signup. POST the URL of your own .well-known/x402.json (or equivalent) manifest:

bash
curl -X POST https://<this-site>/submit \  -H "content-type: application/json" \  -d '{"manifestUrl": "https://yoursite.com/.well-known/x402.json"}'

The manifest is fetched (over HTTPS, with SSRF guards — private/internal addresses are refused before any request is made), validated, and any resource with a populated accepts[] (scheme + network + payTo) is indexed. Re-submitting the same manifest URL refreshes your listing and claims the host if it was previously only in the Coinbase mirror. Submissions are rate-limited per IP (20/hour, 60/day) — every attempt counts, not just successful ones, so failing probes can't dodge the limit.

Registering an A2A agent

Same model, different shape — an A2A agent card has skills[] instead of accepts[] and no inherent payment model, so it lives in its own agent_cards table rather than being forced into the resources shape:

bash
curl -X POST https://<this-site>/submit-agent \  -H "content-type: application/json" \  -d '{"agentCardUrl": "https://youragent.example.com/.well-known/agent-card.json"}'

Requires at minimum a name; skills[], provider, protocolVersion and documentationUrl are stored when present. Same SSRF guards, same rate limiting, same no-account model.

Discovery API (agent-facing)

Mirrors the field names and shape of Coinbase's CDP Bazaar API, plus an additive quality field and a stats endpoint:

EndpointPurpose
GET /discovery/search?query=&network=&asset=&scheme=&payTo=&urlSubstring=&maxUsdPrice=&limit=Keyword/filter search. Text queries rank by relevance (FTS5 bm25); filter-only queries rank by 30-day call volume
GET /discovery/resources?limit=&offset=&sort=Paginated listing of every indexed resource. sort=recent for newest-first, default ranks by 30-day call volume
GET /discovery/merchant?payTo=<address>All resources that pay a specific address
GET /discovery/facets?limit=Compact counts for available networks, assets, schemes, resource types, providers, price bands, liveness and trust states — useful before choosing search filters
GET /discovery/stats?full=Catalog totals: listings, resources, accepts, merchants, network count, calls. full=1 adds the per-network/per-source breakdown — a full table scan, so it's opt-in, not computed by default
GET /resources/{slug}.jsonFull machine-readable record for a single resource
GET /discovery/agents?query=&limit=&offset=Search/list the A2A agent registry (other agents' cards, not Agent Bazaar's own)
GET /agents/{slug}.jsonFull A2A agent card as submitted
GET /discovery/featured?limit=Currently-featured resources (paid placement, see below)
GET /feature?slug=&days={7,30,90}x402-payable: pay Agent Bazaar directly to feature an already-listed resource. See "Featured placement" below

No API key required for any read endpoint — same as Coinbase's.

Agent-facing docs: /llms.txt · /llms-full.txt · /openapi.json · /agents.json · /.well-known/agent-card.json (A2A).

Human-facing pages

Every resource has a permanent, crawlable, server-rendered URL — not a client-side-only modal — with a machine-readable JSON twin alongside it:

PagePurpose
/resources/{slug}Resource detail: description, pricing, accepts[], schema, curl/JS/Python examples
/providers/{host}Every resource published by one provider
/agentsQuickstart for connecting an agent (discover → inspect → pay → execute → verify), plus the registered-agents directory
/agents/{slug}A2A agent detail page — skills, provider, protocol version, card URL
/publishHow to list a resource as a seller
/docsWhat x402/MCP/A2A are, how agent payments work, self-hosting
/guides, /guides/{slug}11 in-depth, code-backed guides — full-length versions of the /docs FAQ answers, plus provider/agent-builder how-tos. .json twin per guide
/categories, /categories/{type}Browse by resource type (populated as providers set one — sparse for the mirrored bulk of the catalog, which doesn't). .json twin (/categories/{type}.json?limit=) returns the whole collection as one array — for an agent that wants "the entire guide library" in one call instead of walking cards one at a time
/networks, /networks/{network}Browse by CAIP-2 network — populated for every resource, since it comes from accepts[]
/protocols, /protocols/{x402,mcp,a2a}What each protocol is and how Agent Bazaar uses it, with live stats
/mcpGET: info page. POST: a real MCP server (JSON-RPC/Streamable HTTP) over the same catalog — search_resources, get_resource, get_pricing, discover_provider, list_resources, get_stats

Listed in

Agent Bazaar's MCP server is published to the official MCP Registry as io.github.SaylorInnovations/agent-bazaar — the canonical registry other aggregators (Glama, PulseMCP) pull from. server.json at the repo root is the source of truth; to re-publish after a change, bump its version and run:

bash
mcp-publisher login github   # once per sessionmcp-publisher publish

Also listed (as a marketplace, not an MCP server specifically) in awesome-x402, awesome-mcp-servers (Aggregators), and gold-402 (Marketplaces & Discovery).

Featured placement

Listing is, and always will be, free — Agent Bazaar never takes a cut of any resource's own accepts[] payment, including the ~15,600 mirrored resources it didn't author. The one thing it does sell directly is placement: a provider can pay Agent Bazaar itself (not the resource's payTo) to put an already-listed resource in the homepage's Featured Resources row and flag it with a featured badge on its resource and provider pages, for 7/30/90 days ($2/$6/$15). It's paid the same way every resource here works — GET /feature?slug=&days= returns a 402 with accepts[]; pay one, retry, get a featuredUntil timestamp back. See /publish#feature for the full walkthrough. Implemented with Saylor Innovations' own solana-x402 library — see Architecture below.

Verified agent skills

resource_type: "Skill" — downloadable, zip-bundled skills (a SKILL.md plus any supporting files/scripts), listed under Agent Bazaar's own host (bazaar.saylorinnovations.com) as a first-party, verified provider. Source lives in skills/; scripts/import-skills.mjs builds the ZIPs and catalog SQL. The 23 free skills cover agent fundamentals, reliable workflows, Markdown vault continuity, evidence-based prospect research, and Kentucky Lottery results. Empty accepts[] deliberately means free; the importer writes directly to D1 rather than using POST /submit, whose manifest validation requires non-empty accepts[]. Paid skills can use normal x402 accepts[].

Architecture

  • Runtime: Cloudflare Pages Functions (Workers runtime).
  • Storage: D1 (SQLite), normalized across listings / resources / resource_accepts, plus an FTS5 virtual table for real keyword search — not just JS-array filtering. submission_log backs per-IP rate limiting.
  • Ingestion: pull-based. Sellers submit a manifest URL; nothing is pushed. Re-submitting the same manifest URL deletes and re-inserts its resources (a full refresh, not a merge). The Coinbase-mirror importer (scripts/import-cdp-bazaar.mjs) is the one exception — a standalone Node script that fetches Coinbase's public catalog and writes SQL directly, run out-of-band from the Workers request path.
  • One runtime dependency — solana-x402 (Saylor Innovations' own x402 resource-server library, pinned to a commit SHA via a github: install), used only by functions/feature.js for payment issuance/verification on the paid-placement endpoint. Everything else has zero runtime dependencies; wrangler remains dev-only, for local D1/Pages tooling and the mirror importer.

Local development

bash
npm installnpm run db:init                # applies schema.sql to a local D1 databasenpm run seed:saylor-official   # Saylor Innovations' own real, verified endpointsnpm run seed:cdp-bazaar        # optional: mirror Coinbase's public Bazaar catalog into itnpm run check:liveness          # optional: probe owner-submitted resources, flag any that don't respondnpm run dev                     # wrangler pages dev, with the D1 binding wired up

If you already have a deployed D1 database predating later schema changes, apply the additive migrations in order instead of re-running schema.sql: npm run db:migrate:remote, then :0003, :0004, :0005, :0006, :0007.

/feature requires a FEATURE_SECRET Pages secret (HMAC-signs its payment quote sessions) — set it with wrangler pages secret put FEATURE_SECRET. Without one it falls back to an insecure dev-only value, which is fine for wrangler pages dev but must never reach production. An optional FEATURE_RPC_URL overrides the default public, rate-limited Solana RPC endpoint.

Keeping it fresh (self-hosting)

seed:cdp-bazaar:remote, seed:saylor-official:remote and check:liveness:remote are just npm scripts — run them on whatever scheduler you already have (cron, GitHub Actions, a Cloudflare Worker with its own Cron Trigger calling out to a small script, etc). They're deliberately plain Node scripts with no dependency on any particular scheduling platform.

Security notes

POST /submit fetches a URL the caller supplies — a classic SSRF vector if unguarded. Before any request is made, the hostname is resolved and rejected if it points at loopback, RFC1918 private ranges, or link-local space (including the 169.254.169.254 cloud-metadata address). Redirects are not followed automatically. Manifest size and fetch time are capped.

D1 cost notes

D1's free tier caps daily row reads. GET /discovery/stats (and listNetworks/listCategories) do an unfiltered GROUP BY over resource_accepts — an aggregate with no WHERE clause reads every row in the table no matter how well-indexed it is, since there's nothing to prune. getStats() is cheap by default (totals only, including a COUNT(DISTINCT network) that rides along for free in the same query) and only pays for the full per-network/per-source breakdown when a caller explicitly asks via ?full=1 — the homepage and /protocols/x402 used to fetch the full breakdown on every casual page view just to display a count, which alone was enough to exhaust the free tier's daily cap during heavy testing. If you add a new page that needs byNetwork/bySource, request it explicitly rather than defaulting to full=true everywhere.

Not yet built (roadmap)

  • Periodic liveness checks — done. scripts/check-liveness.mjs probes every owner-submitted resource (not the mirrored ones — Coinbase already crawls those) and marks it is_live: true/false; a confirmed-down resource gets a visible "not responding" badge on its card, detail page and provider page. It doesn't yet auto-prune or re-fetch changed payment addresses — a down resource stays listed, just flagged.
  • Rolling reliability signal — done. Each liveness check now also inserts into liveness_checks, and the resource row gets a precomputed rolling window (last 10 checks) — liveness.reliability: {checks, live} in the JSON, a "N/M uptime" badge in the UI. Only appears for owner-submitted resources (the only ones actually probed); null means never checked, distinct from a bad score.
  • Example response shape — done. Any resource with an output_schema now also gets an exampleResponse in its JSON (and an "Example shape" block on its page), synthesized from the schema itself — real example/default/enum values where the schema provides them, type-appropriate placeholders otherwise. Clearly not a captured live response; there for an agent to see the shape before paying.
  • Semantic search. Current search is keyword/substring (FTS5) only, unlike Coinbase's hybrid text+semantic search.
  • Scheduled auto-mirroring — done, via a daily scheduled job that runs both importers and the liveness check against production. (Implemented as a scheduled Claude Code cloud routine rather than a Cloudflare Cron Trigger — Pages Functions don't support cron triggers the way standalone Workers do — so this is operational, not something a fork of this repo gets automatically; see the "Keeping it fresh" note below if self-hosting.)
  • Third-party MCP tool directory. /mcp is now a real, working MCP server over this catalog (see above), but it doesn't yet proxy or list other MCP servers with their own detail pages the way /resources/{slug} does for x402 resources.
  • A2A agent registry — done. /discovery/agents, POST /submit-agent, and /agents/{slug} list a directory of other agents' cards (separate from /.well-known/agent-card.json, which is Agent Bazaar's own). Not yet built within it: liveness checks on registered agents (only resources get probed today), and no reputation/trust signal beyond "registered."
  • Automated provider ingestion. Publishing today is manifest-URL only; importing directly from an OpenAPI document, MCP schema, or Git repo is not yet built.
  • Guides/content library — done. /guides has 11 in-depth, code-backed guides (src/guides.js) covering x402, MCP, A2A, agentic commerce, and provider/agent-builder how-tos — the full-length treatment of what /docs only summarizes. Each has a machine-readable .json twin. More can be added anytime; nothing else needs to change beyond appending to GUIDES.
  • Trust badges beyond "verified owner." Endpoint/schema verification with live uptime checks isn't built; today "verified" means only "owner proved control via POST /submit."
  • Federation with the x402 Foundation's discovery working group (x402-foundation/wg-domain-discovery) — the goal is to align with an open standard rather than become a second walled garden.

License

MIT — see LICENSE.

来源:README.md,提交 9f16793

工具

9

search_resources

Search the marketplace by keyword and/or filters (network, asset, scheme, payTo, maxUsdPrice). Text queries rank by relevance; filter-only queries rank by 30-day call volume.

输入参数assetlimitpayToqueryschemenetworkmaxUsdPrice

get_resource

Fetch one resource's full record by slug or numeric id: description, accepts[], output schema, quality signal, and agent-first metadata where the provider supplied it.

输入参数slug必填

get_pricing

Get just the price/accepts[] for a resource, without the full record — cheaper for an agent that only needs to decide whether it can afford something.

输入参数slug必填

discover_provider

List every resource published by a given provider host.

输入参数host必填

list_resources

Paginated listing of every indexed resource, ranked by 30-day call volume (or recency with sort="recent").

输入参数sortlimitoffset

list_saylor_official

List verified Saylor Innovations x402 endpoints directly from the live Saylor manifest. Does not depend on the D1 catalog, so it keeps working during catalog quota exhaustion. Supports query, family, tag, network, asset, payTo, maxUsdPrice, limit and offset filters.

输入参数tagassetlimitpayToqueryfamilyoffsetnetworkmaxUsdPrice

get_stats

Catalog-wide totals: listings, resources, accepts, merchants, 30-day call volume, network/source breakdown.

无需输入参数。

discover_agents

Search or list the A2A agent registry — other agents’ cards (name, skills, provider, protocol version), not Agent Bazaar’s own.

输入参数limitquery

get_agent

Fetch one registered agent's full card by slug or numeric id.

输入参数slug必填

版本历史

1
  1. v1.0.0最新Sep 20, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分