Skip to main content
Glama

x402 Payment Gateway

wever_x402-payment-gateway

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Verifies an EOA payment signature and observes Base USDC nonce, balance and chain time. Does not simulate, submit, settle, reserve or authorize resource access. Operating boundary: Direct access uses x402 Base USDC settlement or the verified-wallet free tier. Verifies an EOA payment signature and observes Base USDC nonce, balance and chain time. Does not simulate, submit, settle, reserve or authorize resource access. The API access fee is separate from any inspected payment or recorded invoice amount. POST /api/x402-payment-gateway. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. This current money service follows its published inspection, policy evaluation or private invoice contract. Payment is an API access fee and grants no spending authority.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
paymentYes
target_productYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -trueNew value: +false
    • removedInput schema / description
      Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."
    • removedInput schema / maxProperties
      Removed value: -64
    • removedInput schema / minProperties
      Removed value: -1
    • addedInput schema / properties / mode / const
      Added value: +"inspect_x402_authorization"
    • removedInput schema / properties / mode / maxLength
      Removed value: -128
    • removedInput schema / properties / mode / minLength
      Removed value: -1
    • removedInput schema / properties / mode / type
      Removed value: -"string"
    • addedInput schema / properties / payment
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "accepted": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "amount": {
      +          "pattern": "^(0|[1-9][0-9]{0,77})(?![\\s\\S])",
      +          "type": "string"
      +        },
      +        "asset": {
      +          "pattern": "^0x[0-9a-fA-F]{40}(?![\\s\\S])",
      +          "type": "string"
      +        },
      +        "extra": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "name": {
      +              "const": "USD Coin"
      +            },
      +            "version": {
      +              "const": "2"
      +            }
      +          },
      +          "required": [
      +            "name",
      +            "version"
      +          ],
      +          "type": "object"
      +        },
      +        "maxTimeoutSeconds": {
      +          "maximum": 3600,
      +          "minimum": 1,
      +          "type": "integer"
      +        },
      +        "network": {
      +          "const": "eip155:8453"
      +        },
      +        "payTo": {
      +          "pattern": "^0x[0-9a-fA-F]{40}(?![\\s\\S])",
      +          "type": "string"
      +        },
      +        "scheme": {
      +          "const": "exact"
      +        }
      +      },
      +      "required": [
      +        "scheme",
      +        "network",
      +        "amount",
      +        "asset",
      +        "payTo",
      +        "maxTimeoutSeconds",
      +        "extra"
      +      ],
      +      "type": "object"
      +    },
      +    "payload": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "authorization": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "from": {
      +              "pattern": "^0x[0-9a-fA-F]{40}(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "nonce": {
      +              "pattern": "^0x[0-9a-fA-F]{64}(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "to": {
      +              "pattern": "^0x[0-9a-fA-F]{40}(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "validAfter": {
      +              "pattern": "^(0|[1-9][0-9]{0,77})(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "validBefore": {
      +              "pattern": "^(0|[1-9][0-9]{0,77})(?![\\s\\S])",
      +              "type": "string"
      +            },
      +            "value": {
      +              "pattern": "^(0|[1-9][0-9]{0,77})(?![\\s\\S])",
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "from",
      +            "to",
      +            "value",
      +            "validAfter",
      +            "validBefore",
      +            "nonce"
      +          ],
      +          "type": "object"
      +        },
      +        "signature": {
      +          "pattern": "^0x[0-9a-fA-F]{130}(?![\\s\\S])",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "signature",
      +        "authorization"
      +      ],
      +      "type": "object"
      +    },
      +    "resource": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "description": {
      +          "maxLength": 256,
      +          "type": "string"
      +        },
      +        "mimeType": {
      +          "const": "application/json"
      +        },
      +        "url": {
      +          "maxLength": 256,
      +          "minLength": 1,
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "url",
      +        "description",
      +        "mimeType"
      +      ],
      +      "type": "object"
      +    },
      +    "x402Version": {
      +      "const": 2
      +    }
      +  },
      +  "required": [
      +    "x402Version",
      +    "resource",
      +    "accepted",
      +    "payload"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / target_product
      Added value: +{
      +  "enum": [
      +    "diligenceops-paid-run",
      +    "agent-daily-operator-brief",
      +    "mcp-diligence-rail",
      +    "agent-work-order-rail",
      +    "agent-paid-workflow",
      +    "unified-agent-checkout",
      +    "agent-allowance-console",
      +    "agent-work-order-exchange",
      +    "proof-relay",
      +    "delegated-authority",
      +    "x402-payment-gateway",
      +    "payment-authority-inspector",
      +    "agent-invoice-rail",
      +    "agent-budget-guard"
      +  ]
      +}
    • addedInput schema / required
      Added value: +[
      +  "mode",
      +  "target_product",
      +  "payment"
      +]
  2. First observed

TDQS

C2.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly=false, idempotent=false, destructive=false and openWorld=true; the description adds real value beyond them by disclosing the cost model (0.10 USDC/call on Base), the rolling 30-day 10-call free tier, and the explicit negative capability list (no simulate/submit/settle/reserve/authorize, no server credentials). That said, much of the surrounding text is vague compliance hedging ('grants no authority', 'follows its published inspection... contract') that adds noise rather than behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It front-loads pricing, which is good, but the body is padded with heavily repeated sentences (the verify/observe sentence appears verbatim twice) and generic legalese, so a large fraction of the text does not earn its place and the actual purpose is not front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent, open-world tool with a complex nested input and no output schema and no parameter descriptions, the description should explain how to construct the payment payload and what the inspection returns. It covers none of that, leaving an agent without enough information to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three required parameters, one of which is a deeply nested payment object with signature, authorization (from/to/value/validAfter/validBefore/nonce), accepted terms and resource. The description explains none of these fields, their expected forms, or how mode/target_product interact with the payment payload, so it fails to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description does state a discernible verb+resource: it verifies an EOA payment signature and observes Base USDC nonce, balance and chain time, and it explicitly rules out simulating, submitting, settling, reserving or authorizing. However, this is buried inside a large block of pricing and legal boilerplate, and the identical capability sentence appears twice, so the core purpose has to be excavated rather than read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It hints at access mechanics (x402 Base USDC settlement or the verified-wallet free tier, read the backend 402 body for terms) but never says when to pick this over the many sibling payment tools such as payment-authority-inspector or ap2-mandate-gateway. No exclusions, prerequisites, or explicit alternative routing are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.