Rozo Checkout
Pay OpenRouter and Coinbase payment links with USDC, USDT, ETH, BNB, POL, SOL or BTC Lightning.
사용해야 할까요
품질 및 안전성
발견 사항 (5)
- HIGH
- MEDIUMsupported_coins에서
- MEDIUMcreate_deposit_order에서
- MEDIUMstellar_wallet_get_signing_request에서
- LOWstellar_wallet_get_signing_request에서
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"checkout": {
"url": "https://mcp.rozo.ai/mcp?src=registry"
}
}
}원격 엔드포인트
https://mcp.rozo.ai/mcp?src=registrystreamable-http할 수 있는 일
도구 목록
도구 (10)
🟢supported_coins
Answers which cryptocurrencies and chains can pay an OpenRouter credit top-up or another AI service invoice through Rozo Checkout: USDC and USDT on Ethereum, BNB Chain, Polygon, Arbitrum and Solana; USDC on Base and Stellar; native ETH (Ethereum, Base, Arbitrum), BNB, POL and SOL; BTC over Lightning; USDT and TRX on TRON (Beta), USDT on TON. Returns each chain id, token symbol and token decimals (TRON and TON rows carry route "tron_ton_alpha", a beta flag and their fee wording), plus webOnlyRoutes: coins served only on checkout.rozo.ai pages. Static list, needs no payment link and makes no network call; quote_invoice reports which of these a specific invoice accepts. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.
입력 스키마
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢quote_invoice(url)
Answers what a specific OpenRouter top-up or other AI service invoice charges, whether it can still be paid through Rozo Checkout, and which coins can pay it. Takes the payment link URL and returns the merchant, invoice amount, callerPays (the total USD charged: invoice plus the Rozo service fee; also callerPaysAtomicUsdc in 6-decimal units), the breakdown original (invoice face value), serviceFee and feeBps (fee rate in basis points, 100 = 1%), the link expiry, payability and supportedSources: the coins THIS invoice can be paid with. The exact amount to send in a given coin, which adds bridge and network fees, or the FX spread on a native coin, on top of callerPays, comes from create_deposit_order. Offer a native coin (ETH, BNB, POL, SOL) only when it appears in supportedSources. Creates nothing and moves no funds.
입력 스키마
{
"type": "object",
"properties": {
"url": {
"type": "string",
"maxLength": 512,
"description": "Payment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."
}
},
"required": [
"url"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡create_deposit_order(url, chainId, tokenSymbol, email)
Creates a one-time deposit order; you pay from your own wallet. Returns the deposit address (or Lightning invoice), the exact amount to send (also in base units with the token decimals), any required memo, the expiry and the rozoPaymentId. This server holds no keys and sends nothing. Send exactly the amount, on exactly that chain and token, before expiresAt. An unfunded order simply expires at no cost. For a native coin the result also carries quoteExpiresAt (the end of the price lock, which expiresAt equals): send the exact coin amount before it. For TRON or TON the result carries the receiving address, the exact amount, the TON comment when one is required, the fees and expiresAt, and no rozoPaymentId: track it with payment_status and the url. Native coins (ETH on Ethereum, Base, Arbitrum; BNB on BNB Chain; POL on Polygon; SOL on Solana) are exact-out like Lightning: the order states the exact coin amount, priced at the current rate plus an FX spread on top of the service fee, and that price holds only until quoteExpiresAt. Native ETH, BNB and SOL take OpenRouter invoices of up to 10,000 credits (about $10,500; refused only above $12750 of callerPays, service fee included, so a 10,000-credit invoice always fits). POL is capped at $3500 (native ETH on Ethereum needs at least $1), and a native coin is offered only when quote_invoice lists it for that invoice. ZEC on Zcash is not available through this server: send a payer holding ZEC to https://checkout.rozo.ai/zec. On-chain BTC (the Bitcoin network, Beta) is not available through this server either; the lightning chain id here is Bitcoin Lightning only. Send a payer who wants to pay on-chain to https://checkout.rozo.ai/btc-onchain. USDT and TRX on TRON (Beta) and USDT on TON go through a dedicated route (route "tron_ton_alpha", the same backend as checkout.rozo.ai/tron and /ton): create_deposit_order returns one exact amount, a receiving address and, on TON when required, a six digit comment, valid until expiresAt. TRON Beta charges 1% with a $0.30 minimum; TON charges 1%; the exact fees come with the order. These orders have no rozoPaymentId: check them with payment_status and the payment link url. Availability can change; quote_invoice reports whether TRON and TON are open for a given invoice.
입력 스키마
{
"type": "object",
"properties": {
"url": {
"type": "string",
"maxLength": 512,
"description": "Payment link: https://payments.coinbase.com/payment-links/pl_... or https://payments.coinbase.com/payment-sessions/paymentSession_..."
},
"chainId": {
"type": "string",
"enum": [
"1",
"56",
"137",
"900",
"1500",
"1600",
"8453",
"42161",
"728126428",
"lightning"
],
"description": "Source chain id from supported_coins: \"1\" Ethereum, \"56\" BNB Chain, \"137\" Polygon, \"42161\" Arbitrum, \"900\" Solana, \"8453\" Base, \"1500\" Stellar, \"lightning\", \"728126428\" TRON (Beta), \"1600\" TON."
},
"tokenSymbol": {
"type": "string",
"minLength": 2,
"maxLength": 8,
"description": "Token you will pay with: USDC, USDT, BTC (Lightning), the chain native coin ETH (1, 8453, 42161), BNB (56), POL (137), SOL (900), or USDT / TRX on TRON, USDT on TON."
},
"email": {
"description": "Optional contact email so ROZO can reach the payer if the payment needs attention. Ask the user once if they are present; never required, omit it if they decline.",
"type": "string",
"maxLength": 320
}
},
"required": [
"url",
"chainId",
"tokenSymbol"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢payment_status(rozoPaymentId, url)
Check a Rozo order: whether the deposit arrived, bridging/payout progress, and whether the OpenRouter or other AI service invoice settled. Pass rozoPaymentId for orders that have one, or url (the payment link) for TRON / TON orders, which have none. Read-only.
입력 스키마
{
"type": "object",
"properties": {
"rozoPaymentId": {
"description": "Order UUID returned by create_deposit_order.",
"type": "string",
"maxLength": 64
},
"url": {
"description": "Payment link of a TRON / TON order (use instead of rozoPaymentId).",
"type": "string",
"maxLength": 512
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢funding_capabilities
What the keyless ROZO Funding API supports right now: whether stellar_onboarding is on, the source chains and USDC assets, the Stellar USDC output, the usdGas options (XLM amounts) and per-order limits. Read-only, creates nothing. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
입력 스키마
{
"type": "object",
"properties": {},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢stellar_wallet_quote(receiverAddress, sourceChain, amountUsd, usdGas)
Price sending USDC/USDT from Base, Ethereum, Arbitrum or Polygon to USDC on a Stellar address. If the address is new or has no USDC trustline, the same plan opens the account, adds the trustline and (with usdGas) gives XLM, in one transaction the address signs once. Returns quoteId and planDigest (needed by stellar_wallet_create_order), the USDC and XLM amounts the receiver gets, every fee line and totals, and whether a signature will be needed. Valid about 10 minutes. Read-only: no deposit address, nothing reserved. usdGas: "0" no XLM, "0.5" or "1" buys XLM (see funding_capabilities for amounts); omitted = the server default. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
입력 스키마
{
"type": "object",
"properties": {
"receiverAddress": {
"type": "string",
"maxLength": 80,
"description": "Stellar PUBLIC address (G...) that receives the USDC. Never a secret key."
},
"sourceChain": {
"type": "string",
"enum": [
"base",
"ethereum",
"arbitrum",
"polygon"
],
"description": "Chain you will pay from."
},
"amountUsd": {
"type": "string",
"maxLength": 16,
"description": "Amount you will send, as a decimal string in USD, e.g. \"10\" or \"10.50\". Limits come from funding_capabilities (1 to 1000 today)."
},
"usdGas": {
"description": "USD of XLM for fees. Omit to use the server default.",
"type": "string",
"enum": [
"0",
"1",
"0.5"
]
}
},
"required": [
"receiverAddress",
"sourceChain",
"amountUsd"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡stellar_wallet_create_order(quoteId, planDigest, orderId)
Turn an approved quote into a payable order. Returns fundingId (keep it private: it is the only handle to the order), the one-time deposit address, the suggested amount and amountPolicy with minAcceptedAmount/maxPricedAmount when any_amount, payBefore and the accepted chains and tokens. orderId is your own reference: the server derives the upstream order id and Idempotency-Key from quoteId plus orderId, so it only has to be unique among your own orders. Retrying with the same quoteId and orderId returns the same order instead of a second one. Creates an order but moves no funds; an unpaid order expires at no cost. Fees come from the quote (fees and totals): never assume a fee. The receiving Stellar address signs ONE transaction (only when it is new or has no USDC trustline). The one-time deposit address is the same on Base, Ethereum, Arbitrum and Polygon; USDC or USDT is accepted 1:1. Follow deposit.amountPolicy: exact or missing means pay the EXACT deposit amount; any_amount uses the suggested amount and returned min/max bounds. Pay once, before payBefore. This server never holds keys: your own wallet pays and signs.
입력 스키마
{
"type": "object",
"properties": {
"quoteId": {
"type": "string",
"maxLength": 64,
"description": "quoteId from stellar_wallet_quote."
},
"planDigest": {
"type": "string",
"maxLength": 64,
"description": "planDigest from the same quote."
},
"orderId": {
"type": "string",
"maxLength": 128,
"description": "Your own order reference, 8 to 128 chars of A-Z a-z 0-9 _ . : -, unique among your orders (for example agent-order-0001). Reuse it with the same quoteId to retry safely."
}
},
"required": [
"quoteId",
"planDigest",
"orderId"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢stellar_wallet_order_status(fundingId)
Read a funding order by fundingId: status, pendingActions (sign_stellar_onboarding means the receiver must sign), the deposit, and each leg (USDC, XLM) with its own status, delivered amount and tx hash. Read-only. Poll about every 15 seconds; completed only when every leg is confirmed.
입력 스키마
{
"type": "object",
"properties": {
"fundingId": {
"type": "string",
"maxLength": 64,
"description": "fundingId from stellar_wallet_create_order."
}
},
"required": [
"fundingId"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡stellar_wallet_get_signing_request(fundingId, walletAddress)
When an order shows sign_stellar_onboarding, build the one transaction the receiving address must sign (creates the account if needed, adds the USDC trustline, claims the USDC, delivers XLM). Returns signingRequestId, the unsigned XDR, networkPassphrase, a readable operations list and expiresAt (at most 5 minutes). Sign it with the receiver wallet YOU control (Stellar SDK, Freighter, any wallet); do not modify it. Check the operations first, and decode the XDR locally to confirm it matches them exactly. The transaction source must NOT be your address (it is a ROZO channel account, so ROZO pays the network fee). Allowed, nothing else: ROZO-sourced beginSponsoringFutureReserves and createAccount for your address; from your address, changeTrust for USDC (issuer GA5ZSEJYB37JRC5AVCIA5MOP4RHTM335X2KGX3IHOJAPP5RE34K4KZVN), endSponsoringFutureReserves, claimClaimableBalance, and at most one payment: the sponsor fee in USDC to ROZO claim custody GBLTI2TTQXUAYNKGCQ63YA55KTFEAOQJ3DPBPELNPWCJVE76ADWMXUAE; and a ROZO-sourced XLM payment to your address. Any other operation type or source (setOptions, extra payments): refuse. Amounts: the claimed USDC (gross) equals the current stable leg minimumAmount (order.legs, after repricing) plus the sponsor fee; the sponsor fee is fixed at quote time (0.0000001 USDC with a paid usdGas tier, the quoted stellar_sponsor_fee with usdGas "0", no fee payment if the address needed no onboarding); the XLM payment equals the native (XLM) leg minimumAmount. The XDR shows only the claimable balance id; its amount is in the operations list and on Horizon /claimable_balances/{id}. The hash of the locally decoded transaction (tx.hash() as hex) must equal the txHash of this signing request. Every ROZO-sourced operation and the transaction source must be one of funding_capabilities rozoAccounts (reserveSponsor, xlmPayer, transactionSources). Do not echo fundingId into logs. Expired, or submit failed: just call this tool again; it supersedes the old request and returns a fresh XDR (only refused while a signed one is still submitting). This server never sees your key. Then call stellar_wallet_submit_signed.
입력 스키마
{
"type": "object",
"properties": {
"fundingId": {
"type": "string",
"maxLength": 64,
"description": "fundingId of the order."
},
"walletAddress": {
"type": "string",
"maxLength": 80,
"description": "The order's receiving Stellar PUBLIC address (G...)."
}
},
"required": [
"fundingId",
"walletAddress"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}🟡stellar_wallet_submit_signed(signingRequestId, signedXdr)
Submit the XDR your own wallet signed for a signing request. This is the claim: the account, trustline, USDC and XLM land in that one transaction. Submitting the same signed XDR again is safe (idempotent). Accepts only the signed transaction envelope, never a secret key. "submitted" is not delivery: poll stellar_wallet_order_status until completed. If it answers template_expired or failed, call stellar_wallet_get_signing_request again and sign the new XDR.
입력 스키마
{
"type": "object",
"properties": {
"signingRequestId": {
"type": "string",
"maxLength": 64,
"description": "signingRequestId from stellar_wallet_get_signing_request."
},
"signedXdr": {
"type": "string",
"maxLength": 20000,
"description": "Signed transaction envelope, base64, as returned by your wallet. NOT a secret key."
}
},
"required": [
"signingRequestId",
"signedXdr"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}커뮤니티
증거