A
licenseNot graded
qualityC
maintenanceEnables agents to discover, sample, and pay per call in USDC for live threat intelligence, ZK proof generation, and arbitrage signals via the x402 protocol.
MIT
Apiosk MCP Server
by obcraft
Related Servers
Alternatives to Apiosk MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover, call, and pay for existing HTTP APIs over MCP with x402 paywalls, non-custodial settlement, and no code changes to the backend.171 npm30Apache 2.0
- AlicenseNot gradedqualityBmaintenanceTurns any business API into a paid AI-agent service, enabling agents to discover, call, and pay per request via x402 on X Layer.Apache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to discover x402 payment services and query on-chain-verified settlement volumes per facilitator through the Model Context Protocol.785 npm27MIT
- FlicenseNot gradedqualityBmaintenanceAI Agent Hub is a pay-per-call API platform for AI agents Every call is billed automatically in USDC using the x402 protocol - there is no API key, no account, and no signup. Agents get instant access to data queries, file storage, and ad impressions, paying only for what they actually use. The same tools are also exposed natively over MCP, so any MCP-capable agent can discover and call them-
- AlicenseNot gradedqualityBmaintenanceMarketplace of MCP servers and APIs that agents pay for per call in USDC over x402 on Base; connect anonymously, pay only when you callMIT
TDQS
B3.1/5.0
Scored across 42 tools
Disambiguation2/5
Several tool families have almost identical names: apiosk_wallet_list/apiosk_list_wallets, apiosk_wallet_create/apiosk_create_wallet, and apiosk_wallet_update/apiosk_update_wallet are only distinguishable by reading descriptions to see local vs managed. apiosk_search/discover/explore and apiosk_execute/fetch_paid also have overlapping boundaries, so an agent can easily misselect.
Naming Consistency2/5
Most tools use apiosk_<verb>_<noun>, but local wallet tools reverse this to apiosk_wallet_<verb>, and x402 route tools drop the apiosk_ prefix entirely (publish_x402_route, unpublish_x402_route). Even within wallet naming, apiosk_wallet_list vs apiosk_list_wallets use different word order for the same resource.
Tool Count2/5
42 tools is far above the 25-tool threshold for a single platform and the surface feels padded with onboarding/helper tools and parallel local/managed wallet stacks. A more focused set around discovery, payment, and publishing would be easier to navigate.
Completeness4/5
The set covers the core lifecycle well: discover, inspect, pay/execute, publish/update/deactivate APIs and x402 routes, and manage wallets/API keys. Minor gaps like a direct balance check and a hard delete for x402 routes are workable-around, so it earns a 4 rather than 5.
Maintenance
ActivityActive
ResponsivenessNo issues