Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
Z_ZERO_API_KEYYesYour Z-ZERO Passport Key (zk_live_...). Obtain it from the dashboard at https://z-zero.xyz/dashboard/agents.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_cardsA

List all available virtual card aliases and their balances. No sensitive data is returned.

check_balanceA

Check spendable USD balance for a card alias. For active token limits, use list_cards instead.

get_deposit_addressesA

Get your Base deposit address to top up your wallet with USDC (or any supported stablecoin on Base).

request_payment_tokenA

Request a single-use JIT virtual card ($1–$100) locked to one amount + merchant. ⚠️ Read mcp://resources/sop first. Only call once the FINAL total is visible — for physical goods that is AFTER shipping is submitted (use get_merchant_hints to navigate there). For digital goods with the price already visible, prefer auto_pay_checkout instead. BEFORE requesting: look at the checkout page one more time and compare it against what the user actually asked for — same items, same quantity, same variant, same destination? If anything differs, do NOT request a token; fix the cart or check with the user first. A mismatch you catch here costs nothing; after this point it costs a card. If you pass cart, the server signs your declared intent and binds the card to it — the user gets cryptographic proof of what this card was authorized for.

get_merchant_hintsA

Get merchant navigation flow for a domain or platform key (e.g. '_platform_etsy'). Returns pre_steps (how to navigate checkout) and platform notes. Call BEFORE starting checkout to understand the multi-step flow.

execute_paymentA

Execute a payment with a one-time token: Z-Zero opens a headless browser, injects the card (you NEVER see the PAN), clicks Pay, then watches for a REAL confirmation before reporting success. Returns a status: confirmed (order placed → token burned, receipt_id may hold a real order #), declined (merchant rejected → token kept for refund), unconfirmed (submitted but no confirmation seen → do NOT retry blindly, verify first), not_submitted (no Pay button → supply a submit_selector hint), or no_fields. ALWAYS pass actual_amount so overcharges are blocked and underspend refunded.

cancel_payment_tokenA

Cancel unused token and refund instantly. Use when user cancels the purchase or to free up a card slot.

request_human_approvalA

Pause and ask the user for approval before risky actions (price mismatch, large amount, unusual request).

set_api_keyA

Activate a new Passport Key instantly, no restart needed. Only call when user explicitly provides a key.

show_api_key_statusA

Check if Passport Key is configured. Shows prefix only, for debugging.

auto_pay_checkoutA

⚠️ MANDATORY: Read mcp://resources/sop first. Only use on PAYMENT pages where final total is visible. Auto-detects Web3 or Fiat and completes payment. For physical goods (Shopify, Etsy), get_merchant_hints first.

report_checkout_failA

Report a checkout you could not complete. Pick the failure_class that best matches what you saw — this feeds Z-ZERO's self-healing loop (labeled failures become better merchant hints for the next run). If nothing fits, use 'unknown' and describe what happened in error_message.

verify_receiptA

Check where an order ENDED UP, and prove it. Returns TWO separate axes: order_status — 'completed' (bought, issuer not reported yet) · 'settled' (issuer confirmed) · 'reversed' (auth voided before clearing — the order does NOT stand) · 'partially_refunded' / 'refunded' (merchant returned money AFTER settlement — the order still happened) — and funds_status — 'no_payout_due' · 'payout_pending' (money owed back but not yet confirmed on-chain) · 'returned' (confirmed on-chain). Read BOTH before speaking: 'reversed' or 'refunded' with funds 'payout_pending' means the buyer has NOT got the money back yet — never say they have. If you told the user a purchase was done and a later check returns 'reversed', tell them unprompted.

Prompts

Interactive templates invoked by user choice

NameDescription
safe_checkoutGuided zero-trust checkout: follows the Z-ZERO SOP, surfaces the final total and asks for human approval before any money moves.
wallet_statusSummarize the Z-ZERO wallet: card aliases, spendable balances, and the Base USDC deposit address for top-ups.

Resources

Contextual data attached and managed by the client

NameDescription
Standard Operating Procedure (SOP) for Autonomous PaymentsA comprehensive guide on how AI agents should use the Z-ZERO tools to execute secure, zero-trust payments.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dempty-glitch/Z-Zero-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server