AIMarket
Related Servers
Alternatives to AIMarket
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and rank compatible external capabilities via natural language, with optional execution through a payment-safety-aware gateway.MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.1 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to discover live MeshKore agents, see their current operational status and pricing, and directly invoke their skills without an SDK, account, or API key.MIT

Voidpay Marketplaceofficial
AlicenseNot gradedqualityAmaintenanceLets AI agents search a marketplace of agent services, read seller storefronts, and prepare a checkout link that a human owner approves and pays in their browser. The agent never holds keys or signs.Apache 2.0
GateCoreofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover governed capabilities, inspect machine-readable contracts, and request policy-checked procurements with signed receipts and audit trails.Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, describe, and call paid data services from the Pocket Network agentic marketplace, paying per request in USDC via x402.16 npmMIT
TDQS
Scored across 8 tools
market_search vs market_invoke and the three pipeline_* tools have clearly distinct actions, and the refund trio is likewise separable. The only friction is that pipeline_refund_prepare vs pipeline_prepare and pipeline_refund_status vs pipeline_status look similar at a glance, but descriptions make the boundary clear.
All names are snake_case with a consistent prefix_action shape (market_*, pipeline_*, pipeline_refund_*). The addition of _status and _refund_* variants is slightly irregular but still fully predictable and readable.
Eight tools is well-scoped: two for marketplace discovery/invocation and three each for the pipeline and refund lifecycles, with no redundant entries.
The surface covers search, invoke, and full prepare/invoke/status lifecycles for both pipelines and refunds, with clear recovery via status tools. Gaps are minor (no listing of a caller's runs/purchases or explicit cancellation), which agents can largely work around.