_ registry / mcp http-sse · checked 3h ago

AgentCard

https://mcp.agentcard.sh

Registry code: a65ccd69d99fe686

api record

Agentcard issues virtual debit cards for AI agents. Calling tools requires connecting an Agentcard account via OAuth — start any tool call to receive the authorization challenge.

endpoint
https://mcp.agentcard.sh/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
889ms

last good check

priced tools
0

of 55 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 55 tools
55 auth-required 55 of 55 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_card_balance auth-required never probed

    The live balance of ONE virtual card (the user's overall cash balance is get_balance). Prefer this over get_card_details when you only need to verify available funds: it is faster and does not expose sensitive card credentials.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The card ID"
    }
  }
}
    arguments 12 lines
  • start_support_chat auth-required never probed

    Start a new support conversation and send the first message

    mcp-tool

    {
  "type": "object",
  "required": [
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Your initial support message"
    }
  }
}
    arguments 12 lines
  • get_balance auth-required never probed

    The user's cash balance: the money that funds new cards. Provisions the balance account on first use. Users add cash with Apple Pay or Google Pay in USD; funds are held as USDC. (Their wallet, meaning the cards themselves, is list_cards.)

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_pending_approvals auth-required never probed

    List the user's PENDING approval requests: asks from connected apps (create a card, view full card details, close/pause/resume a card, change a limit) waiting on the user's decision. Surface each one to the user and let THEM decide; after the user answers, resolve with approve_request. NEVER approve or deny on your own — an approval is the user's consent, not yours. Personal sessions only; company-connected sessions have no personal inbox.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • buy auth-required never probed

    Shop and check out, in natural language, across the merchants the user has linked (DoorDash, etc.). Pass the whole ask as `request` — e.g. "order a caesar salad from Zuni on DoorDash" — and this tool runs the shopping flow for you. It is CONVERSATIONAL: this tool RETURNS a `conversation_id`; pass that SAME `conversation_id` back on every follow-up (your reply to a question, "add a coke", "yes, check out") so it continues the SAME order. Omit it (or set new_order=true) only to start a fresh order. It will ask for the delivery address and have you confirm the cart and total. CHECKOUT (which charges a one-time card) happens ONLY after the user explicitly confirms in a later message — relay the confirmation through `request` ("yes, place the order") on the SAME conversation_id. RELAY REPLIES VERBATIM: when the user answers a question from this tool ("yes", "the 16 oz one", "use my other card"), pass their reply through `request` as-is on the same conversation_id — do NOT rewrite it into a fresh full order command; a rewritten command reads as a NEW ask and the confirmation never lands. NEVER use new_order (or drop the conversation_id) to recover from an error or a refused checkout — that discards the cart and any pending confirmation. Stay on the same conversation_id and follow the error's instruction instead; new_order is ONLY for the user starting an unrelated order. If it hands out a merchant login link (hosted connect), just reply on the SAME conversation_id once the user finishes (e.g. "done — I logged in") and it verifies the link itself. Logins started here have no pending_id, so the buy_connect / buy_connect_status pair does not apply to them. Call get_instructions FIRST for the current usage guide before your first buy.

    mcp-tool

    {
  "type": "object",
  "required": [
    "request"
  ],
  "properties": {
    "request": {
      "type": "string",
      "description": "The natural-language ask or follow-up, e.g. \"order a caesar salad from Zuni on DoorDash\", \"deliver to 123 Main St\", or \"yes, place the order\"."
    },
    "new_order": {
      "type": "boolean",
      "description": "Start a fresh shopping conversation instead of continuing the current one. Use when beginning an unrelated order (ignores any conversation_id)."
    },
    "conversation_id": {
      "type": "string",
      "description": "The conversation_id returned by a previous buy call. Pass it to continue the SAME order (keeps the cart + confirmation). Omit to start a new order."
    }
  }
}
    arguments 20 lines
  • pause_card auth-required never probed

    Pause a multi-use card: temporarily blocks ALL new charges (reversible — use resume_card to unblock). Right for "stop this subscription for now" or a card the user suspects is compromised but is not sure. Only multi-use cards can be paused; single-use cards close after one charge and cannot be paused.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The card ID to pause (from list_cards or create_card)."
    },
    "approval_id": {
      "type": "string",
      "description": "Approval id from a prior approval_required response, once the user has approved. Only for cards created through ANOTHER app: first call without it (the user is emailed an approve link), then retry with it."
    }
  }
}
    arguments 16 lines
  • update_card_limit auth-required never probed

    Change a multi-use card's total spending limit. Raising it reserves the extra amount from the user's cash balance (top up with add_funds if short); lowering it frees the difference, but the new limit can never go below what the card has already spent. Single-use cards cannot be resized.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The multi-use card ID to resize."
    },
    "approval_id": {
      "type": "string",
      "description": "Approval id from a prior approval_required response, once the user has approved. Only for cards created through ANOTHER app: first call without it (the user is emailed an approve link), then retry with it."
    },
    "new_limit_cents": {
      "type": "number",
      "description": "Deprecated alias for spend_limit_cents. Prefer spend_limit_cents (matches the docs and the REST API)."
    },
    "spend_limit_cents": {
      "type": "number",
      "description": "The new TOTAL spending limit in cents (minimum 100). This is the lifetime cap, not a delta: a card that spent $20 of a $50 limit, resized to 8000, can spend $60 more."
    }
  }
}
    arguments 24 lines
  • get_rewards auth-required never probed

    Show the user's tokenback: balance, lifetime earned, and recent activity. Tokenback pays tokens (1 token = 1¢ of credit value) on settled card spend. AI cards (create_card scope_preset: 'ai_labs') earn a boosted rate on AI-lab purchases, and companies can route a share of their earnings to their users as tokenback. Redeem with redeem_rewards.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • verify_phone auth-required never probed

    Check the one-time code the user received from start_phone_verification. On success the balance is unlocked for funding (the verification stays fresh for 60 days) — call add_funds next. A wrong or expired code returns a recoverable status so you can ask the user to re-check it, or call start_phone_verification to resend.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The one-time code the user received, as a string (keep any leading zeros — do not send it as a number)."
    }
  }
}
    arguments 12 lines
  • get_settings auth-required never probed

    View the user's notification preferences (which email alerts they receive), their default payment source (which card or balance agents charge — check it before picking a funding source for them), their default delivery address (the wallet-level shipping address to use when buying physical goods for them — check it before asking them to dictate an address), and authorization settings (whether viewing card details or making transactions requires explicit approval). Authorization settings are read-only here; change the rest with the gated tool update_settings, calling it by name even though it isn't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • buy_list_merchants auth-required never probed

    List merchants available for agent commerce (Rappi, Good Eggs, DoorDash) and whether this user has linked each one. Link a merchant before shopping it.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • buy_connect_status auth-required never probed

    Check the status of a hosted merchant login started with buy_connect. Returns linking (still in progress — call again in a few seconds), linked (success — the merchant is ready to shop), expired, or error. Pass the merchant and the pending_id from buy_connect. ONLY for logins started by the buy_connect tool: a login link handed out by the conversational `buy` tool has no pending_id — for those, reply to the same `buy` conversation ("done — I logged in") instead of calling this.

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant",
    "pending_id"
  ],
  "properties": {
    "merchant": {
      "type": "string",
      "description": "merchant slug (e.g. doordash)"
    },
    "pending_id": {
      "type": "string",
      "description": "The pending_id returned by buy_connect."
    }
  }
}
    arguments 17 lines
  • check_kyc_document auth-required 3h ago

    Check the conversational verification state — use after the user uploads their ID via the browser upload link (or any time you need to re-orient). Returns the current step and the fields still missing.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_instructions auth-required 3h ago

    Call this FIRST; returns the latest usage guide for shopping with `buy` AND for operating the Agentcard account tools (cards, funding, your own card, KYC, support).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_kyc_status auth-required 3h ago

    Check the user's identity verification (KYC) status. Returns whether they are verified and, if not, the current state plus the conversational next step. Use this to poll after the user does the face scan, or any time create_card reports kyc_required.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • send_support_message auth-required never probed

    Send a message in an existing support conversation

    mcp-tool

    {
  "type": "object",
  "required": [
    "conversation_id",
    "message"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Your message"
    },
    "conversation_id": {
      "type": "string",
      "description": "The conversation ID"
    }
  }
}
    arguments 17 lines
  • read_support_chat auth-required never probed

    Read the message history of a support conversation

    mcp-tool

    {
  "type": "object",
  "required": [
    "conversation_id"
  ],
  "properties": {
    "conversation_id": {
      "type": "string",
      "description": "The conversation ID"
    }
  }
}
    arguments 12 lines
  • approve_request auth-required never probed

    Resolve a pending approval request (approve or deny) once the USER has decided. Use this after get_card_details or create_card returns a 202 requiring approval, or for a row from list_pending_approvals. For card_details and transaction, approval automatically completes the follow-up action and returns the result. For cross_app actions (asks from another app: close/pause/resume a card, change a limit, view details), approval records the user's consent and the REQUESTING app completes the action from its side when it retries with the approval id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "approval_id",
    "decision",
    "action",
    "resource_id"
  ],
  "properties": {
    "action": {
      "enum": [
        "card_details",
        "transaction",
        "cross_app:details",
        "cross_app:close",
        "cross_app:pause",
        "cross_app:resume",
        "cross_app:update"
      ],
      "type": "string",
      "description": "The original action type from the approval prompt (list_pending_approvals rows carry it as action)."
    },
    "decision": {
      "enum": [
        "approved",
        "denied"
      ],
      "type": "string",
      "description": "Whether to approve or deny the request"
    },
    "approval_id": {
      "type": "string",
      "description": "The approval request ID"
    },
    "resource_id": {
      "type": "string",
      "description": "Card ID (for card_details and cross_app actions) or approval ID (for transaction)"
    }
  }
}
    arguments 40 lines
  • surprise_me auth-required never probed

    Buy the user something totally unexpected and very silly/stupid-fun under a small dollar cap (default $10, hard max $25). Great when the user cannot decide what to order (from DoorDash etc.) or just wants a fun surprise. It kicks off a shopping conversation that FIRST brainstorms deliberately stupid ideas, picks ONE genuinely unexpected item, builds the cart, and shows the item + exact total. It NEVER checks out by itself: the reply includes a conversation_id — relay the user's explicit confirmation ("yes, place it") through the `buy` tool on that SAME conversation_id, exactly like a normal order. Each surprise_me call starts a fresh surprise; use `buy` for all follow-ups (answers, tweaks, the confirmation).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "vibe": {
      "type": "string",
      "description": "Optional notes/vibe from the user, e.g. \"make it food\", \"something for my desk\", \"they love ducks\"."
    },
    "merchant": {
      "type": "string",
      "description": "Optional merchant hint the surprise should come from, e.g. 'doordash'. Omit to let the agent pick."
    },
    "max_dollars": {
      "type": "number",
      "description": "Hard spend cap in dollars, total including fees. Optional; default 10, values above 25 are clamped to 25."
    }
  }
}
    arguments 18 lines
  • whoami auth-required never probed

    Show who you are operating as: the authenticated AgentCard account's email, user id, name, plan, KYC + account status, member-since date, and how this session is connected (personal login vs a third-party OAuth app connection, with the app name). Call this when the user asks "who am I" / "which account is this", or before money-moving actions when you need to confirm the account. Read-only. KYC shown here is the stored snapshot — use get_kyc_status when you need the live, provider-checked state.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_cards auth-required never probed

    The user's wallet: every live card they hold, with IDs, last four digits, expiry, balance, and status, plus `vaultCards`: the user's OWN cards stored in their Agentcard vault (display fields only; a vaulted card pays through buy with an approval on the user's device (their passkey or master password) and never exposes a number). Start here to find available cards; if none are returned, call create_card. When the shared wallet is enabled, `wallet` lists every card across all connected apps and companies, each tagged with its source (kind personal/company, the issuing app, and the company where applicable); cards created by another app or company are read-only from this session: get_card_details and close_card will not work on them.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_card_details auth-required never probed

    Get decrypted PAN, CVV, expiry, and current balance for a specific card. Use this only when you need to fill in a payment form — prefer get_card_balance if you only need the balance. May require human approval before returning credentials. If approval is required, prompt the user and then call approve_request. Card details are encrypted at rest with AES-256-GCM.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The card ID"
    },
    "approval_id": {
      "type": "string",
      "description": "Approval id from a prior approval_required response, once the user has approved. Only for cards created through ANOTHER app: first call without it (the user is emailed an approve link), then retry with it."
    }
  }
}
    arguments 16 lines
  • close_card auth-required never probed

    Permanently close a virtual card. This is irreversible — the card cannot be reopened. Safe to call on an already-closed card (idempotent). The user's rewards card (the card their tokenback redeems onto) is close-protected: closing it returns its balance to the wallet but retires the card number the user may have on file at AI labs, so it requires confirm_rewards_card — set it ONLY after the user explicitly confirms they want the rewards card closed.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The card ID to close"
    },
    "approval_id": {
      "type": "string",
      "description": "Approval id from a prior approval_required response, once the user has approved. Only for cards created through ANOTHER app: first call without it (the user is emailed an approve link), then retry with it."
    },
    "confirm_rewards_card": {
      "type": "boolean",
      "description": "Required to close the rewards card. Only set after the user explicitly confirms; never set it preemptively."
    }
  }
}
    arguments 20 lines
  • create_card auth-required never probed

    The one card tool: get the user a virtual debit card for a purchase. Cards are live and charged for real when used. For a FIRST-TIME user it starts by putting the user's OWN card in their Agentcard vault (any Visa, Mastercard, Amex, or Discover from any country, no identity verification (KYC), no balance funding): the call returns a secure link (vault_started); send it to the user (they type the card once and lock it with their passkey or master password; Agentcard never sees the number). A vaulted card pays through the buy tool, where the user approves each purchase on their device with their passkey or master password; it never becomes a card number you type, so after vault_started (or vault_ready, when a card is already in the vault) use buy for purchases instead of calling create_card again. If the user specifically needs a card NUMBER, that is an Agentcard funded from their cash balance, which requires KYC the first time: only after the user agrees, call create_card with source "issued". Established users: the saved default decides (get_settings default_payment: their chosen added card, or the wallet balance); with no saved default, an active ADDED card wins, otherwise the cash balance. Per-call overrides: connected_card_id issues against a specific added card, source "issued" forces the cash balance, restart_setup mints a fresh vault link. If the balance is short on the issued path, top up with add_funds. Connections through a company OAuth client have NO card count or amount limits; only first-party personal accounts have per-plan caps. Call get_plan for the limits in effect.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount_cents"
  ],
  "properties": {
    "type": {
      "enum": [
        "single_use",
        "multi_use"
      ],
      "type": "string",
      "description": "Card behavior. 'single_use' (default) closes after its first approved charge — right for one-off purchases. 'multi_use' stays open across charges until its total limit is spent — right for subscriptions and recurring merchants. Multi-use cards can be paused (pause_card), resumed (resume_card), and resized (update_card_limit)."
    },
    "preset": {
      "oneOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "required": [
            "privileges"
          ],
          "properties": {
            "name": {
              "type": "string"
            },
            "privileges": {
              "type": "array",
              "items": {}
            }
          }
        }
      ],
      "description": "Preset for this card: a template name (ai_labs, weekday_meals, cli_only, daily), comma-separated templates, a saved preset name/id, inline JSON privileges, or { name?, privileges }. Adds restrictions only — omit for a normal unrestricted card."
    },
    "source": {
      "enum": [
        "issued"
      ],
      "type": "string",
      "description": "Force the card to be funded from the user's cash balance (the issued path: KYC + wallet funding) even when they have an added or vaulted card or would otherwise be offered the vault. Use it only after the user explicitly picks the balance option. Omit for the default (an active added card wins; first-time users get the vault link)."
    },
    "expires_at": {
      "type": "string",
      "description": "Optional hard expiry for a multi-use card (ISO-8601 with timezone, e.g. \"2027-01-01T00:00:00Z\"). Must be in the future, at most 365 days out. The card closes automatically when it passes."
    },
    "amount_cents": {
      "type": "number",
      "description": "Card funding amount in CENTS, not dollars (minimum 100). 100 = $1.00 and 2500 = $25.00 — a value like 25 would be $0.25. Company-governed connections have no maximum; personal accounts are capped by their plan — call get_plan for the limits in effect."
    },
    "funds_source": {
      "enum": [
        "onramp_flow",
        "company_flow"
      ],
      "type": "string",
      "description": "Where the card funds come from. OMIT unless instructed: the server applies the right default (company-connected accounts use the company wallet automatically when the company enables it). company_flow = the company's wallet funds the card; onramp_flow = the user's own wallet."
    },
    "purchase_key": {
      "type": "string",
      "description": "The purchaseKey from the same approval_pending answer as pending_card_id; the pair proves the retry is for that purchase."
    },
    "scope_preset": {
      "enum": [
        "ai_labs"
      ],
      "type": "string",
      "description": "Silent alias for preset 'ai_labs': a multi-use card restricted to AI-lab merchants (OpenAI, Anthropic, Gemini); charges anywhere else are declined at authorization. AI cards earn boosted tokenback on eligible spend. Implies type 'multi_use'. Prefer `preset`."
    },
    "restart_setup": {
      "type": "boolean",
      "description": "Set true ONLY when the user lost or never received a vault link, it expired (about 15 minutes), or they want to add ANOTHER card. Never needed on the first call or for normal retries. amount_cents is still required on this call (the link itself carries no amount)."
    },
    "pending_card_id": {
      "type": "string",
      "description": "Only when retrying an approval_pending purchase whose preset has since changed: the cardId from that earlier answer, together with purchase_key. The older approval link is retired once the replacement is minted. Never pass it for a different purchase."
    },
    "connected_card_id": {
      "type": "string",
      "description": "Multi-card: issue against a SPECIFIC added card (an id from the user's added cards, see list_added_cards) instead of the newest active one. Omit for the default."
    }
  }
}
    arguments 85 lines
  • get_card_preset auth-required never probed

    Read a card's preset (spend limits, rate limits, allowed categories/merchants, time windows, and surfaces) as a plain-English summary. A card without a preset is unrestricted.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The card id (from list_cards)."
    }
  }
}
    arguments 12 lines
  • set_card_preset auth-required never probed

    Update a card's preset. Pass a template name (ai_labs, weekday_meals, cli_only, daily), a saved preset name (from list_presets), a comma-separated template list, or inline JSON / { name, privileges }. Pass null or "" to clear the card's preset (Agentcard-side checks stop; any limit already on the card network stays). Edits create a new version. The response reports what was applied on Agentcard vs what was updated on the card's spend limit, and whether the change needs a new card.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id",
    "preset"
  ],
  "properties": {
    "preset": {
      "oneOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        },
        {
          "type": "object",
          "required": [
            "privileges"
          ],
          "properties": {
            "name": {
              "type": "string"
            },
            "privileges": {
              "type": "array",
              "items": {}
            }
          }
        }
      ],
      "description": "Template name (ai_labs, weekday_meals, cli_only, daily), comma-separated templates, inline JSON privileges, or { name?, privileges }. Pass null or \"\" with card_id to clear that card's preset."
    },
    "card_id": {
      "type": "string",
      "description": "The card id (from list_cards)."
    }
  }
}
    arguments 39 lines
  • allow_card_merchant auth-required never probed

    Remember a merchant on a card so the next matching charge is allowed even when the card's category or merchant rules would otherwise deny it. One tool call — does not replace the rest of the preset.

    mcp-tool

    {
  "type": "object",
  "required": [
    "pattern"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "Card id (from list_cards)."
    },
    "pattern": {
      "type": "string",
      "description": "Merchant name pattern to remember, e.g. \"STARBUCKS\" or \"ODD CAFE\"."
    }
  }
}
    arguments 16 lines
  • list_presets auth-required never probed

    List every preset you can use by name: the built-in templates (ai_labs, weekday_meals, cli_only, daily) plus any you've saved yourself, each with a plain-English summary of its rules.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • save_preset auth-required never probed

    Save your own preset — a named set of rules (spend caps, category/merchant/place/currency/day/hour/program restrictions) you can reuse by name in set_card_preset or create_card. Saving under a name you already used adds a new version: cards already using the old one keep it, new ones get the update. Pick a name other than the built-ins (ai_labs, weekday_meals, cli_only, daily). Pass either the rule fields below or a raw `privileges` array.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "mode": {
      "enum": [
        "strict",
        "watch"
      ],
      "type": "string",
      "description": "What the preset does when a purchase breaks any of its rules: \"strict\" refuses it (the default), \"watch\" lets it through and tells the user once."
    },
    "name": {
      "type": "string",
      "description": "A name for this preset, e.g. \"meals-only\"."
    },
    "total": {
      "type": "number",
      "description": "Lifetime spend cap, in US dollars."
    },
    "only_in": {
      "type": "string",
      "description": "Comma-separated places to allow charges from: a country (\"US\", \"Canada\"), a region (\"europe\", \"eu\", \"north-america\", \"latin-america\", \"apac\"), or a US state (\"California\", \"US-CA\"). A region expands to its countries; a state next to a region narrows only the US, e.g. \"north-america,US-CA\". Example: \"europe,Canada\"."
    },
    "per_day": {
      "type": "number",
      "description": "Spend cap per rolling 24 hours, in US dollars."
    },
    "per_week": {
      "type": "number",
      "description": "Spend cap per rolling 7 days, in US dollars."
    },
    "timezone": {
      "type": "string",
      "description": "IANA timezone for only_days/only_hours (default UTC), e.g. \"America/Los_Angeles\". Always shown in summaries."
    },
    "only_days": {
      "type": "string",
      "description": "Comma-separated days to allow, e.g. \"mon,tue,wed\" or \"weekdays\"/\"weekends\"."
    },
    "only_from": {
      "type": "string",
      "description": "Comma-separated callers to allow, e.g. \"cli,mcp\" (cli, mcp, api, browser)."
    },
    "per_month": {
      "type": "number",
      "description": "Spend cap per rolling 30 days, in US dollars."
    },
    "categories": {
      "type": "string",
      "description": "Comma-separated spend categories to allow, e.g. \"meals,groceries\" (meals, groceries, travel, software, ai, wellness, retail)."
    },
    "currencies": {
      "type": "string",
      "description": "Comma-separated purchase currencies to allow: ISO 4217 codes or common names, e.g. \"usd,eur\" or \"dollars,euros,pounds,yen\". In strict mode a purchase in another currency is refused at checkout and a settled charge in another currency pauses the card. Checked by Agentcard at checkout and settlement, not by the card network. Unknown currencies are refused."
    },
    "only_hours": {
      "type": "string",
      "description": "An hour range to allow, e.g. \"9-17\" (24-hour clock; defaults to UTC without timezone)."
    },
    "privileges": {
      "type": "array",
      "items": {},
      "description": "Advanced: raw privilege objects instead of the rule fields above."
    },
    "only_merchants": {
      "type": "string",
      "description": "Comma-separated merchant name patterns to allow, e.g. \"openai,anthropic\"."
    }
  }
}
    arguments 73 lines
  • delete_preset auth-required never probed

    Delete a preset you saved (from save_preset). Refuses built-in template names — there's nothing to delete there. Cards already issued keep whatever rules they have; this only retires the name for future use. Refused while a card still inherits the name as a standing default.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "The saved preset name to delete."
    }
  }
}
    arguments 12 lines
  • get_wallet_link auth-required never probed

    The user's hosted wallet, as one shareable URL. Opens their Agentcard wallet in the browser: every card in one place, apply for an Agentcard card (identity verification runs right in the page). Mint it whenever the user needs a browser step (seeing cards, finishing verification when in-chat photos fail) and send them the URL. To ADD the user's own card, pass purpose "add_card": the link then opens their Agentcard vault card form directly (any card, typed once, locked with their passkey or master password, never seen by Agentcard) and works on personal logins too. Pass merchant + amount_cents to open the wallet ON the payment-approval sheet (the user picks a card and approves that exact charge) instead of the card list. Multi-use but short-lived (about 15 minutes — the exact moment is in expiresAt); mint a fresh one when it expires. The wallet link only works for app connections (OAuth).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "purpose": {
      "enum": [
        "wallet",
        "add_card"
      ],
      "type": "string",
      "description": "\"wallet\" (default) opens the hosted wallet. \"add_card\" opens the vault card form so the user can put their own card on file; single-use, about 15 minutes."
    },
    "merchant": {
      "type": "string",
      "description": "Merchant name shown on the payment-approval sheet (with amount_cents)."
    },
    "amount_cents": {
      "type": "integer",
      "minimum": 1,
      "description": "Amount in cents. When present, the link opens on the payment-approval sheet for this charge."
    }
  }
}
    arguments 23 lines
  • list_added_cards auth-required never probed

    List the user's ADDED cards (their own Visa/Mastercard cards enrolled via create_card's add-card flow — the funding source that charges their own card), with ids, brand, last4, expiry, and status. The row marked isDefault is what create_card charges when no connected_card_id is given — the user's chosen default card (set with update_settings default_payment), falling back to the newest active one. Not the same as list_cards (the virtual cards Agentcard issues).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • remove_added_card auth-required never probed

    Remove (unenroll) one of the user's added cards. Irreversible for that enrollment: any virtual cards created against it are closed first, then the card is unenrolled at the network. ALWAYS confirm with the user before calling. Get ids from list_added_cards. The user can add the same card again later (create_card with restart_setup: true).

    mcp-tool

    {
  "type": "object",
  "required": [
    "attached_card_id"
  ],
  "properties": {
    "attached_card_id": {
      "type": "string",
      "description": "The id of the added card to remove (from list_added_cards)."
    }
  }
}
    arguments 12 lines
  • resume_card auth-required never probed

    Resume a paused multi-use card so it accepts charges again. The inverse of pause_card.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The paused card ID to resume."
    },
    "approval_id": {
      "type": "string",
      "description": "Approval id from a prior approval_required response, once the user has approved. Only for cards created through ANOTHER app: first call without it (the user is emailed an approve link), then retry with it."
    }
  }
}
    arguments 16 lines
  • redeem_rewards auth-required never probed

    Redeem tokenback: the tokens' cash value (1 token = 1¢) lands on the user's rewards card as spending power. The rewards card is permanent and locked to AI-lab merchants (OpenAI, Anthropic, Gemini) — created on first redemption, topped up after. Check get_rewards first for the balance and the minimum. Ask the user before redeeming.

    mcp-tool

    {
  "type": "object",
  "required": [
    "tokens"
  ],
  "properties": {
    "tokens": {
      "type": "number",
      "description": "How many tokens to redeem (1 token = 1 cent, so 500 tokens = $5.00 of wallet credit)."
    }
  }
}
    arguments 12 lines
  • recommend_card auth-required never probed

    Ask the vault which of the user's own stored cards earns the most for a purchase (smart purchases). Pass the merchant name, its website when you know it, and the amount. Returns the card id to use as card_id at checkout, the reason in plain words, and the runners-up. null when smart purchases is off for this account, no stored card has been named yet (see name_card), or nothing could be said; then pay as you would have. Never a card number.

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant"
  ],
  "properties": {
    "currency": {
      "type": "string",
      "description": "ISO currency code, default usd. Non-USD purchases account for foreign transaction fees."
    },
    "merchant": {
      "type": "string",
      "description": "The merchant as the user would see it, e.g. \"DoorDash\"."
    },
    "amount_cents": {
      "type": "number",
      "description": "Order total in cents, when known."
    },
    "merchant_url": {
      "type": "string",
      "description": "The merchant's website or checkout origin, e.g. https://www.doordash.com. Improves the category match."
    }
  }
}
    arguments 24 lines
  • name_card auth-required never probed

    Tell the vault which card product one of the user's own stored cards is (e.g. "Chase Sapphire Preferred", "Amex Gold"), so smart purchases can rank it. Takes a vault card id (a `vaultCards` row from list_cards) and the product name as the user says it; the closest match is saved and echoed back. Confirm with the user when the match is not obviously right. Pass clear_product to forget the name, or smart_excluded to keep a card out of the ranking without removing it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "card_id"
  ],
  "properties": {
    "card_id": {
      "type": "string",
      "description": "The vault card id (from list_cards → vaultCards)."
    },
    "product": {
      "type": "string",
      "description": "The card product as the user says it, e.g. \"Chase Sapphire Preferred\" or \"Amex Gold\". Four characters minimum."
    },
    "clear_product": {
      "type": "boolean",
      "description": "true = forget the product name. Do not combine with product."
    },
    "smart_excluded": {
      "type": "boolean",
      "description": "true = leave this card out of smart purchases; false = include it again."
    }
  }
}
    arguments 24 lines
  • submit_user_info auth-required never probed

    Submit the user's phone number and terms acceptance for a virtual card. Call this after create_card returns user_info_required. Do NOT ask the user for occupation, income, or account purpose — those are never asked. Identity fields (name, date of birth, SSN / national ID, address) belong to the KYC flow: create_card tells you whether it runs conversationally (start_kyc → ID photo → face scan) or via a hosted verification_url. After phone + terms are saved, retry create_card.

    mcp-tool

    {
  "type": "object",
  "required": [
    "phone_number",
    "terms_accepted"
  ],
  "properties": {
    "phone_number": {
      "type": "string",
      "description": "User's phone number in international E.164 format with a country code (e.g. +1 555 123 4567, +44 7911 123456)"
    },
    "terms_accepted": {
      "type": "boolean",
      "description": "Must be true — the user accepted the AgentCard cardholder terms of service"
    }
  }
}
    arguments 17 lines
  • start_kyc auth-required never probed

    Begin (or resume) identity verification. Verification is CONVERSATIONAL: it starts with a photo of the user's government ID — the backend reads the printed details automatically and the user confirms every value. Only fields the ID does not carry are asked (like the SSN for US documents, or the national ID number for non-US ones); occupation/income questions are never asked. The only browser step is a short face scan at the end. Relay each step to the user as ONE SHORT message (one or two sentences — the current ask only, never the whole flow, never an unrequested link). Returns the next step, ID-photo upload options, and (for legacy hosted-flow accounts) a hosted verification URL instead.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "terms_accepted": {
      "type": "boolean",
      "description": "DEPRECATED — use agreements_accepted. Pass true once the user has explicitly agreed to the card issuer's cardholder terms in the conversation."
    },
    "agreements_accepted": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Keys of the User Agreements the user explicitly accepted, one by one (the full required set from the agreements list — e.g. e_sign, account_opening_privacy, card_terms, accuracy, non_solicitation). Only pass after presenting each agreement verbatim and getting a yes covering all of them."
    }
  }
}
    arguments 17 lines
  • submit_kyc_document auth-required never probed

    Submit the user's ID photo for identity verification. Ways in: (a) image data you hold programmatically (e.g. the user sent the photo in this chat and your platform exposes its bytes) — pass front_base64 (and back_base64 for a license back; its barcode reads most accurately); (b) local (stdio) mode — pass file_path/back_file_path and the file is read from disk; (c) neither — you get a secure upload link to hand the user. Do NOT ask the user what kind of document it is or where it was issued — the type and country are detected automatically from the photo; only relay a question if the result says the type could not be determined. Returns the fields read off the document — SHOW THEM TO THE USER for confirmation before continuing — plus whatever is still missing. If the result says NO identity details could be read, the image did not read as an ID at all: never insist to the user that it was their ID. Supported: JPEG/PNG/WebP up to 12MB (convert HEIC or HEIF photos first).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "file_path": {
      "type": "string",
      "description": "Local path to the ID photo (front of license, or passport photo page). Local/stdio connections only — remote connections without image data receive an upload link instead."
    },
    "back_base64": {
      "type": "string",
      "description": "Base64 image bytes of the license back (optional, recommended — the barcode reads most accurately). Same rule: programmatically sourced only."
    },
    "front_base64": {
      "type": "string",
      "description": "Base64 image bytes of the ID front (or passport photo page). ONLY pass base64 you received programmatically from your platform (e.g. an injected chat attachment) — never type or reconstruct image bytes yourself."
    },
    "document_type": {
      "enum": [
        "drivers_license",
        "state_id",
        "passport"
      ],
      "type": "string",
      "description": "ONLY pass this when the user themselves said what the document is (\"here's my license\") — otherwise omit it; the type is detected from the photo. Never ask up front."
    },
    "back_file_path": {
      "type": "string",
      "description": "Local path to the back of the license (optional, recommended). Local/stdio connections only."
    },
    "back_mime_type": {
      "type": "string",
      "description": "MIME type of back_base64. Defaults to image/jpeg."
    },
    "front_mime_type": {
      "type": "string",
      "description": "MIME type of front_base64 (image/jpeg, image/png, image/webp). Defaults to image/jpeg."
    },
    "issuing_country": {
      "type": "string",
      "description": "2-letter ISO country that issued the document (e.g. US, AR). ONLY when the user volunteered it — otherwise omit; it is detected from the photo. Never ask up front."
    }
  }
}
    arguments 43 lines
  • submit_kyc_fields auth-required never probed

    Submit identity fields for verification: the ones the ID photo didn't carry (listed by missingFields — the tax/ID number always has to be asked since IDs don't print it; call it "SSN" only for US documents and "national ID number" otherwise), corrections to extracted values the user flagged, and the User Agreements acceptance (agreements_accepted, after presenting each agreement verbatim). That number is forwarded directly to the verification provider and never stored by Agentcard. NEVER ask about occupation, income, spending volume, or account purpose — those are filled automatically and must not be asked.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "ssn": {
      "type": "string",
      "description": "US documents: 9-digit SSN, dashes optional. Non-US documents: the national ID / tax number printed on the ID. Forward-only — never stored."
    },
    "last_name": {
      "type": "string",
      "description": "Legal last name, exactly as printed on the ID document."
    },
    "first_name": {
      "type": "string",
      "description": "Legal first name, exactly as printed on the ID document."
    },
    "address_city": {
      "type": "string",
      "description": "City of the residential address."
    },
    "phone_number": {
      "type": "string",
      "description": "E.164 with country code, e.g. +14155551234."
    },
    "address_line1": {
      "type": "string",
      "description": "Residential street address, line 1 (e.g. 123 Main St)."
    },
    "address_line2": {
      "type": "string",
      "description": "Residential street address, line 2 — apartment, suite, or unit. Omit if none."
    },
    "date_of_birth": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "address_region": {
      "type": "string",
      "description": "2-letter state code for US (e.g. CA)."
    },
    "terms_accepted": {
      "type": "boolean",
      "description": "DEPRECATED — use agreements_accepted. true once the user explicitly accepted the card issuer's cardholder terms."
    },
    "address_postal_code": {
      "type": "string",
      "description": "Postal / ZIP code of the residential address."
    },
    "agreements_accepted": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Keys of the User Agreements the user explicitly accepted, one by one — the FULL required set from the agreements list in the previous step's result. Only pass after presenting each agreement verbatim and getting an explicit yes covering all of them."
    },
    "address_country_code": {
      "type": "string",
      "description": "2-letter ISO country code (e.g. US)."
    }
  }
}
    arguments 61 lines
  • list_transactions auth-required never probed

    Transactions with amount, merchant, status, and timestamps. Pass card_id for one card's transactions; OMIT it for every card in the account (newest first, each row tagged with its card). Use limit and status to filter. The gated views list_all_transactions and list_transactions_by_payment_method also exist; call them by name even though they aren't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "number",
      "description": "Max number of transactions to return (default 20)"
    },
    "offset": {
      "type": "number",
      "description": "Skip this many (all-cards view pagination; ignored for a single card)."
    },
    "status": {
      "type": "string",
      "description": "Filter by transaction status (e.g. PENDING, SETTLED, DECLINED, REVERSED, EXPIRED, REFUNDED)"
    },
    "card_id": {
      "type": "string",
      "description": "A card ID for that card's transactions; omit for all cards in the account."
    }
  }
}
    arguments 22 lines
  • setup_payment_method auth-required never probed

    Save a payment method used ONLY to pay for flight bookings (the fare is charged to it via a hold at booking; no virtual card is created for flights). It does NOT fund cards or the cash balance — cards are funded from the balance (see add_funds). Returns a secure checkout URL the user must open to save their card details.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • add_funds auth-required never probed

    Generate a secure checkout link the user opens to add cash to their own balance (the money that funds new cards) via Apple Pay or Google Pay, in USD. Calling this tool moves NO money and initiates NO transfer: it only prepares a single-use hosted payment page — the exact equivalent of the user clicking 'Add funds' in the dashboard. The user personally reviews, authorizes, and completes (or abandons) the payment in their own browser with their own payment method; you never see or handle payment credentials. If a one-time phone verification is needed first, this tool automatically sends the user a code and tells you where it went: ask the user for the code, call verify_phone with it, then call add_funds again.

    mcp-tool

    {
  "type": "object",
  "required": [
    "amount_cents"
  ],
  "properties": {
    "amount_cents": {
      "type": "number",
      "description": "Amount to add in cents (e.g. 5000 = $50.00). Typical range: $20.00 to $10,000.00 (2000 to 1000000 cents); the exact range depends on the active funding provider and is returned by the API when the amount is invalid."
    },
    "payment_method": {
      "enum": [
        "apple_pay",
        "google_pay"
      ],
      "type": "string",
      "description": "Payment method for the checkout: apple_pay or google_pay. Ask the user which one their device has; apple_pay only when unknown."
    }
  }
}
    arguments 20 lines
  • start_phone_verification auth-required never probed

    Send (or re-send) the user's one-time funding verification code (the provider verifies the phone on the user's Agentcard identity, valid 60 days). add_funds already sends this code automatically when verification is needed — call this tool only to RE-send when the code never arrived (any unexpired code still works; sends are rate-limited). Returns the masked destination (text or email) and whether a code was sent; if the phone is already verified it says so and you go straight to add_funds. After the user reads back the code, call verify_phone.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • redeem_code auth-required never probed

    Redeem a promo code that adds money to the user's cash balance. Each code works once per user; the credit lands in the balance and becomes spendable within a minute or two. Some codes hold the money until the user verifies their identity — the claim still locks the code to this user instantly, and the credit lands automatically once KYC is approved (start_kyc begins verification). The gated tool list_codes shows the user's code history; call it by name even though it isn't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "The promo code exactly as the user provided it (case and dashes are forgiven)."
    }
  }
}
    arguments 12 lines
  • get_plan auth-required never probed

    Show the user's current subscription plan, card limits, and this month's usage. Call this before create_card when you need the per-card amount cap or remaining monthly quota, and ALWAYS before creating a multi-use card: multi-use cards are a paid-plan feature, so maxActiveMultiUseCards is 0 on Free and the mint is refused. Also call it whenever the user asks about their plan, limits, billing, or upgrading. To cancel a paid plan, the gated tool cancel_plan also exists; call it by name even though it isn't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • upgrade_plan auth-required never probed

    Start a paid-plan upgrade. Choose the target plan: 'basic' ($15/mo — 15 cards/month, up to $500 per card) or 'pro' ($100/mo — 50 cards/month, up to $1,000 per card). Defaults to 'basic' if omitted. Returns a Stripe Checkout URL the user must open in their browser to complete payment. After they finish checkout, the plan updates automatically; verify with get_plan. Use only when the user explicitly wants to upgrade. To cancel a paid plan instead, the gated tool cancel_plan also exists; call it by name even though it isn't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "plan": {
      "enum": [
        "basic",
        "pro"
      ],
      "type": "string",
      "description": "Which plan to upgrade to. Defaults to 'basic'."
    }
  }
}
    arguments 14 lines
  • list_payment_methods auth-required never probed

    List the saved payment methods (used only to pay for flight bookings, not for cards or adding funds). Returns each method with its id, brand, last 4 digits, and expiry, and marks the default one. Use setup_payment_method to add a new one. The gated tools set_default_payment_method and remove_payment_method also exist; call them by name even though they aren't in the tools list.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • list_connections auth-required never probed

    List the third-party apps the user has connected to their Agentcard account via OAuth (e.g. Kilo), including when each was connected and whether it is still active. Read-only. To revoke an app, call revoke_connection with its clientId.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • revoke_connection auth-required never probed

    Revoke a third-party app's access to the user's Agentcard account. Disconnects the app and invalidates its OAuth tokens; it must reconnect via OAuth to regain access. Pass the clientId shown by list_connections.

    mcp-tool

    {
  "type": "object",
  "required": [
    "client_id"
  ],
  "properties": {
    "client_id": {
      "type": "string",
      "description": "The OAuth client ID of the app to revoke (from list_connections)."
    }
  }
}
    arguments 12 lines
  • link_account auth-required never probed

    Link or merge another Agentcard account that belongs to the same person. Use when the user says they already have an account under a DIFFERENT email or phone number — most often after identity verification (KYC) is rejected as a duplicate, which means that person already verified on another account. Two steps: (1) call with { type, identifier } to send a one-time code to that email/phone; (2) call again with the { ticket, code } to verify. If the identifier belongs to a different account, the two accounts are MERGED (the identity-verified account survives and gains the other's email/phone, so both sign in to one account); if no account has it, it is simply added to the current account.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "code": {
      "type": "string",
      "description": "Step 2: the one-time code the user received."
    },
    "type": {
      "enum": [
        "email",
        "phone"
      ],
      "type": "string",
      "description": "Step 1: which kind of identifier the OTHER account uses."
    },
    "ticket": {
      "type": "string",
      "description": "Step 2: the ticket returned by step 1."
    },
    "identifier": {
      "type": "string",
      "description": "Step 1: the email address or phone number of the other account to verify."
    }
  }
}
    arguments 26 lines
  • buy_unlink_merchant auth-required never probed

    Disconnect a merchant — drops the saved session + link. The user must re-link (e.g. hosted connect) before shopping it again.

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant"
  ],
  "properties": {
    "merchant": {
      "type": "string",
      "description": "Merchant slug to disconnect (e.g. doordash)."
    }
  }
}
    arguments 12 lines
  • buy_connect auth-required never probed

    Connect a merchant for shopping. For merchants that need a real login (e.g. DoorDash) this opens a secure hosted browser session and returns a URL the user opens to log in; after they finish, call buy_connect_status with the pending_id to confirm. Merchants that need no login (e.g. Agentcard Flights) come back ready immediately. Use this instead of buy_link_merchant for hosted-login merchants. This tool pairs only with buy_connect_status and only tracks logins it started itself; a login link handed out by the conversational `buy` tool has no pending_id and is verified inside that same buy conversation (the user replies there, e.g. "done — I logged in").

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant"
  ],
  "properties": {
    "merchant": {
      "type": "string",
      "description": "merchant slug (e.g. doordash)"
    }
  }
}
    arguments 12 lines
  • manage_subscription auth-required never probed

    Manage a recurring meal/grocery SUBSCRIPTION (e.g. Locale) — NOT a one-time purchase, and no payment is taken (the subscription auto-bills the card on file at the merchant). action: 'menu_search' (browse the recurring menu; items flagged inPlan are covered by the plan), 'get_skip_dates' (list skipped/paused deliveries), 'skip'/'unskip' (one upcoming delivery date), 'set_skip_dates' (replace the full skip set; [] resumes all), 'update_setting' (change a setting). Locale settings: subscription_size (meals, e.g. 8), calorie_preference (low_calorie|both|moderate), diets (array), longevity_allergens (array), ingredient_allergies (array), default_window ('9am - 6pm'|'3pm - 7pm'|'9am - 12pm'), delivery_instructions (text). Link the merchant first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "merchant",
    "action"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "skip/unskip: one ISO delivery date (YYYY-MM-DD)"
    },
    "dates": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "set_skip_dates: FULL set of ISO dates to skip ([] resumes all)"
    },
    "limit": {
      "type": "number",
      "description": "menu_search: max items"
    },
    "query": {
      "type": "string",
      "description": "menu_search: term over the recurring menu (e.g. 'salmon'); '' lists everything"
    },
    "value": {
      "description": "update_setting: the new value (number, string, or array of strings)"
    },
    "action": {
      "enum": [
        "menu_search",
        "get_skip_dates",
        "skip",
        "unskip",
        "set_skip_dates",
        "update_setting"
      ],
      "type": "string",
      "description": "the management action"
    },
    "setting": {
      "type": "string",
      "description": "update_setting: the setting key (see description)"
    },
    "merchant": {
      "type": "string",
      "description": "merchant slug (e.g. locale)"
    }
  }
}
    arguments 51 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a65ccd69d99fe686/badge.svg)](https://brick.blue/agent/a65ccd69d99fe686)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on agentcard.sh 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.