Skip to main content
Glama

Genesis402 by UnyKorn (x402 pay-per-call)

Call any endpoint

genesis402_call

Calls any of the 380 Genesis402 endpoints by name (DeFi, SEC filings, research, web/domain intel, AI text tools, multi-chain reads). Prices $0.001-$0.25 USDC on Base. Use for any endpoint without a dedicated tool; look up the name and parameters with genesis402_catalog first. Parameters are validated for free before any quote. Without payment_signature (or a local payer) it returns the exact price quote and signs nothing; with payment it returns the result plus the settlement details.

Input Schema

NameRequiredDescriptionDefault
paramsNoParameters for that endpoint as an object, matching the parameter schema shown in genesis402_catalog. Omit if the endpoint takes none.
endpointYesEndpoint name exactly as listed by genesis402_catalog, e.g. "defi-yields" or "wallet-brief" (a leading slash is ignored).
payment_signatureNoOptional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

NameRequiredDescriptionDefault
modeYesQUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
paidYestrue only when a payment was settled for this call.
priceNoThe Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
resultNoPAID or FREE: the endpoint's JSON result.
resourceNoQUOTE_ONLY: the full URL of the paid resource.
how_to_payNoQUOTE_ONLY: how to sign and resend the call.
settlementNoPAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
what_you_getNoQUOTE_ONLY: the rail's description of what the payment buys.
payment_required_b64NoQUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
also_accepted_networksNoQUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed18 schema fields changed
    • changedInput schema / properties / endpoint / description
      Previous value: -"Endpoint name from genesis402_catalog, e.g. defi-yields or price."New value: +"Endpoint name exactly as listed by genesis402_catalog, e.g. \"defi-yields\" or \"wallet-brief\" (a leading slash is ignored)."
    • changedInput schema / properties / params / description
      Previous value: -"The endpoint's parameters as an object; see its parameters in genesis402_catalog."New value: +"Parameters for that endpoint as an object, matching the parameter schema shown in genesis402_catalog. Omit if the endpoint takes none."
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."
    • changedOutput schema / properties / also_accepted_networks / description
      Previous value: -"Other payment networks this endpoint accepts."New value: +"QUOTE_ONLY: every network the 402 challenge accepts."
    • changedOutput schema / properties / how_to_pay / description
      Previous value: -"How to pay for this call."New value: +"QUOTE_ONLY: how to sign and resend the call."
    • changedOutput schema / properties / mode / description
      Previous value: -"QUOTE_ONLY when no payment was made; the quote is in price."New value: +"QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment."
    • addedOutput schema / properties / mode / enum
      Added value: +[
      +  "QUOTE_ONLY",
      +  "PAID",
      +  "FREE"
      +]
    • changedOutput schema / properties / paid / description
      Previous value: -"true or the paid quote when payment settled."New value: +"true only when a payment was settled for this call."
    • addedOutput schema / properties / paid / type
      Added value: +"boolean"
    • changedOutput schema / properties / payment_required_b64 / description
      Previous value: -"The raw x402 PAYMENT-REQUIRED header, base64."New value: +"QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client."
    • addedOutput schema / properties / price / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "atomic": {
      +        "description": "Price in USDC atomic units (6 decimals), as a decimal string.",
      +        "type": "string"
      +      },
      +      "network": {
      +        "description": "CAIP-2 network id of the lane, eip155:8453 (Base).",
      +        "type": "string"
      +      },
      +      "payTo": {
      +        "description": "Address the payment settles to.",
      +        "type": "string"
      +      },
      +      "usd": {
      +        "description": "Price in US dollars.",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "atomic",
      +      "usd",
      +      "payTo",
      +      "network"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / properties / price / description
      Previous value: -"Quote on Base USDC: atomic, usd, payTo, network."New value: +"The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment."
    • changedOutput schema / properties / resource / description
      Previous value: -"The endpoint URL that was quoted or called."New value: +"QUOTE_ONLY: the full URL of the paid resource."
    • changedOutput schema / properties / result / description
      Previous value: -"The endpoint's response data."New value: +"PAID or FREE: the endpoint's JSON result."
    • changedOutput schema / properties / settlement / description
      Previous value: -"Decoded x402 settlement (tx hash, network, payer)."New value: +"PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none."
    • changedOutput schema / properties / what_you_get / description
      Previous value: -"What the paid call returns."New value: +"QUOTE_ONLY: the rail's description of what the payment buys."
    • addedOutput schema / properties / what_you_get / type
      Added value: +"string"
    • addedOutput schema / required
      Added value: +[
      +  "mode",
      +  "paid"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / endpoint / description
      Added value: +"Endpoint name from genesis402_catalog, e.g. defi-yields or price."
    • addedInput schema / properties / params / description
      Added value: +"The endpoint's parameters as an object; see its parameters in genesis402_catalog."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "also_accepted_networks": {
      +      "description": "Other payment networks this endpoint accepts.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "how_to_pay": {
      +      "description": "How to pay for this call.",
      +      "type": "string"
      +    },
      +    "mode": {
      +      "description": "QUOTE_ONLY when no payment was made; the quote is in price.",
      +      "type": "string"
      +    },
      +    "paid": {
      +      "description": "true or the paid quote when payment settled."
      +    },
      +    "payment_required_b64": {
      +      "description": "The raw x402 PAYMENT-REQUIRED header, base64.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "price": {
      +      "description": "Quote on Base USDC: atomic, usd, payTo, network."
      +    },
      +    "resource": {
      +      "description": "The endpoint URL that was quoted or called.",
      +      "type": "string"
      +    },
      +    "result": {
      +      "description": "The endpoint's response data."
      +    },
      +    "settlement": {
      +      "description": "Decoded x402 settlement (tx hash, network, payer)."
      +    },
      +    "what_you_get": {
      +      "description": "What the paid call returns."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description goes well beyond them by disclosing the price band ($0.001-$0.25 USDC on Base), that parameter validation is free pre-quote, and the two distinct outcome modes (quote-only with no signing vs. result plus settlement details on payment). This is exactly the added behavioral context the annotations cannot carry.

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

Conciseness5/5

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

Purpose and scope lead, then pricing, then the catalog prerequisite, then the payment branch — a sensible order with no filler. Every sentence carries distinct operational information.

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

Completeness5/5

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

An output schema exists, so return formatting need not be described, yet the description still distinguishes the two return modes. Between the description, the routing guidance to genesis402_catalog, and the fully covered schema, an agent has everything needed to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the workflow semantics behind payment_signature (omit to receive a quote, nothing charged) and by pointing params at the schema shown in genesis402_catalog. It does not add format detail for the endpoint name beyond what the schema already gives.

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

Purpose5/5

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

States a specific verb (calls) and resource (any of the 380 Genesis402 endpoints), enumerates the endpoint families covered, and explicitly positions itself against the dedicated siblings ('Use for any endpoint without a dedicated tool'). An agent can route between this and genesis402_defi_yields or genesis402_whois without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use rule ('any endpoint without a dedicated tool'), a prerequisite step ('look up the name and parameters with genesis402_catalog first'), and a when-not-to-pay path ('without payment_signature ... signs nothing'). The alternatives and the gating condition are both named.

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.