Skip to main content
Glama

Api pass pro buy

api_pass_pro_buy

Buy a Pro prepaid multi-API x402 credit key ($0.99 paid on Base/Arc/Solana USDC -> $1.39 usable balance, +40% bonus; under $1 spend cap). Send the returned apx_ key in X-APEX-PASS or Authorization: Bearer. $0.99 per call over x402 (USDC on Base or USDC on Arc or USDC on Solana only). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": "api_pass_pro_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden, and it does disclose a lot: price, bonus, a sub-$1 spend cap, accepted chains, the returned apx_ key, and the auth headers to use it. It omits key behavioral facts an agent needs before committing money — whether retries or repeat calls charge again, what the unsigned first call returns, and whether terms expire.

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

Conciseness3/5

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

Purpose and price are front-loaded, which is good, but the pricing is stated twice ($0.99 in the first sentence and again mid-paragraph) and the accepted chains are enumerated twice in different phrasings. The sentences are dense, run-on, and mix payment mechanics with post-purchase auth instructions.

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?

For a one-parameter, no-annotation, no-output-schema purchase tool it covers the essentials: what is bought, what it costs, which chains, how to authenticate the returned key, and the two-step signing flow. Only edge cases (failed payment, repeat purchase, terms lifetime) are missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema already explains that `payment` is a signed x402 base64 payload that completes the purchase. The description adds one genuinely new semantic point — that `payment` should be omitted on a first call to fetch terms — but otherwise restates the schema's meaning.

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 and resource ("Buy a Pro prepaid multi-API x402 credit key") and pins down the value proposition ($0.99 in, $1.39 usable, +40%). It never explains how it differs from the sibling api_pass_buy, so an agent comparing the two must infer the Pro distinction from the name alone.

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

Usage Guidelines4/5

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

Gives an explicit operational sequence: call once without `payment` to obtain terms, sign them with your own wallet, then call again with `payment`. That is clear when-to-pass guidance. It stops short of saying when a caller should choose this Pro pass over api_pass_buy or what to do after the key is issued.

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.

Resources