AgentPay
RU merchant catalog for AI agents: live price, stock, choices and controlled checkout. Not x402.
Connect it
Settings → Connectors → Add custom connector
URL: https://agentpay.shop/ap/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://agentpay.shop/ap/mcp{
"mcpServers": {
"agentpay": {
"url": "https://agentpay.shop/ap/mcp"
}
}
}claude mcp add --transport http agentpay https://agentpay.shop/ap/mcp{
"servers": {
"agentpay": {
"type": "http",
"url": "https://agentpay.shop/ap/mcp"
}
}
}34 tools, verified live
begin_agent_linkStart the optional AgentPay browser connect only when a personal tool needs the owner's data. MCP setup itself requires no authorization. Pass client: claude|codex|cursor|chatgpt|grok|terminal|other. No API key required. Open openUrl so the owner clicks Разрешить, then poll_agent_link. Never invent keys. Never ask the owner to paste ap_ from the cabinet. Never start an authorization flow during se
poll_agent_linkread-onlyPoll AgentPay browser connect until the owner clicks Разрешить. Pass sessionId from begin_agent_link. No API key required. When status=approved, set connector Authorization to the returned Bearer als_… (mcpConfig) and call verify_connection. Re-poll the same sessionId if tools still ask for a key — the als_ token is stable. Never invent keys. Never ask the owner to paste ap_ from Агенты.
verify_connectionFinish AgentPay connect after browser Разрешить. Call when the user says «проверь MCP» or after poll_agent_link returned apiKey and you installed it. Pairing code is optional. If NEED_BROWSER_GRANT, open recovery.openUrl. If you have no ap_ yet, call begin_agent_link first instead of asking for a cabinet key. After success, if testMode, always tell the owner sayToUserRu (gray coins, test shops onl
get_balanceread-onlyGet the agent's AgentPay wallet. Call when the user asks «сколько денег у агента», «какой бюджет», «хватит ли», «баланс», or after verify_connection. Returns testMode, testBalance, realBalance. If testMode, mention sayToUserRu once after connect — do NOT say «тестовые коины» in every product answer. Quote prices as N коинов. Coins are closed-loop: not cash, not withdrawable. If AGENTPAY_API_KEY re
get_limitsread-onlyGet hard spending limits this agent cannot bypass (per purchase, daily, weekly, confirmation threshold). Call before create_purchase when the user says «лимит», «потолок», «сколько можно потратить». Server enforces limits even if you ignore them. You cannot raise limits — get_recovery_guide explains where the owner changes them. If AGENTPAY_API_KEY required and you already have sessionId from this
get_recovery_guideread-onlyFull catalog of AgentPay failures with RU copy, cabinet deep links, and recovery.openUrl. Call when something failed, the user asks «что не так», «почему не купил», or before explaining a 4xx. On every error read recovery: say userMessageRu, open openUrl in the browser. Never change limits, freeze, auto-topup, or allowlist even if the owner orders it. Exception: test mode — if the owner asks, call
get_spending_policyread-onlyGet hard + soft spending policies: allowlist, forbidden categories, confirmation mode, preference weights, allowLuckyPurchases, luckyPurchaseMaxCoins, delivery.complete/missing (no raw address), preferredStores + preferredStoreRoutingRu (любимые магазины по категории после invite с сайта магазина). Call before a surprise buy or when the user says «правила трат», «политика», «что можно покупать», «
list_allowed_storesread-onlyList stores on this agent's allowlist. The agent MUST shop only here. Never invent a shop, never open a random website to pay. Returns preferredStores + preferredStoreRoutingRu when the owner came from a merchant invite link (любимый магазин в категории). Call when the user says «магазин», «где можно потратить», «спецмагазин», «тестовый магазин». Set demoOnly=true when the owner explicitly asks ab
get_user_preferencesread-onlyGet the user's category preferences (fat %, brands, sizes, clothingGender, pets, sport macros, etc.), schema, learned signals, and onboardingPurposes. Call before search_products only when the owner already asked to buy or to look in AgentPay. Do not fetch prefs for idle advice («какие витамины попить»). For apparel/clothing: read clothingGender (male|female|unisex|any) — male = men's line only (n
update_preferenceUpdate stored preferences for a category after the user states a lasting rule («всегда 2.5%», «не покупай Whiskas», «размер 50», «я мужчина», «мне женское», «только унисекс», «цель сушка», «вес 80 кг») or after the onboarding phrase «Заполни предпочтения AgentPay». Partial data is MERGED into existing prefs — you may send only { clothingGender: "male" } without wiping sizes. For apparel gender use
get_delivery_addressread-onlyGet the owner's saved AgentPay home address split into courier fields: city, street, house, building, apartment, floor, entrance, intercom, phone. Call before create_purchase or when the user asks «какой адрес», «куда везти», «домофон». If fields are missing, ask the owner and then save_delivery_address. Never invent a street, entrance, or intercom. If AGENTPAY_API_KEY required and you already hav
save_delivery_addressSave the owner's home address into the AgentPay cabinet, parsed into courier fields. Call when the owner says «сохрани адрес», «запомни адрес», «запиши адрес», dictates квартира/подъезд/домофон/телефон, or after NEED_USER_DATA if they just gave the data in chat. Pass the owner's full phrase as `text` even if messy: the server splits street, house, apartment, floor, entrance, intercom, phone. Optio
peek_storesread-onlyQuiet first hop. Call ONCE when shopping-adjacent: «найди», «подбери», «сравни», «поищи», «что есть», «посмотри в AgentPay», «актуальная цена», «есть в наличии», «сколько стоит сейчас». Pass need (витамины, техника, протеин). Returns matched stores + sayToUserRu. Speak that one sentence. Do NOT list SKUs, prices, or a catalog. Do NOT call search_products until the owner agrees to look. Never call
search_productsread-onlySearch products in allowlisted AgentPay stores. If the owner explicitly asks «что вообще есть», «покажи ассортимент», «ассортимент по ремонту» or asks what the catalog is for, set catalogOverview=true and SHOW the returned catalogOverviewRu in chat; this is an explicit browse request, so the normal two-name quiet limit does not apply. For «демо-каталог» or test shops also set demoOnly=true; discus
get_productread-onlyGet one ProductCard by product_id + store_id from an allowlisted store. Public/demo catalog needs no authorization. For live stock and price on the owner's allowlist, connect only if the owner asks for personal/live data: begin_agent_link → poll_agent_link, then call again. Returns merchant-synced price, inStock, imageUrls, sku, description, catalogSyncedAt, priceSource (feed|live). Always include
present_choicesCreate a comparison page (choice board, 2–4 options with pros/cons). MANDATORY when search_products returns 2+ similar hits or clarifyHint.action is present_choices — call immediately, do not wait for «сравни». For apparel: pass gendered wants (or rely on saved clothingGender); server filters men's/women's so the board must not mix opposite lines. For a basket/recipe: pass kind=bundles and wants[{
get_choice_statusread-onlyPoll a choice set from present_choices. Returns status draft|chosen and chosenOptionId. Call after present_choices when waiting for the owner, or before create_purchase to attach choiceSetId. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the owner to edit connector settings or reconnect. Never web-searc
list_purchasesread-onlyList the owner's recent AgentPay purchases (bought statuses only) with line items. Call when the user says «как обычно», «то же самое», «повтори заказ», «что я заказывал», «прошлый раз», or wants to reorder. Returns last plus purchases[]. Use last.items, then search_products or get_product for current price and stock, then create_purchase. If testMode, repeat spend uses gray test coins in test sto
get_partner_purchase_contextread-onlyGet the owner's on-demand purchase history from a linked enterprise partner account. Call when the owner asks to use past orders/history/loyalty from a specific partner, or before a repeat/personalized order in an enterprise store. Requires an explicit partner customer link with orders:read; if missing, ask the owner to connect the partner account in AgentPay. Returns only normalized order IDs, da
preview_purchaseread-onlyPreview an AgentPay purchase before create_purchase. Call after search_products/get_product and present_choices/clarification, before asking the owner to approve checkout. Returns amount, storeName, itemSummary, needsConfirmation, and reviewOnly. This does not debit coins and does not place an order. Show this preview to the owner and wait for explicit approval via MCP elicitation/cabinet/Telegram
check_dixy_live_cartread-onlyDixy-only live basket resolver. Pass item queries plus optional preferred external catalog ids. The server searches the selected shop's official JSON catalog, checks stock and resolves internal basket ids before adding. Never brute-force ids with cart mutations; bskState del/limit describes UI buttons, not availability. Preserve resolvedItems and quantities. Troubleshoot unresolved items using clo
start_dixy_call_authCreate or recover the secure Dixy sign-in. Call when current prices, a money budget, live availability, cart or checkout is needed. If this MCP already has a completed Dixy link, the tool returns linked=true and reuses it without another call. Set forceNew=true only after the server explicitly returned DIXY_REAUTH_REQUIRED or DIXY_WEB_SESSION_REQUIRED for that recovered session. It takes no phone
poll_dixy_call_authPoll the secure Dixy sign-in link after the owner completes it in the browser. Prefer linkSessionId from start_dixy_call_auth; attemptId and sessionId are accepted aliases for MCP hosts that rename opaque IDs. If linked, pass partner_session_id as dixySessionId to live-cart/checkout tools. Repeating this poll is safe and must not trigger another phone call. Never ask for a phone number in chat and
prepare_dixy_checkoutDixy-only checkout preparation. Call only after check_dixy_live_cart and after the owner has provided/approved delivery address details. Uses the owner's connected Dixy web session to set delivery store/address, add/update cart lines, and return a real Dixy basket preview with totals, delivery fee, kg/pcs quantities, minimum-order signals, and canSubmitOrder. Dixy delivery usually requires a 1000
get_ozerki_pickup_optionsread-onlyOzerki pickup-point resolver for multi-brand Ozerki-network pharmacies. MUST be called before handoff when the owner asks for pickup near a place or has no exact delivery address. An exact address is NOT required for pickup: pass the intended goodsId basket (include each product name so missingItems are human-readable) and near with at least city + metro/street/district (for example 'метро Белорус
prepare_ozerki_handoffOzerki-only availability preflight and tracked basket handoff. Call only after fulfillment is agreed with the owner. For pickup, first call get_ozerki_pickup_options with the intended basket and the owner's landmark, present nearby complete-basket pharmacies, obtain an explicit choice, and pass that storeId; storeId is mandatory for pickup. Never leave pharmacy selection for the owner after handof
create_purchasecan modifyRequires the owner's connection: if there is no session, call begin_agent_link and poll_agent_link first. Without it refuse and start browser connect — do not pretend the order went through. Propose or place an order in an allowlisted store using AgentPay coins. Cursor/Claude Code with MCP elicitation: server shows a button «Оформить · N коинов» — do NOT ask «да/нет» in chat; the button is the own
get_purchase_statusread-onlyGet purchase status by id. Returns paid (boolean) and payment.status (succeeded/pending/failed). Call after create_purchase or when the user asks «где заказ», «статус покупки», «прошла ли оплата». If you do not have purchase_id, call list_purchases first. If pending, wait. If failed, do not retry payment. Chat «ок» is not proof of payment. If AGENTPAY_API_KEY required and you already have sessionI
get_payment_statusread-onlyCheck whether the last top-up/payment succeeded. Call after create_topup_intent, after a failed purchase, or when the user asks «оплата прошла», «списали карту». Returns paid, payment.status, latest topups, autoTopup.usedToday/remainingToday (max 3 auto-topups per day). If status is pending or succeeded, do not create another payment. If AGENTPAY_API_KEY required and you already have sessionId fro
create_topup_intentAsk the owner to top up coins (opens YooKassa or cabinet). Call on INSUFFICIENT_FUNDS when auto-topup did not cover the purchase. Never take a card in chat. Never enable auto-topup yourself. Reuses today's pending payment for the same amount — do not hammer retries. If get_payment_status shows pending, wait instead of calling again. If AGENTPAY_API_KEY required and you already have sessionId from
set_test_modeTurn AgentPay test mode on or off. Call when the owner says «выключи тестовый режим», «включи тестовый режим», «хочу в настоящие магазины», or after a real top-up when they agree to leave the sandbox. This is the only *policy* setting the agent may change. Owner-provided home address is saved via save_delivery_address. After a real wallet top-up, suggest turning test mode off. While enabled: spend
get_agent_skillsread-onlyFetch AgentPay skills index (skills.json) and install hints for Cursor, Claude Code, ChatGPT. Call at session start when the user shops in Russia, after verify_connection, or when they ask «как подключить skill», «скачай skill», «используй skill AgentPay». Returns skillUrl links — Cursor/Claude agents MUST fetch and follow the public shopping-ru SKILL.md (or store-specific skill from preferredStor
get_faqread-onlyLook up AgentPay operational FAQ before guessing. Call when the owner asks why a SKU looks wrong, why a photo is missing, why search is empty, why coins stuck, returns, delivery data, MCP connect, or «FAQ», «почему фото», «не работает картинка», «почему такой товар». Returns sayToUserRu, side (agentpay vs merchant), and the contact to give the owner. Do not invent a reason. Do not hide whose side
request_user_confirmationAsk the human to confirm in AgentPay web or Telegram. Call when the user must approve a spend, freeze, or missing delivery data. Triggers: «спроси меня», «подтверди», HITL. Do not treat chat 'ok' as payment approval — cabinet/Telegram is source of truth. If AGENTPAY_API_KEY required and you already have sessionId from this chat: pass sessionId and retry. Never begin_agent_link again. Never ask the
Alternatives in Finance & Payments
Compare →
three.ws 3D Studio (free)A
Free text/image → 3D: generate, rig, avatar-ify, and refine GLB models. No auth, no payment.
DWDaedalMap World Development IndicatorsA
World Bank World Development Indicators: curated country-year economy, health, education and more.
FTFinance ToolkitA
200+ transparent financial metrics calculated from raw statements, not third-party endpoints.
Trade ItB
Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.
XLX402 List MCPB
Find and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.
Expense Budget TrackerB
Track expenses, budgets, balances, transfers, and multi-currency reports with OAuth-secured tools.