gatewards_call_api
Make a paid API call through Gatewards. Payment is automatic — if the API returns 402, USDC is settled on-chain and the request retries with a receipt.
LABSCO SUMMARY
The spend cap sits in the request path, so an over-budget call is refused rather than recorded.
That is the difference between a budget and a report, and it is the reason to choose proxy mode by default — you also get response caching and cross-agent deduplication, so two agents asking the same question pay once. Self-custody is the other half: the agent signs its own USDC payments and the key stays on your machine, which is worth the extra setup only when you actually need to pay per call on-chain.
What it is
A client for Gatewards, a routing layer for paid APIs. It finds services on the marketplace, makes the call, and settles payment — either through the gateway with a budget enforced, or on-chain from the agent's own wallet.
What you get
- Paid API services on the marketplace, with names, descriptions, endpoints and prices, searchable — gatewards_discover_services
- A GET or POST call made through the layer, returning status, data and what it cost; if the API answers 402, USDC settles on-chain and the request retries carrying a receipt — gatewards_call_api
- Today's spend, the remaining budget and active subscriptions — gatewards_check_budget
- Prepaid credit plans listed for a service, at a fixed USDC price — gatewards_get_plans
- A credit bundle bought for a service, in proxy mode — gatewards_subscribe
- Two modes from the same server: proxy, which adds budget enforcement, response caching and cross-agent deduplication, and x402 self-custody, where the agent signs payments itself and the keys never leave the machine
Requirements
For proxy mode, an agent API key from the Gatewards dashboard — pass it as --api-key or GATEWARDS_API_KEY — and the gateway URL, which defaults to a local address and should be pointed at https://api.gatewards.com for the hosted one. Self-custody mode instead takes --private-key with an RPC URL and a USDC contract address. Run npx @gatewards/mcp-server; the server starts without a key but cannot reach the gateway until it has one.
Setup effort
One command plus a key — npx @gatewards/mcp-server --api-key=<YOUR_API_KEY> --gateway=https://api.gatewards.com, then supply credentials
USE CASES
01
Finding an API for something your agent cannot do
Search the marketplace and compare endpoints and prices before committing to one.
02
Calling a paid API without wiring up billing first
Make the call through the layer and let the payment settle behind it, with the cost returned alongside the data.
03
Keeping an autonomous agent from overspending
Set the budget on the agent key and read the remaining balance as it works.
04
Bringing down the cost of a service you call constantly
Look at its prepaid plans and buy the credit bundle instead of paying per call.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
gatewards_check_budget
Check your current spending budget. Returns daily spend and remaining budget.
gatewards_discover_services
Discover available paid API services on the Gatewards marketplace. Returns service names, descriptions, endpoints, and prices.
gatewards_get_plans
List available subscription plans. Plans offer prepaid credits at a fixed USDC price.
gatewards_subscribe
Subscribe to a credit plan. Purchases a bundle of credits for a service.
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. gatewards_subscribe works only in proxy mode (--api-key), not with --private-key. The gateway URL defaults to http://localhost:3001; point --gateway or GATEWARDS_GATEWAY_URL at https://api.gatewards.com or every tool reaches nothing.
Requires
- npx on PATH
- GATEWARDS_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @gatewards/mcp-server --api-key=<YOUR_API_KEY> --gateway=https://api.gatewards.comMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gatewards": {
"command": "npx",
"args": [
"@gatewards/mcp-server",
"--api-key=<YOUR_API_KEY>",
"--gateway=https://api.gatewards.com"
]
}
}
}The --api-key flag in this configuration is GATEWARDS_API_KEY (flags win over environment variables): <YOUR_API_KEY> is the agent key from your Gatewards dashboard. You can also drop the flag and set GATEWARDS_API_KEY instead.
