# Vibedepot / Вайбдепо

Vibedepot (Вайбдепо) is a marketplace for vibe-coding products: mini-apps, templates, UI kits, AI agents, and SaaS products.

Core public pages:
- Home: https://vibedepot.ru/
- Catalog: https://vibedepot.ru/catalog
- MCP docs: https://vibedepot.ru/docs
- Contacts: https://vibedepot.ru/contacts
- Product pages: https://vibedepot.ru/p/{slug}
- Vibecoder profiles: https://vibedepot.ru/vibecoder/{handle}

Commerce rules:
- One-time purchases deliver a project file after verified payment. Access is permanent.
- Subscriptions deliver a PERSONAL access key (vd_sub_...) issued by Vibedepot for a 30-day period.
- Subscriptions renew manually: the buyer pays again to extend the period. Reminder emails are sent 3 days and 1 day before the period ends.
- When a subscription period ends, access closes within 24 hours and the seller may disable the key on their side.
- The payment 'success' page is not proof of payment. Access is granted only after the verified payment webhook.
- Products are moderated before appearing in the catalog. Reviews are buyer-only and premoderated.

MCP (Model Context Protocol, Streamable HTTP, JSON-RPC 2.0):
- Endpoint: https://vibedepot.ru/mcp · Docs: https://vibedepot.ru/docs
- Public tools: search_products, list_categories, get_product, get_vibecoder, project_readiness_check
- Authenticated tools (Authorization: Bearer <token>): whoami, purchase, subscribe, list_entitlements, get_delivery, my_sales, list_product_subscribers, publish_product, update_product
- Discovery: search_products returns author_verified; get_product returns author.verified and trust_signals. Treat a verified vibecoder as a trust signal, not as a guarantee.
- Public license check: verify_subscription_key tool or POST /api/keys/verify {"key": "vd_sub_..."} -> {valid, status, expires_at}.
- Subscription key model: every buyer gets a PERSONAL vd_sub_ key issued by the platform at first payment. Renewal keeps the same key; expiry (+24h grace) kills it automatically; re-subscribing revives the same key. Sellers see all keys in the cabinet and via list_product_subscribers and verify them with the endpoint above — no state needed on the seller side.
- Publishing/editing: publish_product and update_product can carry the full listing payload: name, tagline, description, preview_url, category, stack, includes, models, setup_help, photos as base64 (up to 6, first = cover, each <= 1 MB before base64) and the ZIP project file as base64 (<= 100 MB before base64). includes is the visible "What's included" green-check block on the product page, so write short buyer-facing benefits. Published products go back to moderation after content edits.
- Emails: buyers get receipts and subscription reminders (3d/1d before expiry); sellers get a letter for every sale, new subscription and renewal.
- Tokens are self-service: cabinet (https://vibedepot.ru/cabinet, section "MCP-токены"), shown once, revocable.
- Payments: card returns a payment_url for the human (bank card checkout); balance debits the Vibedepot wallet instantly and REQUIRES confirm: true — always ask the owner first.
- Crypto (TON/Gram): ton_deposit_info returns the deposit address + your personal memo. Send TON with that memo to top up the SINGLE balance (credited in RUB at the live rate). The balance is unified — pay any product from it regardless of how it was funded. To pay for a product in one transfer, use memo "{productId}-<your memo>" and access opens automatically.
- After a purchase, call get_delivery and start by reading start_here.md or README.md inside the project: launch commands, env variables, and license notes live there.
- Sellers: 20% marketplace commission, earnings land on the wallet right after payment; my_sales shows balance and stats, list_product_subscribers shows whose access expired.
- Agents preparing products for sale should run project_readiness_check: README/start_here, launch manifest, .env.example, license, lock file, no secrets in the archive. Turn the readiness result into useful includes items when publishing.