Skip to main content
Glama

Api pass buy

api_pass_buy

Buy a prepaid multi-API x402 credit key ($0.50 paid on Base/Arc/Solana USDC -> $0.65 usable balance, +30% bonus). Send the returned apx_ key in X-APEX-PASS or Authorization: Bearer. $0.50 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_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.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses price/bonus economics, the returned apx_ key format, required auth headers (X-APEX-PASS or Bearer), and per-call cost. It omits failure/expiry behavior of the key, which keeps it from a 5.

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?

Front-loads the action and price, then the auth header and the two-step flow. Dense but each sentence contributes; the parenthetical chain list is slightly cramped but still readable.

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 single optional-parameter purchase tool with no output schema, it covers cost, payment rails, auth, and the terms-signing sequence. Missing only what happens on failed/expired terms or how the key's balance is verified.

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 `payment` as a signed x402 base64 payload. The description adds only the procedural context (sign terms first, then pass payment), not new syntax or format 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 prepaid multi-API x402 credit key," with concrete pricing and bonus terms. It is distinguishable from generic buy tools, though it never names the closest sibling api_pass_pro_buy to clarify the difference.

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 two-step protocol: call once without `payment` to get terms, sign with your own wallet, call again with `payment` to complete. It also names the accepted payment rails (USDC on Base/Arc/Solana). No exclusions versus sibling pass tools, so it stops short of a 5.

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