x402 Gateway — Inspect Paid API Terms MCP Server
com.scriptmasterlabs/x402-gateway
What this kind of tool is for
- Chain multi-step workflows across the other tools in this directory.
- Run a scheduled or triggered job instead of retyping the same request.
- Have your agent watch a feed, queue, or repo and act on new items.
How to compare servers like this
- Trigger model:
- Understand what starts the automation — a command, a schedule, or an event — before relying on it.
- Blast radius:
- Prefer tools that hand you a review point before an irreversible action runs.
- Chaining cost:
- Each chained step adds a failure point; keep critical paths on the fewest tools.
- Maintenance signal:
- Automations break quietly; a maintained tool is the difference between repair and rediscovery.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the x402 Gateway — Inspect Paid API Terms MCP server?
Discover x402 paid APIs and inspect fresh payment requirements before authorizing spend.
How to install x402 Gateway — Inspect Paid API Terms
Copy-paste configuration for popular MCP clients.
{
"mcpServers": {
"x402-gateway": {
"url": "https://mcp-x402-gitlab-main.onrender.com/mcp"
}
}
}Related MCP servers
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
View repository →Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending.
View repository →Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown.
View repository →SqueezeOS MCP for live machine discovery and x402-paid USDC APIs on Base.
View repository →Verified, pay-per-use API tools for AI agents through one authenticated connection.
View repository →49 deterministic tools for text integrity, agent control, and contextual quality evidence.
