depix-mcp

Non-custodial Pix payment gateway on the Liquid Network. An AI agent creates checkouts/products, reads transaction status, and manages support tickets — 22 tools. Non-custodial: no funds, no keys held.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://depix-mcp--depixapp.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "depix-mcp": {
      "url": "https://depix-mcp--depixapp.run.tools"
    }
  }
}

能力清单

工具	说明
create_checkout	Create a ONE-OFF payment (checkout) with a hosted payment page, on either settlement rail — paid once, short-lived. For a dated or recurring payment link (a "cobrança": rent, tuition, an instalment), use `create_product` with kind="charge" instead. Default `payment_method: "pix"` — the payer pays a Pix QR in any bank app, and `payer_tax_number` (their CPF/CNPJ) is required. `payment_method: "depix"` — the payer sends DePix wallet-to-wallet on the Liquid network to the merchant's dedicated address: there is no Pix QR (the response carries `depix` instead of `pix`), no payer document is used, the merchant may grant a discount, and the payment is confirmed on-chain — `approved` at the first confirmation (~1 minute) and `completed` at the second (~2 minutes). The depix rail requires the merchant to have it enabled, otherwise the API answers `depix_not_enabled`. Requires scope `merchant_write`. Amount is BRL cents (the face value, before any DePix discount).
get_checkout	Fetch a checkout by id (owner view). `payment_method` tells you which rail it settles on; a still-payable depix checkout also carries its `depix` payment instructions (address, exact amount, URI). Requires scope `merchant_read`.
list_checkouts	List checkouts with filters and pagination. Requires scope `merchant_read`.
simulate_checkout_payment	Mark a SANDBOX checkout as paid so you can observe checkout.completed. Live checkouts return sandbox_only. Requires scope `merchant_write`.
wait_for_checkout	Wait server-side for a checkout to reach a terminal status, emitting progress. One call — no client-side polling. Returns { status, terminal, timed_out }. Requires scope `merchant_read`.
create_product	Create a reusable product (fixed-price checkout template with a public page), or — with kind="charge" — a CHARGE (Portuguese: "cobrança"): a payment link with a due date and optional late fine/interest, for rent, tuition or an instalment. A charge is served at pay.depixapp.com/c/{id} and never appears on the merchant's public store. NOTE: `create_checkout` makes a ONE-OFF payment that is paid once and is short-lived; this tool with kind="charge" makes a STANDING one that has a due date and can recur. Requires scope `merchant_write`.
list_products	List products with filters and pagination. Charges are NOT included by default — pass kind="charge" to list them (each row then carries `charge_state` with the current cycle, days late and today's total) or kind="all" for both. Requires scope `merchant_read`.
get_product	Fetch a product by id with checkout aggregates. Requires scope `merchant_read`.
update_product	Partially update a product or charge (only provided fields change). A charge's due_date, recurrence and late fees are editable here; `kind` is not — it is fixed at creation. Requires scope `merchant_write`.
activate_product	Make a product purchasable again. Requires scope `merchant_write`.
deactivate_product	Hide a product from the public page and block new checkouts. On a CHARGE this also kills its live pay.depixapp.com/c/{id} link — anyone holding it sees "cobrança indisponível" and cannot pay. Reversible with activate_product. Requires scope `merchant_write`.
set_featured_products	Reconcile the pinned product set/order on the public page in one call (empty array clears all). Requires scope `merchant_write`.
list_product_checkouts	List checkouts created from a product. Requires scope `merchant_read`.
get_account	Identify the authenticated merchant (connection test). Requires scope `merchant_read`.
get_deposit_status	Read a deposit's status (read-only). Requires scope `wallet_read`. This MCP cannot create deposits (that is the SDK, F3).
get_withdrawal_status	Read a withdrawal's status (read-only). Requires scope `wallet_read`. This MCP cannot create withdrawals (that is the SDK, F3).
get_onboarding_status	Narrate what the account still needs to go live: an ordered ladder of steps (create the wallet, verify WhatsApp, deposit+convert+withdraw to verify, create the store), each with a plain PT+EN title and instruction to relay to the human, an absolute app deep link, and the current numbers. Composes the verification progress with a store probe, and — when every step is complete — triggers verification itself so the account never sits 'all green but not verified'. Read-first; the only write is that self-heal trigger.
update_merchant_profile	Update the store's LIGHT profile fields — business_name, logo_url, website, default_redirect_url, default_callback_url — via PATCH /api/merchants/me. Only the fields you pass change. The money-redirecting fields (liquid_address, split_address) are NOT here by design and cannot be changed with a key. Requires scope `merchant_write`.
get_vault_status	Read the account's position in the Cofre deposit-hold mechanism (read-only): whether it is active, how long a new deposit is held, the trust level, and the rolling receive cap with how much is left this window. Requires scope `wallet_read`.
list_webhook_logs	Read recent webhook delivery attempts (read-only): the event, the endpoint, the HTTP status it returned or the transport error, the attempt number and when it was sent — newest first. Pass `id` to fetch one delivery. Did my webhook arrive, and what did the endpoint answer?
open_support_ticket	Open a support ticket for a bug, unexpected behavior, or an account/payment problem. The body becomes the first message. A human replies within 1 business day — replies are NOT pushed to you: poll get_support_ticket to read them (check back in minutes, not seconds; this is not a live chat). For API or how-to questions, the docs (depixapp.com/docs and depixapp.com/llms.txt) usually answer instantly — prefer a ticket only when something is broken or account-specific. Up to 5 open tickets per account.
get_support_ticket	Fetch one of your tickets with its full message thread. Poll this to read the human's reply — support answers within 1 business day, so check back in minutes, not seconds. Returns 404 if the ticket does not exist or was opened by another session/key.
list_support_tickets	List the tickets you opened (this session/key), newest activity first. Use get_support_ticket to read a thread and poll for replies.
reply_support_ticket	Post a reply to one of your tickets. On an answered ticket this moves it back to awaiting a reply; on an auto-closed ticket within 7 days it reopens it. A human answers within 1 business day — poll get_support_ticket for the response (minutes, not seconds).
close_support_ticket	Close one of your tickets once you no longer need help. This is terminal — to continue later, open a new ticket.
attach_support_ticket_file	Attach ONE file to a ticket so the support team can see it — typically a diagnostic/log file or a screenshot that documents a bug. Provide the bytes base64-encoded in file_b64 (no data: URI prefix), up to ~3 MB, with content_type one of image/png, image/jpeg, image/webp, application/pdf, text/plain or application/json. The file is forwarded to a human on the support side; it is not stored or served back, so the result records only the filename and type. Attaching counts as a reply: an answered ticket returns to awaiting a reply, and an auto-closed ticket within 7 days reopens. If the response is attachment_unavailable, retry shortly or continue with reply_support_ticket.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。