Proxygate MCP server

Search the Proxygate marketplace for APIs an agent can buy. Optional free-text query (semantic + keyword search, same as the public catalog), category filter, and result limit. Returns each API with its listing id, name, service slug (for call_api), category, buyer price per request (in micro-USDC), listing type, trust/rating hints, and a capped endpoint preview (endpoint_count = full total). No authentication required.

Get per-service pricing for Proxygate APIs. Optional single-service filter (exact service slug — take it from browse_apis). Returns the per-request USDC price plus per-input/output token USDC prices (null for per-request services). No authentication required.

Get the authenticated wallet's Proxygate balance breakdown: total balance, available (spendable now), and pending settlement, all in micro-USDC. Top up via the x402 rail (GET /v1/x402/topup). Requires authentication.

List the authenticated wallet's recent Proxygate API requests (newest first), with service, path, HTTP status, cost in micro-USDC, and timestamp. Cursor-paginated. Requires authentication.

Rate a seller after buying from one of their listings. Give the listing_id and a thumbs verdict (score: true = positive). Proxygate rates the wallet's most recent successful request to that listing (within the last 24h). Rating only, no payment. Requires authentication.

Execute a billed API call through Proxygate, end-to-end. Give a listing_id from browse_apis, the endpoint path, and the HTTP method; the service slug is optional (derived from the listing). Optional query/headers/body pass through; set header x-proxygate-shield to off/monitor/strict to control response scanning. Proxygate reserves balance, handles upstream authentication for you, forwards the request, and charges your wallet. Returns the upstream status, headers, and body plus the amount charged (cost_micro_usdc), a signed receipt, and a request_id. Spends from your balance — requires authentication with the mcp:trade (or proxy) scope.

Inspect one endpoint of a listing before spending: parameters (name, location, required, type), request body schema, and response schemas, resolved one $ref level from the listing's uploaded docs. Give the listing_id from browse_apis plus the endpoint method and path (for GraphQL listings: the operation name as path). No authentication required.