Skip to main content
Glama

Get Paxiom x402 Verifier & Preflight Metadata

get_x402_verifier_info
Read-onlyIdempotent

Retrieve Paxiom Receipt Verifier reference service discovery metadata, published Ed25519 counter-attestation public keys (/.well-known/x402-keys.json), and free rate-limited public HTTP endpoints for offline verification, live Base USDC settlement verification (/v1/receipt/verify-live), and pre-payment seller safety preflight (/v1/x402/preflight). Stateless, read-only, and free with no authentication required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_x402_verifier_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
baseUrlYesHTTPS origin of the verifier API.
serviceYesCanonical verifier service identifier ("paxiom-receipt-verifier").
npmPackageYesLocal zero-dependency npm SDK and stdio MCP package details (@paxiom/receipts).
mcpEndpointYesStreamable-HTTP MCP endpoint URL.
freeEndpointsYesUnauthenticated free HTTP routes for offline verification, live settlement verification, seller preflight, and .well-known key discovery.
receiptVersionYesSupported receipt schema version ("paxiom.receipt.v0").
paidX402EndpointsYesNull on the free public reference verifier (or custom x402 gate descriptor if enabled on a self-hosted instance).
trustedPaxiomKeysYesPublished Ed25519 counter-attestation public keys ({ keyId, algorithm, publicKey }).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / freeEndpoints / description
      Previous value: -"Unauthenticated free HTTP routes for offline verification, demo fixtures, and .well-known discovery."New value: +"Unauthenticated free HTTP routes for offline verification, live settlement verification, seller preflight, and .well-known key discovery."
    • changedOutput schema / properties / paidX402Endpoints / description
      Previous value: -"Active x402 Base USDC payment terms, payTo address, facilitator URL, and priced route descriptors, or null if disabled."New value: +"Null on the free public reference verifier (or custom x402 gate descriptor if enabled on a self-hosted instance)."
    • changedOutput schema / properties / receiptVersion / description
      Previous value: -"Supported Paxiom receipt schema version (\"paxiom.receipt.v0\")."New value: +"Supported receipt schema version (\"paxiom.receipt.v0\")."
    • changedOutput schema / properties / trustedPaxiomKeys / description
      Previous value: -"Published Ed25519 root counter-attestation public keys ({ keyId, algorithm, publicKey })."New value: +"Published Ed25519 counter-attestation public keys ({ keyId, algorithm, publicKey })."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "baseUrl": {
      +      "description": "HTTPS origin of the verifier API.",
      +      "type": "string"
      +    },
      +    "freeEndpoints": {
      +      "description": "Unauthenticated free HTTP routes for offline verification, demo fixtures, and .well-known discovery.",
      +      "type": "object"
      +    },
      +    "mcpEndpoint": {
      +      "description": "Streamable-HTTP MCP endpoint URL.",
      +      "type": "string"
      +    },
      +    "npmPackage": {
      +      "description": "Local zero-dependency npm SDK and stdio MCP package details (@paxiom/receipts).",
      +      "type": "object"
      +    },
      +    "paidX402Endpoints": {
      +      "description": "Active x402 Base USDC payment terms, payTo address, facilitator URL, and priced route descriptors, or null if disabled.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "receiptVersion": {
      +      "description": "Supported Paxiom receipt schema version (\"paxiom.receipt.v0\").",
      +      "type": "string"
      +    },
      +    "service": {
      +      "description": "Canonical verifier service identifier (\"paxiom-receipt-verifier\").",
      +      "type": "string"
      +    },
      +    "trustedPaxiomKeys": {
      +      "description": "Published Ed25519 root counter-attestation public keys ({ keyId, algorithm, publicKey }).",
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "service",
      +    "receiptVersion",
      +    "baseUrl",
      +    "mcpEndpoint",
      +    "npmPackage",
      +    "trustedPaxiomKeys",
      +    "freeEndpoints",
      +    "paidX402Endpoints"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds real extra context — stateless, free, rate-limited, and no authentication required — which is genuine behavioral information not present in the annotations. However, it does not describe what the returned metadata looks like or any rate-limit specifics, so it stays at a solid 3-4 range rather than fully fleshed out.

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

Conciseness4/5

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

A single dense sentence that front-loads the primary resource (verifier reference metadata) before the sub-resources and the stateless/free qualifiers. Nothing is wasted, though the many parenthetical paths make it heavy to parse in one pass.

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

Completeness4/5

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

With zero parameters, an output schema present, and annotations covering safety, the description needs only to convey access model and scope, which it does (stateless, read-only, free, no auth). The one omission is routing guidance relative to the sibling verification tools.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The mention of concrete well-known paths is helpful orientation but is not parameter information.

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

Purpose4/5

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

States a specific verb (retrieve) and a specific resource (Paxiom Receipt Verifier discovery metadata, Ed25519 public keys, and public HTTP endpoints), with named paths like /.well-known/x402-keys.json and /v1/receipt/verify-live. It does not explicitly contrast itself with the sibling tools explain_receipt or verify_receipt, so an agent must infer that this returns metadata rather than performing verification.

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

Usage Guidelines3/5

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

Usage is only implied through the enumerated endpoint purposes ('offline verification', 'live Base USDC settlement verification', 'pre-payment seller safety preflight'), which hints at when the tool is useful. There is no explicit statement of when to call this instead of verify_receipt or explain_receipt, and no exclusions or prerequisites beyond the free/no-auth note.

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.