HOTLIKESHOP
Search & buy MMO/social accounts, proxies & digital services from HOTLIKESHOP in your AI chat.
사용해야 할까요
품질 및 안전성
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"hotlikeshop-mcp": {
"url": "https://hotlikeshop.com/api/mcp"
}
}
}원격 엔드포인트
https://hotlikeshop.com/api/mcpstreamable-http할 수 있는 일
도구 목록
도구 (32)
🟢search_products(query, limit)
Search the public catalog by keyword in the product name; returns id, name, price (VND), stock, category and url. Read-only, no api_key required. WHEN TO USE: the user already has a search term or product name. PREFER INSTEAD: list_categories + list_category_products to browse without a keyword, best_sellers for "popular", latest_products for "new", get_product for the full detail of one id. Not for buying — pass a found id to quote_order. Tìm sản phẩm công khai theo tên; chỉ đọc, không cần api_key.
입력 스키마
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Keyword / từ khóa (product name)."
},
"limit": {
"type": "integer",
"description": "Max results (default 20, max 50)."
}
},
"required": [
"query"
]
}🟢get_product(id)
Get the full public detail of ONE product by its numeric id: name, price (VND), stock, category, long description and url. Read-only, no api_key required. WHEN TO USE: after search_products / list_category_products / best_sellers gave you an id and the user wants the full description of that single item. PREFER INSTEAD: compare_products to evaluate 2-5 ids at once, similar_products to find alternatives. Requires a known product id (not a name). Not for buying — pass the id to quote_order. Xem chi tiết 1 sản phẩm công khai theo id (kèm mô tả); chỉ đọc, không cần api_key.
입력 스키마
{
"type": "object",
"properties": {
"id": {
"type": "integer",
"description": "Product id."
}
},
"required": [
"id"
]
}🟢list_categories
List every public category with its id, name and in-stock product count. Read-only, takes no parameters, no api_key required. WHEN TO USE: call this FIRST to discover the category taxonomy and get the category_id values required by list_category_products, best_sellers, latest_products and recommend_products. PREFER INSTEAD: search_products when the user already has a keyword, or how_to_start for onboarding. This only lists categories — it does not return individual products. Liệt kê danh mục công khai kèm số sản phẩm; dùng để lấy category_id.
입력 스키마
{
"type": "object",
"properties": {}
}🟢list_category_products(category_id, limit)
List in-stock public products inside ONE category by category_id: id, name, price (VND), stock. Read-only, no api_key required. PREREQUISITE: get category_id from list_categories first. WHEN TO USE: browse everything in a chosen category. PREFER INSTEAD: search_products for keyword search across all categories, best_sellers to rank a category by sales, recommend_products to filter by budget, latest_products for newest. Not for buying — pass a chosen id to quote_order. Liệt kê sản phẩm công khai trong 1 danh mục theo category_id.
입력 스키마
{
"type": "object",
"properties": {
"category_id": {
"type": "integer",
"description": "Category id."
},
"limit": {
"type": "integer",
"description": "Max results (default 30, max 100)."
}
},
"required": [
"category_id"
]
}🟢get_2fa(secret)
Generate the current 2FA/TOTP code (6 digits) from a Base32 secret key (Google Authenticator style). Computed on the server in-memory only, never stored or logged. Free, no api_key required. WHEN TO USE: the user has an authenticator secret key (from an account they bought or own) and needs the live TOTP code now. PREFER INSTEAD: get_mail_code for email OTP/verification codes delivered to a mail-bundled order. Requires a valid Base32 secret. Sinh mã 2FA/TOTP hiện tại (6 số) từ khóa bí mật Base32; tính cục bộ, không lưu, không gửi đi đâu.
입력 스키마
{
"type": "object",
"properties": {
"secret": {
"type": "string",
"description": "Base32 secret key (spaces allowed). Khóa bí mật Base32 (cho phép có dấu cách)."
}
},
"required": [
"secret"
]
}🟢check_live_facebook(uid, proxy)
Check whether ONE Facebook UID (numeric) is live or dead via the public profile-picture endpoint (server-side). Read-only, free, no api_key required. Facebook blocks datacenter IPs, so if it cannot verify it returns status "needs_proxy" — pass your own "proxy" to check reliably. WHEN TO USE: a single Facebook UID. PREFER INSTEAD: check_health_bulk for many accounts at once or for Instagram/Telegram/TikTok, deep_inspect for a detailed profile (followers, bio, media). Kiểm tra 1 UID Facebook (số) sống/chết; FB chặn IP máy chủ nên nếu không check được sẽ trả "needs_proxy" — truyền "proxy" riêng để check chuẩn.
입력 스키마
{
"type": "object",
"properties": {
"uid": {
"type": "string",
"description": "Facebook numeric UID. UID Facebook (chỉ gồm chữ số)."
},
"proxy": {
"type": "string",
"description": "Optional: YOUR own proxy for this request only (never shared). Format: http(s)://user:pass@host:port or socks5://host:port. Tùy chọn: proxy CỦA BẠN, chỉ áp cho request này (không chia sẻ). Dạng http(s)://user:pass@host:port hoặc socks5://host:port."
}
},
"required": [
"uid"
]
}🟢check_health_bulk(items, platform, proxy)
Bulk live/dead check for MANY accounts at once (max 20 per call): Facebook UID (numeric) or Instagram/Telegram/TikTok usernames. Returns per-item status + a summary. Read-only, free, no api_key required. IG/FB items that cannot be verified (datacenter IP blocked) are moved to "skipped" — pass your own "proxy" to check them reliably. WHEN TO USE: a list of 2-20 accounts, or any non-Facebook platform. PREFER INSTEAD: check_live_facebook for a single Facebook UID, deep_inspect for one detailed profile. Kiểm tra sống/chết HÀNG LOẠT (tối đa 20/lần): UID Facebook hoặc username IG/TG/TikTok; mục IG/FB không check được bị đưa vào "skipped" — truyền "proxy" riêng để check chuẩn.
입력 스키마
{
"type": "object",
"properties": {
"items": {
"type": "array",
"items": {
"type": "string"
},
"description": "List of UIDs (Facebook) or usernames (IG/TG/TikTok). Danh sách UID/username (tối đa 20). Cũng chấp nhận 1 chuỗi ngăn cách bởi dấu phẩy/xuống dòng."
},
"platform": {
"type": "string",
"enum": [
"facebook",
"instagram",
"telegram",
"tiktok"
],
"description": "Platform to check. Nền tảng cần kiểm tra (mặc định facebook)."
},
"proxy": {
"type": "string",
"description": "Optional (recommended for IG/FB): YOUR own proxy, this request only, never shared. http(s)://user:pass@host:port or socks5://host:port. Tùy chọn (nên có cho IG/FB): proxy CỦA BẠN, chỉ request này."
}
},
"required": [
"items"
]
}🟢deep_inspect(platform, handle, proxy)
Deep profile lookup for ONE social account (server-side, best-effort, public data only): Instagram/TikTok → followers, bio, verified, media; Telegram → title, members; Facebook UID → live/dead + avatar. Read-only, free, no api_key required. IG/FB block datacenter IPs → if it cannot read it returns status "needs_proxy"; pass your own "proxy" to read reliably. WHEN TO USE: you want rich detail about one profile. PREFER INSTEAD: check_health_bulk to sweep many accounts for live/dead only, check_live_facebook for a quick single-UID liveness check. Xem SÂU 1 tài khoản MXH (chỉ đọc công khai); IG/FB chặn IP máy chủ → nếu không xem được trả "needs_proxy", truyền "proxy" riêng để xem chuẩn.
입력 스키마
{
"type": "object",
"properties": {
"platform": {
"type": "string",
"enum": [
"facebook",
"instagram",
"telegram",
"tiktok"
],
"description": "Platform. Nền tảng cần xem."
},
"handle": {
"type": "string",
"description": "Username/handle (IG/TG/TikTok) or numeric UID (Facebook). Also accepts a full profile URL. Username hoặc UID (FB); chấp nhận cả link profile."
},
"proxy": {
"type": "string",
"description": "Optional (recommended for IG/FB): YOUR own proxy, this request only, never shared. http(s)://user:pass@host:port or socks5://host:port. Tùy chọn (nên có cho IG/FB): proxy CỦA BẠN, chỉ request này."
}
},
"required": [
"platform",
"handle"
]
}🟢recommend_products(budget, keyword, category_id, limit)
Recommend in-stock public products by budget and/or keyword/category, cheapest first, with a simple combo suggestion. Read-only, no api_key required, public fields only (price VND). WHEN TO USE: the user has a budget or a vague need ("something under 50k for Facebook"). PREFER INSTEAD: search_products for an exact keyword, best_sellers for popularity, latest_products for newest, list_category_products to see a whole category. Optionally scope with category_id from list_categories. Gợi ý sản phẩm CÒN HÀNG theo ngân sách và/hoặc từ khóa/danh mục (rẻ trước) kèm gợi ý combo; chỉ trả field công khai (giá VND).
입력 스키마
{
"type": "object",
"properties": {
"budget": {
"type": "integer",
"description": "Max unit price in VND (optional). Ngân sách/giá tối đa mỗi SP (VND, tùy chọn)."
},
"keyword": {
"type": "string",
"description": "Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn)."
},
"category_id": {
"type": "integer",
"description": "Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn)."
},
"limit": {
"type": "integer",
"description": "Max results (default 8, max 20)."
}
}
}🟡topup_guide(api_key, amount, lang)
Explain how to add funds (deposit) to a hotlikeshop account and list the active deposit methods/networks + min/max. Info only — this tool never moves money. Read-only. WHEN TO USE: call this FIRST, before create_usdt_deposit or create_binance_deposit, to see which networks are enabled; pass api_key to also show current balance & the shortfall vs a target amount. PREFER INSTEAD: how_to_start for full new-user onboarding, get_my_balance if you only need the balance number. Pass lang="en" for an English guide. Hướng dẫn nạp tiền (chỉ thông tin, KHÔNG thanh toán); truyền api_key để kèm số dư & phần còn thiếu, kèm quy đổi USD.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Optional: your shop api_key to also show current balance & shortfall (with USD conversion). Tùy chọn: api_key để hiện số dư & phần còn thiếu."
},
"amount": {
"type": "integer",
"description": "Optional: amount you want to spend (VND) to compute shortfall. Tùy chọn: số tiền cần (VND) để tính phần còn thiếu."
},
"lang": {
"type": "string",
"description": "Optional: \"en\" for English guide, otherwise Vietnamese. Tùy chọn: \"en\" để nhận hướng dẫn tiếng Anh."
}
}
}🟢how_to_start(lang)
Onboarding guide for NEW users: how to start buying on hotlikeshop through this MCP (create account -> get api_key -> top up -> search & buy). Read-only, no api_key required. WHEN TO USE: the very FIRST call for a new / international user, or whenever someone lacks an api_key or asks "how does this work". Lists which tools are free vs. which need an api_key. PREFER INSTEAD: topup_guide for deposit specifics, quote_order + buy_product to actually purchase, search_products to browse. Pass lang="en" (default) or lang="vi". Hướng dẫn bắt đầu cho người mới: tạo tài khoản -> lấy api_key -> nạp tiền -> tìm & mua.
입력 스키마
{
"type": "object",
"properties": {
"lang": {
"type": "string",
"description": "Optional: \"en\" (default) or \"vi\". Ngôn ngữ hướng dẫn: \"en\" (mặc định) hoặc \"vi\"."
}
}
}🟢best_sellers(category_id, keyword, limit)
List best-selling in-stock public products (most sold first), public fields only (price VND + units sold). Read-only, no api_key required. WHEN TO USE: the user wants "popular / hot / most bought" items. PREFER INSTEAD: latest_products for "new arrivals", search_products for a keyword, recommend_products for a budget, list_category_products for a full category. Optionally scope with category_id (from list_categories) or a keyword. Danh sách sản phẩm BÁN CHẠY còn hàng (đã bán nhiều nhất trước); chỉ trả field công khai (giá VND + số đã bán).
입력 스키마
{
"type": "object",
"properties": {
"category_id": {
"type": "integer",
"description": "Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn)."
},
"keyword": {
"type": "string",
"description": "Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn)."
},
"limit": {
"type": "integer",
"description": "Max results (default 10, max 20)."
}
}
}🟢latest_products(category_id, keyword, limit)
List newest in-stock public products (recently added first), public fields only (price VND). Read-only, no api_key required. WHEN TO USE: the user wants "new arrivals / just added". PREFER INSTEAD: best_sellers for "popular", search_products for a keyword, recommend_products for a budget, list_category_products for a full category. Optionally scope with category_id (from list_categories) or a keyword. Danh sách sản phẩm MỚI còn hàng (thêm gần đây nhất trước); chỉ trả field công khai (giá VND).
입력 스키마
{
"type": "object",
"properties": {
"category_id": {
"type": "integer",
"description": "Limit to a category id (optional). Giới hạn theo danh mục (tùy chọn)."
},
"keyword": {
"type": "string",
"description": "Keyword in product name (optional). Từ khóa trong tên SP (tùy chọn)."
},
"limit": {
"type": "integer",
"description": "Max results (default 10, max 20)."
}
}
}🟢compare_products(ids)
Compare 2–5 public products side by side (price, stock, min/max, sold, category) with a quick summary (cheapest / most stock / best seller). Read-only, no api_key required, public fields only (price VND). PREREQUISITE: you already have 2-5 product ids. WHEN TO USE: help the user pick between specific candidates. PREFER INSTEAD: get_product for one id in depth, similar_products to first discover comparable items, search_products / list_category_products to find ids. So sánh 2–5 sản phẩm cạnh nhau để khách chốt nhanh; chỉ field công khai (giá VND).
입력 스키마
{
"type": "object",
"properties": {
"ids": {
"type": "array",
"items": {
"type": "integer"
},
"description": "Danh sách 2–5 product id cần so sánh, vd [943, 1004]. Cũng chấp nhận chuỗi \"943,1004\"."
}
},
"required": [
"ids"
]
}🟢similar_products(id, limit)
Given ONE product id, list similar in-stock public products (same category, best-selling first; fills with newest from other categories if few). Read-only, no api_key required, public fields only (price VND + units sold). PREREQUISITE: a known product id. WHEN TO USE: suggest alternatives / cross-sell around an item the user is viewing, then optionally compare_products. PREFER INSTEAD: search_products for keyword search, recommend_products for budget-based picks, list_category_products to browse the whole category. Cho 1 product id, trả các SP TƯƠNG TỰ còn hàng (cùng danh mục, ưu tiên bán chạy; bù SP mới khác danh mục nếu ít).
입력 스키마
{
"type": "object",
"properties": {
"id": {
"type": "integer",
"description": "Product id gốc để tìm SP tương tự, vd 943."
},
"limit": {
"type": "integer",
"description": "Max results (default 8, max 20)."
}
},
"required": [
"id"
]
}🟡get_my_balance(api_key)
Get your account balance, level and discount (requires your shop api_key). Read-only, spends nothing. WHEN TO USE: the user asks "how much do I have" or you need to confirm funds before quote_order / buy_product. PREFER INSTEAD: wallet_history for the full ledger of top-ups/spends/refunds, topup_guide to add funds, quote_order to price a specific purchase. Requires a valid api_key. Xem số dư & hạng tài khoản (cần api_key); trả balance (VND), level, discount.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key. Khóa API tài khoản shop của bạn (Trang cá nhân → API)."
}
},
"required": [
"api_key"
]
}🟢quote_order(api_key, product_id, quantity)
STEP 1 of buying: get a price quote for a product BEFORE purchasing. Returns unit price, discount, total to pay (VND), your balance, stock, and a confirm_token (single-use, valid ~5 min). SPENDS NOTHING. Requires api_key + product_id. WHEN TO USE: always call this first, then show the total to the user and get explicit approval before buy_product. PREFER INSTEAD: get_my_balance to only check funds, check_order_status for an order that already exists (not for pricing a new one). Bước 1 khi mua: báo giá TRƯỚC khi mua, trả confirm_token; KHÔNG trừ tiền. Luôn hỏi người dùng xác nhận rồi mới gọi buy_product.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"product_id": {
"type": "integer",
"description": "Product id (from search_products / get_product)."
},
"quantity": {
"type": "integer",
"description": "Quantity to buy (default 1)."
}
},
"required": [
"api_key",
"product_id"
]
}🟡buy_product(api_key, confirm_token)
STEP 2 of buying: place the order using the confirm_token from quote_order. IRREVERSIBLE — this SPENDS real balance and delivers the product; returns order_code + the delivered content. PREREQUISITE: a fresh confirm_token from quote_order (same api_key). WHEN TO USE: only AFTER the user has explicitly approved the exact total shown by quote_order. Do NOT call speculatively or to re-price. AFTERWARDS: check_order_status for delivery (set refresh=true if it looks stuck), get_mail_code for OTP, submit_complaint if faulty. Bước 2: đặt mua thật bằng confirm_token (TRỪ TIỀN THẬT & giao hàng); chỉ gọi sau khi người dùng đã đồng ý giá đã báo.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key (must match the one used in quote_order)."
},
"confirm_token": {
"type": "string",
"description": "The confirm_token returned by quote_order (valid ~5 minutes, single use)."
}
},
"required": [
"api_key",
"confirm_token"
]
}🟡check_order_status(api_key, order_code, refresh)
Check the status and delivered content (account credentials) of ONE of your orders by order_code (requires your api_key). Read-only by default — spends nothing. OPTIONAL refresh=true: if the order looks stuck/undelivered (pending/failed), re-triggers delivery from the system (async, safe — never charges money, never touches a completed/refunded order) then returns the current status; poll again after ~5-10s. PREREQUISITE: an order_code (from buy_product or list_orders). WHEN TO USE: the user wants the current state or the delivered data of a specific order; set refresh=true only to nudge a stuck order. PREFER INSTEAD: list_orders to find the order_code first, get_mail_code for the email OTP, submit_complaint if the delivered item is faulty. Kiểm tra trạng thái & nội dung đã giao của 1 đơn theo order_code (cần api_key); truyền refresh=true để ép giao lại nếu đơn treo — không tính phí.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"order_code": {
"type": "string",
"description": "The order code returned by buy_product."
},
"refresh": {
"type": "boolean",
"description": "Set true to re-trigger delivery when the order looks stuck/undelivered (async; safe, never charges). Default false = plain read-only status check."
}
},
"required": [
"api_key",
"order_code"
]
}🟡submit_complaint(api_key, order_code, reason, description)
File a complaint / warranty-refund request for ONE delivered order (requires your api_key). Opens a support case; the shop reviews within 3 days and if unresolved in time the order is auto-refunded. NOT idempotent — one complaint per order, so confirm with the user before calling. PREREQUISITE: an order_code that was delivered and is genuinely faulty. WHEN TO USE: the bought item is wrong / dead / login-fails / short quantity. PREFER INSTEAD: check_order_status with refresh=true first if it merely looks stuck (undelivered), then check_order_status to track the case afterwards. Gửi khiếu nại/bảo hành-hoàn tiền cho 1 đơn (cần api_key); shop xử lý ≤3 ngày, quá hạn TỰ ĐỘNG HOÀN; mỗi đơn chỉ khiếu nại 1 lần; theo dõi bằng check_order_status.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"order_code": {
"type": "string",
"description": "The order code you want to complain about (must belong to your account)."
},
"reason": {
"type": "string",
"description": "Short reason for the complaint, e.g. \"Sai sản phẩm\", \"Không đăng nhập được\", \"Die/khóa\", \"Thiếu số lượng\", \"Khác\"."
},
"description": {
"type": "string",
"description": "Optional details describing the problem (which items failed, error message, etc.)."
}
},
"required": [
"api_key",
"order_code",
"reason"
]
}🟢list_orders(api_key, page, limit)
List your recent orders (order history), paginated, with order_code, product, quantity, total paid, status and date (requires your api_key). Read-only, spends nothing. WHEN TO USE: the user wants their purchase history or you need to find an order_code. AFTERWARDS: check_order_status (with refresh=true to nudge a stuck order) / get_mail_code for a specific order_code. PREFER INSTEAD: wallet_history for money movements (top-ups/refunds), not order details. Liệt kê lịch sử đơn (order_code, sản phẩm, số lượng, tổng tiền, trạng thái, ngày) — cần api_key; dùng để tìm order_code rồi gọi check_order_status / get_mail_code.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"page": {
"type": "integer",
"description": "Page number (default 1)."
},
"limit": {
"type": "integer",
"description": "Orders per page (default 20, max 100)."
}
},
"required": [
"api_key"
]
}🟢get_mail_code(api_key, order_code)
Get the latest email OTP / verification code for a purchased mail-bundled account order. Supports Hotmail/Outlook via OAuth (refresh_token) and mail.tm (email + password). Read-only. PREREQUISITE: api_key + an order_code whose delivered account includes an inbox. WHEN TO USE: the user needs the verification code sent to the email that came with their order. PREFER INSTEAD: get_2fa for authenticator (TOTP) codes, check_order_status to see the delivered credentials themselves. Lấy mã OTP/xác minh mới nhất cho đơn tài khoản có kèm mail (Hotmail/Outlook qua refresh_token, mail.tm qua email+mật khẩu); cần api_key + order_code.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"order_code": {
"type": "string",
"description": "The order code of the mail-bundled account order."
}
},
"required": [
"api_key",
"order_code"
]
}🟡create_usdt_deposit(api_key, amount_usd, network)
Create a USDT deposit order to top up your balance. The SERVER generates the real receiving wallet address and a unique amount (with cents) — relay them to the user VERBATIM, never invent or edit a wallet address. Supports TRC20 / BEP20 / Polygon / Arbitrum / Base. PREREQUISITE: api_key; call topup_guide FIRST to see which networks are active + min/max. WHEN TO USE: the user wants to deposit on-chain USDT. AFTERWARDS: once they send, call verify_usdt_deposit with order_code + claim_token. PREFER INSTEAD: create_binance_deposit for users paying inside the Binance app. Tạo đơn nạp USDT — hệ thống tự sinh ĐỊA CHỈ VÍ và SỐ TIỀN kèm số lẻ độc nhất; chuyển lại NGUYÊN VĂN, KHÔNG tự chế/sửa ví.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"amount_usd": {
"type": "number",
"description": "Whole-number USD amount to deposit (decimals are ignored — the system assigns a unique cents suffix)."
},
"network": {
"type": "string",
"description": "USDT network: trc20 | bep20 | polygon | arbitrum | base (default trc20). Only networks with a configured wallet work — check topup_guide.",
"enum": [
"trc20",
"bep20",
"polygon",
"arbitrum",
"base"
]
}
},
"required": [
"api_key",
"amount_usd"
]
}🟡verify_usdt_deposit(api_key, order_code, claim_token, method, tx_hash)
Check / confirm a USDT deposit created by create_usdt_deposit. Scans the blockchain for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~15s, credits only once. PREREQUISITE: order_code + claim_token from create_usdt_deposit. WHEN TO USE: after the user has sent the USDT, to confirm and credit it; optionally pass method="hash" + tx_hash to verify by a specific transaction. PREFER INSTEAD: verify_binance_deposit for Binance Pay deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp USDT — quét blockchain, khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"order_code": {
"type": "string",
"description": "order_code from create_usdt_deposit."
},
"claim_token": {
"type": "string",
"description": "claim_token from create_usdt_deposit (single-order secret)."
},
"method": {
"type": "string",
"description": "Verification mode: \"amount\" (default, auto-scan by unique amount) or \"hash\".",
"enum": [
"amount",
"hash"
]
},
"tx_hash": {
"type": "string",
"description": "Transaction hash (only when method=\"hash\")."
}
},
"required": [
"api_key",
"order_code",
"claim_token"
]
}🟡create_binance_deposit(api_key, amount_usd)
Create a Binance Pay deposit order to top up your balance. The SERVER returns the shop receive Pay ID (and QR) plus a unique USDT amount (with cents) — relay them VERBATIM, never invent them. PREREQUISITE: api_key AND Binance Pay must be enabled (check topup_guide first). WHEN TO USE: the user will pay inside the official Binance app. AFTERWARDS: call verify_binance_deposit with merchant_trade_no. PREFER INSTEAD: create_usdt_deposit for on-chain USDT transfers. Tạo đơn nạp Binance Pay — hệ thống trả Pay ID nhận tiền + số USDT kèm số lẻ; chuyển lại NGUYÊN VĂN.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"amount_usd": {
"type": "number",
"description": "Whole-number USD amount to deposit (the system assigns a unique cents suffix)."
}
},
"required": [
"api_key",
"amount_usd"
]
}🟡verify_binance_deposit(api_key, merchant_trade_no)
Check / confirm a Binance Pay deposit created by create_binance_deposit. Reads the shop Binance Pay history for a matching transfer and credits your balance when found. Idempotent — safe to poll every ~12s, credits only once. PREREQUISITE: merchant_trade_no from create_binance_deposit. WHEN TO USE: after the user has paid via Binance Pay, to confirm and credit it. PREFER INSTEAD: verify_usdt_deposit for on-chain USDT deposits, get_my_balance/wallet_history to inspect balance afterwards. Kiểm tra & xác nhận đơn nạp Binance Pay — khớp thì cộng tiền (an toàn khi gọi lại nhiều lần).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"merchant_trade_no": {
"type": "string",
"description": "merchant_trade_no from create_binance_deposit."
}
},
"required": [
"api_key",
"merchant_trade_no"
]
}🟢wallet_history(api_key, page)
Get the balance ledger for the account: every top-up (bank/USDT/Binance Pay + bonuses, check-in, missions, wheel, reviews, affiliate) and every spend (purchases) / refund, with the running balance after each entry, plus totals in/out. Paginated (20/page, newest first). Read-only, spends nothing. WHEN TO USE: the user wants a history of money movements or to audit where funds went. PREFER INSTEAD: get_my_balance for just the current number, list_orders for purchase/order details rather than money entries. Requires api_key. Xem lịch sử biến động số dư (nạp/tiêu/hoàn) kèm số dư sau mỗi giao dịch.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"page": {
"type": "integer",
"description": "Page number (default 1, 20 rows per page)."
}
},
"required": [
"api_key"
]
}🟢gamefi_status(api_key, lang)
One-shot overview of all FREE balance rewards the account can grab right now: daily check-in (available today? streak, reward range), lucky-wheel spins available, and the quest board (how many quests are complete & claimable). Read-only. WHEN TO USE: call this FIRST whenever the user asks about rewards/free balance, then use daily_checkin / spin_wheel / list_quests + claim_quest to collect. Note: all rewards credit the SHOPPING balance (spendable in-shop, NOT withdrawable). Requires api_key. Tổng quan phần thưởng miễn phí: điểm danh, vòng quay, nhiệm vụ có thể nhận (thưởng vào số dư mua hàng, không rút được).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"lang": {
"type": "string",
"description": "Language for labels: \"vi\" or \"en\" (default en)."
}
},
"required": [
"api_key"
]
}🟢daily_checkin(api_key)
Perform the once-a-day check-in and collect the reward (random 200-1,000đ base + streak milestone bonuses at 7/30 days, sometimes x2 combo). Idempotent — if already checked in today it just says so (no double credit). Each check-in also grants +1 lucky-wheel spin. Reward credits the SHOPPING balance (not withdrawable). WHEN TO USE: the user wants to claim today's free check-in. PREFER INSTEAD: gamefi_status to first see if it is available, spin_wheel to use the earned spin, claim_quest for quest rewards. Requires api_key. Điểm danh hằng ngày nhận thưởng (mỗi ngày 1 lần).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
}
},
"required": [
"api_key"
]
}🟢spin_wheel(api_key)
Spin the lucky wheel once and return the prize won + new balance. Consumes exactly one spin server-side (NOT free to repeat — each call uses a spin). PREREQUISITE: available spins, earned from check-ins/deposits/purchases (see gamefi_status). WHEN TO USE: the user has spins and wants to use one. PREFER INSTEAD: daily_checkin to earn a spin first, gamefi_status to see how many spins remain. Winnings credit the SHOPPING balance (not withdrawable). Requires api_key. Quay vòng quay may mắn 1 lượt (cần còn lượt quay).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
}
},
"required": [
"api_key"
]
}🟢list_quests(api_key, lang)
List the daily & weekly quest board with progress: each quest key, title, reward, current/target progress, whether it is complete and whether it is already claimed. Read-only, spends nothing. WHEN TO USE: the user wants to see quests or you need a quest_key. AFTERWARDS: call claim_quest on any quest that is complete but not yet claimed. PREFER INSTEAD: gamefi_status for a combined rewards summary (check-in + wheel + quests). Requires api_key. Danh sách nhiệm vụ ngày/tuần kèm tiến độ + phần thưởng.
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"lang": {
"type": "string",
"description": "Language for titles: \"vi\" or \"en\" (default en)."
}
},
"required": [
"api_key"
]
}🟢claim_quest(api_key, quest_key)
Claim the reward for ONE completed quest. Server verifies completion from real data; idempotent — one claim per quest per period (a second call will not double-credit). Reward credits the SHOPPING balance (not withdrawable). PREREQUISITE: a quest_key that is complete-but-unclaimed, from list_quests or gamefi_status. WHEN TO USE: collect a finished quest. PREFER INSTEAD: list_quests to find which quest_key is claimable, daily_checkin / spin_wheel for those specific rewards. Requires api_key. Nhận thưởng 1 nhiệm vụ đã hoàn thành (dùng quest_key từ list_quests).
입력 스키마
{
"type": "object",
"properties": {
"api_key": {
"type": "string",
"description": "Your shop account API key."
},
"quest_key": {
"type": "string",
"description": "The quest key to claim (from list_quests), e.g. daily_checkin, daily_buy1, weekly_spend50k."
}
},
"required": [
"api_key",
"quest_key"
]
}커뮤니티
증거