API Tools
proxygate.ai
Manages Proxygate API marketplace interactions including browsing, purchasing, and usage tracking.
ENDPOINT 1
https://gateway.proxygate.ai/mcp
MCP server metadata
- Name
- proxygate
- Version
- 1
Proxygate is a curated API marketplace for agents: one identity, one prepaid USDC balance, metered per call with signed receipts. Buying data is two steps: 1. browse_apis with a free-text q (semantic + keyword search) to find a listing. Each result carries the listing id, the service slug, a capped PREVIEW of callable endpoints (endpoint_count holds the full total; drill into one with describe_endpoint), and the buyer price per request in micro-USDC (1 USDC = 1,000,000 micro-USDC). 2. call_api with that listing_id, the endpoint path, and the method. The service slug is optional (derived from the listing). The response includes the upstream body, the exact amount charged, a signed receipt, and a request_id. Optional steps: describe_endpoint(listing_id, method, path) shows an endpoint's parameters and schemas before you spend; check_balance shows what you can spend; get_usage lists past calls; rate_seller(listing_id, score) rates a seller you bought from within 24h. Funding: top up your balance over the x402 rail. GET /v1/x402/topup returns a 402 challenge with a ready-to-sign Solana depositTransaction; sign and submit it, then confirm. When gasless mode is enabled the platform pays all SOL (tx fees and vault rent) and a small USDC fee applies, so buyers need only USDC, never SOL. Notes: prices shown by browse_apis/get_pricing are per-request buyer prices; dynamic security surcharges may apply when response scanning (shield) is active. Pass the header x-proxygate-shield: off in call_api headers to opt out of response scanning, or strict to block flagged responses. call_api spends from your balance and requires the mcp:trade or proxy scope.
Known tools 7
check_balanceGet the authenticated wallet's Proxygate balance breakdown: total balance, available (spendable now), and pending settlement, all in micro-USDC.
Inferred read-onlyget_usageList the authenticated wallet's recent Proxygate API requests (newest first), with service, path, HTTP status, cost in micro-USDC, and timestamp.
Inferred read-onlydescribe_endpointInspect 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.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.proxygate]
url = "https://gateway.proxygate.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"proxygate": {
"type": "http",
"url": "https://gateway.proxygate.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: proxygate
Remote MCP URL: https://gateway.proxygate.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"proxygate": {
"url": "https://gateway.proxygate.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"proxygate": {
"type": "http",
"url": "https://gateway.proxygate.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "proxygate",
"transport": "streamable-http",
"url": "https://gateway.proxygate.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.