Moneda

Check the health and status of the Moneda MCP server

無需輸入參數。

Search the Moneda knowledge base (FAQ) for answers to questions about Moneda's features, fees, security, accounts, earnings, deposits, withdrawals, legal info, and more. Use this whenever a user asks about how Moneda works.

List the FAQ table of contents: every category (slug, name) with each item's id and question. Use an id with get_faq_item for the full answer.

無需輸入參數。

Get all FAQ items in a specific category. Use the moneda://knowledge resource to discover available category slugs.

Get a specific FAQ item by ID, including its full answer and resolved related questions. Use this after search_knowledge or get_faq_category to drill into a specific question.

Get the user's account balances (USD Account, EUR Account, CHF Account, CAD Account, MXN Account, USD Earnings, EUR Earnings, USD Smart Earnings, EUR Smart Earnings), optionally filtered by currency. CHF, CAD, and MXN rows only appear for users in their staged rollouts (gated by ENABLE_CHFAU, ENABLE_CANADA, and ENABLE_MXNB). Balances are fetched live from the blockchain by default. If blockchain queries fail, returns the latest database snapshot with a notice. Check the 'source' field: 'live' means real-time blockchain data, 'snapshot' means historical data from the last periodic sync. Includes sparkline trend data from recent snapshots and current APY rates for earnings accounts.

Get the user's Moneda smart wallet address on Base network. IMPORTANT: Only supports USDC, EURC, CHFAU, CADD, and MXNB on Base — other tokens or chains will result in permanent loss of funds. For Moneda-to-Moneda transfers, prefer sharing @username (instant, feeless).

無需輸入參數。

Get transaction history including card programme activity. Standard format returns JSON; tax_export returns a compact CSV with full unmasked addresses, token contracts, vault tokens, sender/recipient details, and tax labels (Koinly/CoinTracker/TaxBit compatible). Use year for annual tax exports (up to 250 per request). Filter by typeGroup, type, category, currency, dates, counterparty, amount, status, hasNote, hasCategory, hasReceipt, and card. For card queries, pass `card` (matches a card by its last 4 digits like "1234" or by a substring of the card alias like "subscriptions"), `cardId` if you already have the UUID, or `typeGroup: "card"` for activity across all cards. CARD_* rows include merchantName, MCC, country, and last4.

Get spending grouped by transaction type group (transfer, exchange, deposit, withdrawal, earnings, topup, offramp) for a 7/30/90-day window. Includes period-over-period comparison. For finer breakdowns by user-assigned category, contact, or merchant, use get_spending_by_category / get_spending_by_contact / get_spending_by_merchant. (This tool was previously named get_spending_summary.)

Get the current exchange rate between two currencies

Get your lifetime accumulated savings from using Moneda — total fees Moneda covered on your behalf (sponsored network fees + on/off-ramp fees) plus your plan's fee discount vs the Standard plan. This is NOT a balance: never answer "how much have I saved" from wallet or vault amounts. Returns the total AND its three components, so you can say where the savings came from.

無需輸入參數。

List the user's bills (AP queue), ordered 'due-soon first' (dueDate ASC NULLS LAST, id DESC). Filter by `status[]` — defaults to `['PENDING']`. Cursor-paginated; pass `nextCursor` from the previous page back as `cursor` to advance. Each row carries the extracted merchant, total, currency, invoice number, and due date.

Fetch a single bill by id with full extracted detail — merchant (name, taxId, address), total, currency, due date, invoice number, vendor IBAN/BIC/routing/account, payment status, and a presigned `downloadUrl` valid for ~15 minutes.

Get the current APY (Annual Percentage Yield) rates for Moneda earnings products. Morpho Earnings is a DeFi lending vault and YO Smart Earnings is a higher-yield vault. USD and EUR have both Morpho and YO vaults; MXN has a Morpho-only vault (no YO). CHF and CAD are accepted at the parameter boundary for consistency but currently return empty (no yield vault on those currencies yet).

Get a daily time series of earnings and vault balance for a Morpho or YO vault account. Returns up to one year of UTC-day data points (timestamp, earnings, balance) plus totalEarnings and netDeposits summaries.

Update the authenticated user's display name

Rename a passkey so it is recognisable in the security screen (e.g. 'Work laptop'). Pass the passkey id from get_passkeys. Cosmetic only — it cannot add, remove, or weaken a credential. Send an empty label to clear it back to the provider name.

Set whether the user's conversations with Moneda AI may be used to train Moneda's own models (the Settings > Privacy toggle). enabled=false turns it off; enabled=true turns it back on. The choice applies to what the user sends from then on: messages sent while objected stay excluded even if it is turned back on. It does not change how Moneda answers the user, security logging, or quality measurement. Always on for the free Standard plan: turning it off needs a paid plan and is refused otherwise. Only call this when the user explicitly asks. Read the current value with get_settings (helpImproveMoneda).

Change the user's decimal separator (DOT = 1,234.56, COMMA = 1.234,56), or opt in or out of marketing and product-update emails and push notifications. Pass only what the user asked to change; at least one field. Security and transactional messages always send and cannot be turned off. Only call this when the user explicitly asks. Returns the settings after the change. Language and theme are app-only.

Get the user's current points balance from the rewards program

無需輸入參數。

Get the user's points activity history showing what actions earned or spent points

Get the user's unique referral code and referral count

無需輸入參數。

Get the list of users this user has referred to Moneda

無需輸入參數。

Get the user's virtual bank account details (IBAN and ACH), payment capabilities, and activation status. Minimum transfer: €1 for EUR (IBAN/SEPA) and $1 for USD (ACH).

無需輸入參數。

Get how much of the user's Iron virtual-account spending limit is left, per direction (deposit = money in, withdrawal = money out), on a rolling 52-week window. Also reports whether Iron is currently requesting enhanced due diligence (EDD). Crossing a limit does NOT reject the transfer: Iron PAUSES it and gives the user 24 hours to supply a Source-of-Wealth document, so check this BEFORE proposing a large deposit or withdrawal. `rfiRequired: true` means Iron has an open information request waiting on the user's answers (see get_information_requests). `missingRequirements` (only while `eddRequired`) lists the Iron requirement codes still outstanding, e.g. `kyc_questionnaire`, `kyc_proof_of_residence`: the user finishes them in the Moneda app at Settings > Features and limits. `threshold: null` means the customer has no enforced cap. Thresholds are personalised per customer — never assume a number, always read it here.

無需輸入參數。

List the compliance information requests (RFIs) Iron/MoonPay has sent the user about their virtual account: status, the open round's questions and any requested documents. Read-only. MoonPay requires the user to answer personally, so NEVER answer on their behalf or draft answers for them to paste: tell them to open the Moneda app at Settings > Features and limits and respond to the information request there. While a request is waiting on a response, transfers may be held.

無需輸入參數。

Get the date a US bank (ACH) transfer would actually settle. Accounts for Iron's 3:00 PM ET same-day cutoff, weekends, AND US federal bank holidays — a transfer sent the afternoon before Thanksgiving does not arrive the next day. Use this to answer 'when will my money arrive?' instead of saying 'next business day'. USD/ACH only; Iron publishes no equivalent cutoff for EUR/SEPA.

Get the user's contacts: Moneda users they interact with, saved external wallets, and saved bank accounts. Each wallet and bank entry has a contactAccountId field — pass it as the contactAccountId parameter to initiate_payment (transfer_contact_bank / transfer_contact_wallet). Use the contact's username (from the owner field or the username field) as contactUsername.

Get the user's app settings and preferences: language, currency, country, theme, notifications, biometrics, and display options.

無需輸入參數。

Get the user's recovery contacts and the people who have you as their recovery contact (guardian).

無需輸入參數。

Get the user's passkeys (security keys). target='WALLET' (default) lists the smart-account signing keys — id, label, provider, status, masked wallet address, creation date, kind ('primary' = the key from signup, 'backup' = an extra key added later as a second Safe owner), and onchainStatus (a 'pending' backup exists but cannot sign yet). target='LOGIN' lists the email-login credentials — id, label, status, masked credential id, device, last used, and provider when it could be identified (absent means unknown, including every credential registered before Moneda recorded it). Pass the id plus the same target to set_passkey_label to rename one. This does NOT report which key the app will use for the NEXT signature: that preference is stored only on the user's own device and is not readable through any API, so never infer it from kind or ordering.

Get the user's saved external wallets and bank accounts for withdrawals/off-ramping. Each entry has an accountId field — pass it as the accountId parameter to initiate_payment (transfer_account). These are NOT the user's Moneda wallet — use get_wallet instead to get the user's actual Moneda smart wallet address.

無需輸入參數。

Assign a spending category to a transaction. Identify the transaction by its transactionHash from get_transactions.

Add or update a personal note on a transaction. Identify the transaction by its transactionHash from get_transactions. Maximum 140 characters.

Assign spending categories to multiple transactions at once. Accepts up to 25 items. Each item maps a transactionHash to a category. Returns per-item results. Use with get_transactions hasCategory=false to find uncategorized transactions first.

Add or update notes on multiple transactions at once. Accepts up to 25 items. Each item maps a transactionHash to a note (max 140 chars). Returns per-item results. Use with get_transactions hasNote=false to find unannotated transactions first.

Add a crypto wallet to the user's saved external accounts. IMPORTANT: The wallet must support USDC, EURC, CHFAU, CADD, and MXNB on the Base network. Sending other tokens or using other chains will result in permanent loss of funds. The user MUST confirm they understand this before the wallet is saved — set confirmed=true only after explicit user acknowledgment.

Add a bank account to the user's saved accounts. For EU: provide IBAN (and optionally BIC). For US: provide accountNumber, routingNumber, and accountType (CHECKING or SAVINGS). US banks support ACH transfers only. Bank capability is verified before saving.

Register an external (non-Moneda) contact with their details. EU Travel Rule requires first name, last name, and country of residence. At least one wallet address or bank account must be provided. For wallets, the user must confirm Base network USDC/EURC/CHFAU/CADD/MXNB support before saving.

Add a Moneda user to your contacts by their username. If the contact already exists but was deactivated, it will be reactivated.

Search for Moneda users by username, display name, full email, or phone number. Respects user privacy settings — users who have disabled search visibility for specific fields will not appear in results matching those fields. Returns username and display name for matching users.

List the banks Koywe supports for a LATAM country, used when registering a third-party or first-party bank account that requires an explicit bank code (Colombia/PSE, Chile/CLP_BANK, Bolivia/BOB_BANK). Each bank entry has: name (human label), value (Koywe entity code — pass back as bankCode), and domain (for logo display). Mexico/Argentina/Peru also return banks but those rails resolve the bank from the account number automatically.

List the country, currency, and rail combinations Moneda can pay out to. Each entry includes the required fields you'll need to collect from the user before calling add_bank, add_contact_external, or initiate_payment. The output is provider-agnostic — don't branch on which underlying processor handles each rail. Pass an optional `countrySymbol` to filter (e.g. 'BR' returns only Brazilian PIX). Empty result for a country means Moneda doesn't currently support it.

Preview the cost, FX rate, and final amount for moving money between two currencies. Provide exactly one of `amountIn` (what the user sends) or `amountOut` (what they want to receive). Returns the quote ID, exchange rate, fee, and how long the quote stays valid. Use this BEFORE initiate_payment so the user can confirm the rate. Routes internally based on the currency pair — agents don't need to know which provider handles which corridor.

Send money to someone else (a Moneda user, a contact, or an external bank/wallet). Creates a payment request that requires user approval in the Moneda mobile app. Not for converting between the user's own currencies: use initiate_currency_exchange for that. Look up the recipient first via search_users, get_my_accounts, or get_contacts. Check balance with get_balance before calling. After calling, poll get_payment_status. Bank transfers require an active Iron account and a registered autoramp.

Convert money between two of the user's own currency accounts (e.g. USD to EUR). Nothing leaves the user; to pay or send to anyone, use initiate_payment instead. Creates a request the user approves in the Moneda mobile app; the destination is the user's own account in toCurrency. Check balance with get_balance first. After calling, poll get_payment_status.

Propose a RECURRING payment (e.g. $50 monthly to a Moneda user or a contact's Base wallet). Creates a draft the user reviews, approves and signs with their passkey in the Moneda mobile app; nothing is sent until then and you never schedule or move funds yourself. Not for one-off payments: use initiate_payment. Look up the recipient first (search_users, get_contacts). The draft expires after 48 hours if the user does not approve it.

Buy or sell a crypto asset (e.g. cbBTC for Bitcoin, WETH for Ethereum) with the user's own balance. Not for sending money (use initiate_payment) or converting between currencies (use initiate_currency_exchange). The route/venue is chosen by the server. Creates a request the user reviews at the live price, approves and signs in the Moneda mobile app. After calling, poll get_payment_status.

Buy a Base token that is not in initiate_crypto_trade's catalogue, by contract address, spending the user's own USD, EUR, CHF or MXN balance. Use initiate_crypto_trade for catalogue assets (cbBTC, WETH, …). The token must be tradeable on Base via LiFi. Creates a request the user reviews at the live price, approves and signs in the Moneda mobile app. After calling, poll get_payment_status.

Move the user's own money into or out of an earnings vault: DEPOSIT from a currency account into Earnings (MORPHO) or Smart Earnings (YO), WITHDRAW back out. Not for sending money (use initiate_payment), converting currencies (use initiate_currency_exchange) or trading (use initiate_crypto_trade). YO has USD and EUR vaults; MORPHO has USD, EUR and MXN. Check balances with get_balance and rates with get_apy_rates first. Creates a request the user approves and signs in the Moneda mobile app. After calling, poll get_payment_status.

Check the current status of a payment request. Use this to poll for approval after calling initiate_payment. Terminal statuses: COMPLETED, FAILED, EXPIRED, REJECTED.

Pay for a resource using the x402 protocol (HTTP 402 Payment Required). When an API returns HTTP 402 with x402 paymentRequirements, use this tool to initiate the payment. The payment requires user approval in the Moneda app before it executes. Parameters map to x402 paymentRequirements fields: - payTo: the recipient wallet address from the 402 response - amount: the payment amount (e.g. "0.01") - currency: USD or EUR (maps to USDC or EURC on Base) - resource: the URL being paid for (shown to the user for context) - network: must match the Moneda deployment ("base" or "base-sepolia") After calling this tool, poll get_payment_status every 10-15 seconds until a terminal status (COMPLETED, FAILED, EXPIRED, REJECTED). On COMPLETED the funds settle on-chain to payTo. Note: Moneda does not yet emit the x402 X-PAYMENT proof header, so a bare retry only unlocks the resource if its facilitator accepts on-chain settlement as proof.

List the crypto held in a Safe that can be sent out: balance (in the token's smallest unit), decimals, USD value where one can be found, and whether the token is allowlisted or merely discovered on LiFi's Base list. Covers the main account, vaults and joint accounts. Pass the returned contract address to initiate_crypto_send — never the symbol, because two tokens can claim the same one. `enabled: false` means crypto transfers are off for this account, which is not the same as holding nothing.

Send crypto out of a Safe — the main account, a vault or a joint account — to a Moneda contact or a raw Base address, for any token the account holds. Not for selling a token (use initiate_crypto_trade), buying one (initiate_token_buy) or sending money (initiate_payment). Amounts are in the token's own smallest unit (atoms): call list_sendable_crypto first and use its `decimals` and `address`. Creates a request the user reviews, approves and signs in the Moneda mobile app — nothing moves until they do. After calling, poll get_payment_status.

List the user's sub-accounts (vaults / nested Safes). Excludes CLOSED vaults by default; pass includeClosed: true to see archived ones too. Returns id, name, status, type, and the on-chain child Safe address.

Get one sub-account by id with full detail — name, status, type, members, parent + child Safe addresses, deployment index, close timestamp.

Read on-chain balances for a sub-account's child Safe. Pass currency (USDC / EURC / CHFAU / CADD / MXNB) to filter to a single token; omit to get every enabled token. Balances are returned as raw bigint strings — 6 decimals for USDC/EURC/CHFAU/MXNB, 18 for CADD.

Aggregate wealth across the user's main account + every live vault. Returns per-leg breakdown (wallet + Morpho + YO for main; wallet-only for vaults) plus per-currency totals (USDC, EURC, CHFAU, CADD, MXNB) and combined totalUsd/totalEur grand totals. USDC/EURC are cross-converted using the on-chain Aerodrome rate; CHFAU, CADD and MXNB keep their own columns but are also folded into totalUsd/totalEur using their fiat rates (MXNB via its Aerodrome pool). MXNB includes the Juno MXNB Prime Morpho vault. `stocksUsd` is the value of stocks and ETFs in the brokerage account at the latest delayed quote, and `cryptoUsd` the value of crypto held in the main account and every vault at the current reference price (both 6-decimal USD; null means it could not be priced, not zero). The app's Total wealth adds both on top of the currency totals; the app prices crypto at what selling now would return, so its figure can differ slightly. `stockPositions` and `cryptoPositions` list each held asset (symbol, quantity in whole units, valueUsd, costUsd, realizedUsd): use them for 'how much crypto do I hold', 'what is my bitcoin worth' (cbBTC) or 'what stocks do I own'. `costUsd` is what the user paid for the position, so valueUsd minus costUsd is how much they are up or down; null means the cost is not on record (for example tokens received from outside), so do not report a gain or loss for it. `realizedUsd` is the profit or loss the user already locked in by selling part of that position (negative for a loss), separate from the unrealized figure: quote it for 'how much have I made selling X'; null means it is not on record, so say so rather than zero. `closedStockPositions` lists stocks and ETFs the user has sold all of, each with `realizedUsd` (what selling it made or lost): use it for 'how did my Tesla trade end up' or 'what have I made on stocks I sold'. `closedCryptoPositions` is the same for crypto the user bought in the app and has fully sold; a token they moved in or out some othe

無需輸入參數。

List the OPEN spend / withdraw / membership / threshold requests on a joint account that needs multiple approvals (M-of-N). Returns each request's type, status, amount, how many approvals it has out of the threshold, and who proposed it. Read-only: voting and executing need the user's passkey on their device.

Get one joint-account request by id, including the per-member approval list (who approved, who rejected, and when). Read-only.

Move money from the user's main account INTO one of their sub-accounts. Not for paying someone (use initiate_payment) or converting currencies (use initiate_currency_exchange). Creates a request the user approves in the Moneda mobile app; nothing happens until then. After calling, poll get_payment_status.

Move money from a sub-account back to the user's own main account. Not for paying someone from a sub-account (use initiate_payment with source.kind=sub_account). Single-signature sub-accounts only; for a joint account use propose_sub_account_multisig_proposal. Creates a request the user approves in the Moneda mobile app; nothing happens until then. After calling, poll get_payment_status.

Swap inside a sub-account between a currency (USD, EUR, CHF, CAD, MXN) and a crypto asset (e.g. cbBTC), or between two currencies. Funds stay in the sub-account. Not for the main account (use initiate_crypto_trade or initiate_currency_exchange). Creates a request the user approves in the Moneda mobile app; nothing happens until then. After calling, poll get_payment_status.

Freeze a sub-account the user created, blocking its spending. Unfreezing can only be done in the app. Creates a request the user approves in the Moneda mobile app; nothing happens until then. After calling, poll get_payment_status.

Open a SPEND or WITHDRAW proposal on a joint account that needs more than one approval. This only creates the proposal; co-owners still approve and execute it in the Moneda app. For single-signature sub-accounts use propose_sub_account_withdraw or initiate_payment with source.kind=sub_account. Creates a request the user approves in the Moneda mobile app; nothing happens until then. After calling, poll get_payment_status.

Get the user's CURRENT subscription plan and how it is billed. Returns hasLiveSubscription, status (TRIALING/PENDING_FIRST_CHARGE/ACTIVE/PAST_DUE/CANCELLED), planType (STANDARD/PREMIUM/ULTRA), billingProvider (ONCHAIN/STRIPE/APP_STORE/PLAY_STORE), billedTo ('balance' | 'card' | 'app_store'; app_store plans are cancelled or changed in the user's Apple or Google account settings, not in Moneda), balanceFundsRenewal (true only for ONCHAIN — a non-zero stablecoin balance is needed for the next renewal; false for STRIPE card plans, where the wallet balance is irrelevant), currency, billingPeriod, periodEnd, cancelledAt. Use this before advising on a low/zero balance: a 0 balance only threatens the subscription when balanceFundsRenewal is true.

無需輸入參數。

List the user's subscription charge history (SUBSCRIPTION_CHARGE rows from the keeper cron), newest first. Cursor-paginated — pass `nextCursor` from the previous page back as `cursor` to advance. Each row carries the plan tier, billing period (MONTHLY/ANNUAL), amount (lower-units string), currency, status, on-chain transaction hash, billing period start/end, and the invoice number (null until the user generates the invoice). Use get_subscription_invoice to generate the PDF for a charge.

Generate (idempotently) the ZUGFeRD plan invoice PDF for a single subscription charge and return a 1-hour presigned download URL. First call allocates the invoice number (YYYY-NNNNNN), renders the PDF/A-3 with embedded EN 16931 XML, and uploads to S3; subsequent calls return a fresh presigned URL for the existing row. The user must own the underlying charge. Returns `{ invoiceNumber, downloadUrl }`.

List the user's in-app notifications, newest first. Pass filter='unread' to scope to unread items (use this to answer 'do I have any new notifications?'). Each notification has a `type`, an optional `deepLink`, and a `metadata` JSON blob whose shape varies by type. Returns up to `limit` items (default 20, max 50) with a `nextCursor` for pagination.

Number of unread in-app notifications for the user. Cheaper than list_notifications when the agent only needs the count to answer 'do I have anything new?'.

無需輸入參數。

Read one message from Moneda (a notification with type MONEDA_MESSAGE, id from list_notifications): title, body, tone, optional button, attached documents (by index), and `reply`, which is null when no reply is asked for, else says whether a document is none/optional/required. `repliedAt` is set once the user has replied.

Get a download link (valid 10 minutes) for a document Moneda attached to a message. `index` comes from the message's `attachments` list in get_moneda_message.

List the replies the user sent to messages from Moneda, newest first: text, the message title, and the attached document's name if any. Returns up to `limit` items (default 20, max 50) with a `nextCursor` for pagination.

Step 1 of 2 for attaching a document to a reply to a message from Moneda (only when get_moneda_message shows `reply.attachment` optional or required). Returns a presigned S3 PUT URL (`uploadUrl`), a signed `uploadKey` and a literal `curlCommand` to run in your code sandbox; the file bytes go straight to S3 and never enter the conversation. After the PUT succeeds, pass `uploadKey` to reply_to_moneda_message. PDF, JPEG or PNG, max 5 MB; the slot expires in 15 minutes. Only upload a file the user chose for this reply.

Send the user's reply to a message from Moneda that asks for one. The reply is delivered to the Moneda team, so only send text the user wrote or explicitly approved word for word, never text you composed on your own, and show it to the user before sending. One reply per message (max 600 characters); it cannot be edited afterwards, only undone within 10 seconds (undo_message_reply). When the message takes a document, first stage it with request_message_reply_upload and pass the `uploadKey` plus the file's display name.

Undo a reply the user just sent to a message from Moneda. Only call this when the user asks to undo, and only within 10 seconds of sending (until the reply's `undoableUntil`); afterwards it fails with "too late". The reply and its document are deleted and the message asks for a reply again.

List the user's transaction receipts (PDFs, images, structured invoices), newest first. Each entry carries extracted summary fields (merchant, total, date, currency) plus the linked transactionId when attached. Use `transactionHash` (from `get_transactions`) to scope to one transaction, `needsReview=true` to find rows flagged for manual review, and `status` to filter by lifecycle state. Default page 20, max 100.

Fetch a single receipt by id with full extracted fields (merchant, total, currency, tax breakdown, line-item count) plus a presigned `downloadUrl` valid for ~15 minutes. Use this when the user asks about a specific receipt or to surface the file URL to the LLM context.

List the parsed line items on a receipt — description, quantity, unitPrice, totalPrice, taxRate, and category. Useful for spend-by-product breakdowns or itemized review of an invoice.

Search across every parsed line item the user has uploaded (case-insensitive substring on description + normalized description). Returns matching items, total count, and aggregate spend grouped by currency. Optional `category`, `startDate`, and `endDate` further narrow the window. Use this for questions like 'how much did I spend on cappuccinos this year?'.

List German hospitality-receipt (Bewirtungsbeleg) overlays attached to the user's transactions. Each row carries the underlying transactionId, date, location, occasion, total/tip/subtotal split, deductible vs non-deductible amounts, and signing state. Pass `transactionHash` (from `get_transactions`) to scope to one transaction. Default page 20, max 100.

List self-issued substitute receipts (Eigenbeleg) — used when the original receipt for a transaction was lost or never issued. Each row carries the linked transactionId, recipientName, amount, reason, and signing state. Pass `transactionHash` (from `get_transactions`) to scope to one transaction. Default page 20, max 100.

Step 1 of 2 for uploading a local receipt file. Returns a presigned S3 PUT URL (`uploadUrl`), a signed `uploadKey`, and a literal `curlCommand` to execute in your code sandbox to stage the file. The file bytes are sent directly to S3 — they never enter the conversation context. After the curl PUT succeeds, call `finalize_receipt_upload` with the returned `uploadKey` to run OCR + matching. Use this for any local file (PDF, JPEG, or PNG, max ~5 MB).

Step 2 of 2 for uploading a local receipt file. Pass the `uploadKey` returned from `request_receipt_upload` AFTER you've executed the `curlCommand` to PUT the file to S3. Validates the staged file, runs OCR + LLM extraction, attempts to auto-match to an existing transaction, and persists line items. Returns `receiptId`, optional `billId` (for invoice-shaped docs), and `matched`/`suggested`/`transactionId`.

Import a receipt directly from an https:// URL (S3, Drive shared link, public file host, etc.). The server fetches the file behind an SSRF guard (rejects private IPs, Moneda infra, and non-https), validates it, then runs OCR + matching. Single tool call, no sandbox needed. Use this when the receipt is already accessible at a URL.

Re-run the OCR / LLM extraction pipeline on an existing receipt and return the refreshed fields. Use this when the user reports incorrect extraction or after a model upgrade. Refuses DELETED rows and rows without a stored file. Synchronous — the response carries the post-extraction snapshot.

Permanently delete a receipt and its stored file. This is a HARD delete — the row, its line items, and any Bewirtungsbeleg/Eigenbeleg overlay go with it, and there is no undo and no recycle bin. Confirm with the user before calling. To move a receipt to a different transaction use detach_receipt + attach_receipt instead; deleting loses the extraction.

Mark a receipt as a partial payment: the document covers more than this one payment (a deposit or instalment against a larger invoice), so its total differing from the transaction amount is expected. Replaces the `amount_mismatch` review reason with `partial_payment` so the receipt stops warning; the flag survives a reparse. Does not change any amounts. Check with the user first; only use it when get_receipt shows an amount mismatch the user confirms is intentional.

Correct a receipt's top-line amounts when the scan read them wrong: total, subtotal, tax amount, tax rate and tip. Each field is optional: omit it to leave it unchanged, pass null to clear it. At least one field is required. taxRateValue is a percentage (19 for 19%, not 0.19). Only the stored amounts change; a later reparse_receipt re-extracts and overwrites them. Use values the user gave or confirmed. Returns the receipt's amounts after the update.

File an unattached receipt against a transaction. A transaction holds at most ONE receipt, so this returns a conflict if another is already attached — detach that one first. Also clears any pending match suggestion, since the user has now decided.

Unlink a receipt from its transaction, leaving the receipt itself intact as an orphan. Use this to correct a wrong match, or to free a transaction so a different receipt can be attached. Does NOT delete anything.

Accept the matcher's suggested transaction for a receipt, promoting the soft suggestion to a real attachment. Suggestions exist when the match score was too low to attach automatically — read `suggestedTransactionId` / `suggestedMatchScore` from get_receipt and check the suggestion with the user before confirming.

Dismiss the matcher's suggested transaction for a receipt. The receipt stays an unattached orphan and stops being offered against that transaction. Use attach_receipt afterwards if you know the correct one.

List the email addresses set up for ZK email-based account recovery. Returns id, email, weight, status (pending/invited/accepted/declined/removed), and timestamps. Defaults to the user's main account when accountId is omitted.

Get one recovery email's full detail by id — email, weight, status, timestamps, notes, and the on-chain account address it protects.

Get the recovery configuration for an account: accepted recovery emails, total weight, and the threshold required to approve a recovery. The threshold is a fixed number that must match the on-chain Universal Email Recovery Module config.

Get the most recent ZK email recovery request snapshot for an account. Returns hasActiveRecovery: false when no recovery exists or the latest is in a terminal state (cancelled/completed/expired); otherwise returns recovery details including approved/pending recovery emails (anonymized as a***@domain) and time until executable. Reads from DB only — agents tolerate the slight lag while the cron syncs on-chain state.

Get daily spending totals for a stablecoin over a window. Returns one data point per UTC day with non-zero spending. Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

Get spending grouped by user-assigned transaction category over a window. Transactions without a category land in an 'UNCATEGORIZED' bucket. Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

Get the total amount sent to a single recipient (Moneda user, external bank, or external wallet) over a window. Identify the recipient by their account ID (recipientAccountId). Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

Get spending grouped by recipient/merchant. Each Moneda user gets their own bucket; off-ramps share a single bucket per type (bank-withdrawal, external-wallet, coinbase, wallet-connect). Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

Compare total spending across two arbitrary windows (e.g. this month vs last month, year-over-year). Returns absolute and percentage deltas; deltaPct is null when previous total is 0. Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

List the underlying spending transactions for a window. Optionally drill down into a category bucket (bucketKind='category', bucketId=CategoryType or 'UNCATEGORIZED') or a merchant bucket (bucketKind='merchant', bucketType=..., bucketId=user UUID for type='user'). Paginated via take/skip. Amounts are in currency units (26.5 means 26.50), like `get_transactions`.

Create a scoped autonomous payment session bound to your agent. The user pre-funds a dedicated child Safe and installs an on-chain spending policy (single pinned recipient, per-execution and per-period caps) with a passkey in the Moneda app. After that you can call agent_execute_payment repeatedly within the policy — no per-payment approval. This call does NOT activate the session: it returns a counterfactual child Safe address and an activation deep link the user must open in the Moneda app. Poll get_agent_session until status is ACTIVE before executing.

Execute a payment to an ACTIVE agent session's pinned recipient, within its on-chain spending policy — no per-payment user approval. The recipient and amount must satisfy the session's allowlist and per-execution / per-period caps, and the child Safe must hold enough balance. For safe retries pass a stable idempotencyKey: retrying with the SAME key returns the original transaction instead of double-spending. WITHOUT an idempotencyKey, retries are only de-duplicated within a ~30s window — a delayed retry (e.g. after a bundler/network timeout) could send a second payment. Call get_agent_session first to confirm the session is ACTIVE and check remainingPeriodCap.

Get one agent session's full detail by id: status, spending policy, remaining period cap, and the 5 most recent executions. Poll this after create_agent_session until status is ACTIVE.

List your scoped autonomous agent sessions, newest first, with status, policy, remaining period cap, and expiry. Filter by status to find ACTIVE sessions ready to execute against.

Revoke an agent session. This immediately halts all further execution on the backend (the execute path only runs ACTIVE sessions). The on-chain session remains installed until the user completes the uninstall in the Moneda app, but no payments can be made through it in the meantime. Use this when the agent is done with the mandate or the user asks to stop it.

List the user's active login sessions (signed-in devices and clients: mobile app, web, CLI, API) and connected agents (MCP integrations). Use this to answer 'what devices am I signed in on?' or before terminating a session. Each login session has an `id` (pass to terminate_session), a `type`, device/location info, and `lastActive`. Each connected agent has an `id` (pass to disconnect_connected_service) and `isThisConnection: true` marks the agent making this call.

無需輸入參數。

Terminate one login session by id (from list_active_sessions). The device is signed out immediately and cannot renew. Returns { success } — false means the session was already gone or isn't the user's.

Terminate all of the user's login sessions on other devices (every signed-in app/web/CLI/API session). Does NOT disconnect agent connections — use disconnect_connected_service for those. Returns { revoked } = how many were terminated.

無需輸入參數。

Disconnect a connected agent (MCP integration) by id (from list_active_sessions) or by its OAuth client id. Revokes its access immediately. If you disconnect the agent making this call, this connection ends.

List the API keys on the account: name, prefix (first 12 characters), scopes, last use, expiry, and whether each is still active. The secret itself is stored hashed and is never returned here — it is shown only once, when the key is created.

無需輸入參數。

Create an API key for a script, the CLI, or an integration. Returns the secret ONCE — it cannot be retrieved again, so hand it to the user immediately and tell them to store it somewhere safe. Maximum 10 active keys. The key can only carry scopes this connection already holds, and payment scopes are never available on an API key.

Revoke an API key by its id (from list_api_keys). The key stops working on its very next request. Irreversible — a new key must be created to restore access.

Redeem a CONFIRMED on-chain charge for prepaid AI usage credits. Provide the transactionHash of a completed transfer you (the user) sent to the Moneda treasury tagged as a usage-credit purchase. The amount is read from the verified on-chain charge — never from input — converted to USD budget with the standard markup, and granted exactly once (idempotent on the hash, so re-calling is safe).

Set (or clear) the monthly spend limit on AI usage credits — the ceiling on how much of the prepaid balance may be consumed per calendar month (resets the 1st, UTC). Pass a USD amount to cap spending, or null to remove the cap (unlimited). Idempotent: setting the same value twice is a no-op.

Read the config for redeeming Moneda Points into AI usage credits: the points-per-$1 rate, the minimum redemption, the monthly cap, the user's current points balance, and how much of the monthly allowance is left. Call this before redeem_points to price and gate a redemption.

無需輸入參數。

Redeem the user's Moneda Points for prepaid AI usage credits. Spends points (a negative points transaction) and grants the matching AI budget atomically. Enforces the minimum, the sufficient-balance check, and the monthly cap (see get_points_redemption_config). Pass a stable requestId (uuid) held across retries when you can: retrying with the same value is a no-op (returns granted:false). Omitting it is safe. The server derives the key from (user, points, 30s window) rather than minting a random one, so a retry still dedupes.

Check what the user may currently do with tokenized equities (dShares): whether they can trade, which regulatory jurisdiction they are onboarded under, and — if they cannot trade — the ordered list of reasons why. Call this before proposing any stock purchase so the user is told what to fix rather than hitting a failure at approval time.

無需輸入參數。

For a US-jurisdiction user, list what is still outstanding before their brokerage account can be opened: missing profile answers, unaccepted disclosures, and whether a taxpayer id is on file. Returns field NAMES and counts only, never the user's answers. Regulatory disclosures and attestations can only be completed by the user in the Moneda app — this tool tells you what to explain and where to send them, it does not let you supply any of it. A non-US user gets an empty, already-complete result.

無需輸入參數。

Is a stock market open, and when does it change? Defaults to the US. Pass exchange (an EODHD code: XETRA, F, LSE, PA, AS, BR, LS, MI, MC, SW, CO, ST, HE, OL, VI, IR) or a symbol with that suffix (SAP.XETRA) for a European exchange. Returns the current session (pre_market, open, after_hours or closed; European exchanges have only open and closed), whether today is a trading day, any holiday or early close, the trading day's windows as ISO instants, and the next session change. Render the instants in the user's own timezone.

Companies that have filed with the SEC to go public in the US (S-1 or F-1) and have not listed yet: name, stage (filed, priced or listed), proposed ticker, website, and first and latest filing dates. Use for "what IPOs are coming up?" or "is X going public?". Nothing on the list can be bought until it lists; to follow one and be alerted when it prices, send the user to the IPO page under Invest in the Moneda app. Returns available:false when market data is off for the user.

無需輸入參數。

How many commission-free stock trades the user has left this window, without quoting an order. The window steps from their own subscription anniversary, not the calendar month, so quote resetsAt rather than a day of the month. If degraded is true the count could not be read: say so, never state it as fact.

無需輸入參數。

List the user's crypto conditional orders (LIMIT / STOP_LOSS / TAKE_PROFIT / TRAILING_STOP, settled via CoW), newest first. Each has status (PENDING_ACTIVATION / ARMED / PUBLISHED / FILLED / CANCELLED / EXPIRED), side, assetSymbol, triggerPrice or trailPercent, raw-unit sellAmount / minBuyAmount, expiresAt and skipReason (why the keeper last did not act, e.g. insufficient_balance). Orders can only be created in the Moneda app.

無需輸入參數。

Get one crypto conditional order by id, with its full status, trigger, amounts and fill details.

Cancel a crypto conditional order rule: every open repeat (PENDING_ACTIVATION, ARMED, PUBLISHED or WAITING) of the order's rule is cancelled, so passing any repeat's id stops the whole repeating rule. A PUBLISHED order is live in the CoW order book: it is withdrawn on-chain first, then marked CANCELLED; if the withdrawal fails the order stays live and the call errors (retry). Filled, cancelled or expired orders return a conflict error. Confirm with the user before calling.

Fetch complete account overview in one call: balances, recent transactions (last 7 days), and current APY rates. Use this instead of calling get_balance + get_transactions + get_apy_rates separately.

無需輸入參數。

Fetch balance check data in one call: all account balances, exchange rates, and APY rates. Use this instead of calling get_balance + get_exchange_rate + get_apy_rates separately.

無需輸入參數。

Fetch comprehensive financial summary data in one call: balances, recent transactions (10), APY rates, and exchange rates. Use this instead of calling 5+ individual tools.

無需輸入參數。

Fetch points and referral data in one call: points balance, recent activity, referral code, and referees. Use this instead of calling get_points_balance + get_points_activity + get_referral_code + get_referees separately.

Fetch earnings overview data in one call: earnings vault balances, APY rates, and recent earnings transactions. Use this instead of calling get_balance + get_apy_rates + get_transactions(typeGroup=earnings) separately.

無需輸入參數。

Fetch security checkup data in one call: passkeys, recovery contacts, and security-related settings. Use this instead of calling get_passkeys + get_recovery_contacts + get_settings separately.

無需輸入參數。

Fetch all account setup data in one call: wallet address, Moneda account balances, virtual bank accounts, and saved external accounts. Use this instead of calling get_wallet + get_balance + get_virtual_accounts + get_my_accounts separately.

無需輸入參數。

Fetch payment readiness data in one call: KYC status, virtual accounts, external accounts, contact count, and balances. Use this instead of calling 5 individual tools to check payment readiness.

無需輸入參數。

Fetch spending analysis data in one call: spending by type group, daily totals, and category breakdown for a period. Use this instead of calling get_spending_by_type_group + get_daily_spending + get_spending_by_category separately. All totals are in USDC units (26.5 means 26.50).

Generate a PDF balance statement of your activity (opening/closing balances, transactions with home-currency values, fees, FX rates) for a tax year or date range. Async: returns a requestId immediately — poll get_statement_status until it is READY to get a time-limited download link. Not tax advice.

Check the status of your most recent balance-statement request. When READY, returns a time-limited PDF download URL. Not tax advice.