OpportunitiesEntities
Docs
    Ring Platform

    Decentralized Self-building Future

    Sign In
    Entities
    Opportunities
    Store
    Docs
    Platform Concepts
    RING EconomySonoratek LLCGlobal ImpactAI Meets Web3
    Get Started
    Quick StartCalculatorRoadmap
    Privacy|Contact
    v1.104.17|Sonoratek LLC

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Ring Logo

    Loading documentation...

    Preparing Ring content

    Ring Logo

    Loading documentation...

    Preparing Ring content

    Ring Logo

    Loading documentation...

    Preparing Ring content

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Login via Telegram (OIDC) or Mini App initData auth. Member auth: Authentication. Stars membership: SubscriptionConductor.

    Ring ships a Telegram Admin Bot so platform admins can moderate news, run selected admin operations, and receive approval callbacks without opening the web admin UI — while still obeying the same RBAC SSOT as /admin.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    Do not confuse these Telegram surfaces

    SurfaceAudienceSecret / crypto
    Login via TelegramMembers (browser)AUTH_TELEGRAM_ID / SECRET — OIDC at oauth.telegram.org
    Mini App initDataMembers (WebApp client)WebAppData HMAC — TELEGRAM_MINI_APP_BOT_TOKEN (fallbacks documented on Authentication)
    Link Telegram (profile)Logged-in membersLogin Widget HMAC with ADMIN_BOT_TOKEN / TELEGRAM_LOGIN_BOT_TOKEN
    telegram_stars membershipPaying membersSame Mini App bot token + Bot API createInvoiceLink — SubscriptionConductor
    Admin bot (this page)Platform admins

    Why operators use Telegram

    Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

    Trust & Brand fit

    Telegram management sits with authentication, security, and verification:

    • Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
    • Destructive actions (user delete, platform settings) stay superadmin-only.
    • Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user via communication.telegramId
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit

    Related documentation

    Related documentation

    Authentication

    Prerequisite: member Login via Telegram OIDC + Mini App initData vs this admin bot.

    SubscriptionConductor

    See-also: telegram_stars invoices share the Mini App bot token helper — not this admin webhook.

    News Kingdom architecture

    Same-workflow: scoring, promotion, and Telegram approve callbacks.

    Autonomous Newsroom (Grok)

    Next-step: draft → image → Telegram approve pipeline.

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Login via Telegram (OIDC) or Mini App initData auth. Member auth: Authentication. Stars membership: SubscriptionConductor.

    Ring ships a Telegram Admin Bot so platform admins can moderate news, run selected admin operations, and receive approval callbacks without opening the web admin UI — while still obeying the same RBAC SSOT as /admin.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    Do not confuse these Telegram surfaces

    SurfaceAudienceSecret / crypto
    Login via TelegramMembers (browser)AUTH_TELEGRAM_ID / SECRET — OIDC at oauth.telegram.org
    Mini App initDataMembers (WebApp client)WebAppData HMAC — TELEGRAM_MINI_APP_BOT_TOKEN (fallbacks documented on Authentication)
    Link Telegram (profile)Logged-in membersLogin Widget HMAC with ADMIN_BOT_TOKEN / TELEGRAM_LOGIN_BOT_TOKEN
    telegram_stars membershipPaying membersSame Mini App bot token + Bot API createInvoiceLink — SubscriptionConductor
    Admin bot (this page)Platform admins

    Why operators use Telegram

    Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

    Trust & Brand fit

    Telegram management sits with authentication, security, and verification:

    • Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
    • Destructive actions (user delete, platform settings) stay superadmin-only.
    • Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user via communication.telegramId
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit

    Related documentation

    Related documentation

    Authentication

    Prerequisite: member Login via Telegram OIDC + Mini App initData vs this admin bot.

    SubscriptionConductor

    See-also: telegram_stars invoices share the Mini App bot token helper — not this admin webhook.

    News Kingdom architecture

    Same-workflow: scoring, promotion, and Telegram approve callbacks.

    Autonomous Newsroom (Grok)

    Next-step: draft → image → Telegram approve pipeline.

    Manage via Telegram

    Use Founder / Developer tabs in the docs sidebar. This is the admin bot for operators — not member Login via Telegram (OIDC) or Mini App initData auth. Member auth: Authentication. Stars membership: SubscriptionConductor.

    Ring ships a Telegram Admin Bot so platform admins can moderate news, run selected admin operations, and receive approval callbacks without opening the web admin UI — while still obeying the same RBAC SSOT as /admin.

    ConcernTruth
    WebhookPOST /api/telegram/admin-bot/webhook
    Codelib/telegram/admin-bot/
    RBACfeatures/auth/user-role.ts — isPlatformAdmin / isSuperadmin
    News approvalBot callbacks + News / News Kingdom

    Do not confuse these Telegram surfaces

    SurfaceAudienceSecret / crypto
    Login via TelegramMembers (browser)AUTH_TELEGRAM_ID / SECRET — OIDC at oauth.telegram.org
    Mini App initDataMembers (WebApp client)WebAppData HMAC — TELEGRAM_MINI_APP_BOT_TOKEN (fallbacks documented on Authentication)
    Link Telegram (profile)Logged-in membersLogin Widget HMAC with ADMIN_BOT_TOKEN / TELEGRAM_LOGIN_BOT_TOKEN
    telegram_stars membershipPaying membersSame Mini App bot token + Bot API createInvoiceLink — SubscriptionConductor
    Admin bot (this page)Platform admins

    Why operators use Telegram

    Missile-hour ops and travel-friendly moderation: approve newsroom drafts, check critical queues, and keep an audit trail — without VPN into a desktop admin session.

    Trust & Brand fit

    Telegram management sits with authentication, security, and verification:

    • Only whitelisted Telegram IDs mapped to Ring admin / superadmin users can talk to the bot.
    • Destructive actions (user delete, platform settings) stay superadmin-only.
    • Admins must first link Telegram on their Ring profile (or sign in via Telegram OIDC so communication.telegramId is set) before the whitelist can see them.

    Security

    Defense layers and admin posture.

    News

    Telegram approval in the newsroom pipeline.

    Implementation

    Modules

    PathRole
    app/api/telegram/admin-bot/webhook/route.tsTelegram updates ingress
    lib/telegram/admin-bot/bot-config.tsToken, webhook secret, setWebhook
    lib/telegram/admin-bot/whitelist.tsMap Telegram chat → Ring admin user via communication.telegramId
    lib/telegram/admin-bot/ring-api-executor.tsOperation-level RBAC before Ring HTTP
    lib/telegram/admin-bot/news-callback-handler.tsInline news approve/reject
    lib/telegram/admin-bot/anthropic-router.tsOptional NL → tool routing
    lib/telegram/admin-bot/audit-logger.tsInteraction audit

    Related documentation

    Related documentation

    Authentication

    Prerequisite: member Login via Telegram OIDC + Mini App initData vs this admin bot.

    SubscriptionConductor

    See-also: telegram_stars invoices share the Mini App bot token helper — not this admin webhook.

    News Kingdom architecture

    Same-workflow: scoring, promotion, and Telegram approve callbacks.

    Autonomous Newsroom (Grok)

    Next-step: draft → image → Telegram approve pipeline.

    ADMIN_BOT_TOKEN + ADMIN_BOT_WEBHOOK_SECRET + whitelist

    Authentication

    Member Login via Telegram OIDC + roles the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: https://<your-domain>/api/telegram/admin-bot/webhook (HTTPS in production). Validate secret_token via validateWebhookSecret.

    Member Login OIDC uses different env: AUTH_TELEGRAM_ID / AUTH_TELEGRAM_SECRET — see Authentication.

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    PathRole
    features/auth/components/telegram-signin-button.tsxLogin via Telegram OIDC
    lib/auth/telegram-oidc.tsAuth.js OIDC provider
    lib/auth/telegram-miniapp-initdata.tsMini App WebAppData HMAC + bot token helper
    features/auth/components/telegram-linking-modal.tsxLegacy Login Widget linking
    app/api/auth/telegram/callback/route.tsWidget callback (session required)
    lib/auth/telegram-login-widget-hash.tsShared widget HMAC
    lib/payments/subscription/providers/telegram-stars-subscription.tsStars XTR invoices

    Ring MCP Server

    See-also: IDE MCP twin for the same clone’s admin operations.

    Admin API

    Depends-on: web admin HTTP surfaces the bot mirrors carefully.

    ADMIN_BOT_TOKEN + ADMIN_BOT_WEBHOOK_SECRET + whitelist

    Authentication

    Member Login via Telegram OIDC + roles the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: https://<your-domain>/api/telegram/admin-bot/webhook (HTTPS in production). Validate secret_token via validateWebhookSecret.

    Member Login OIDC uses different env: AUTH_TELEGRAM_ID / AUTH_TELEGRAM_SECRET — see Authentication.

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    PathRole
    features/auth/components/telegram-signin-button.tsxLogin via Telegram OIDC
    lib/auth/telegram-oidc.tsAuth.js OIDC provider
    lib/auth/telegram-miniapp-initdata.tsMini App WebAppData HMAC + bot token helper
    features/auth/components/telegram-linking-modal.tsxLegacy Login Widget linking
    app/api/auth/telegram/callback/route.tsWidget callback (session required)
    lib/auth/telegram-login-widget-hash.tsShared widget HMAC
    lib/payments/subscription/providers/telegram-stars-subscription.tsStars XTR invoices

    Ring MCP Server

    See-also: IDE MCP twin for the same clone’s admin operations.

    Admin API

    Depends-on: web admin HTTP surfaces the bot mirrors carefully.

    ADMIN_BOT_TOKEN + ADMIN_BOT_WEBHOOK_SECRET + whitelist

    Authentication

    Member Login via Telegram OIDC + roles the bot must respect.

    Typical scenarios

    • Autonomous newsroom draft arrives → admin taps Approve in Telegram → locale fan-out.
    • On-call admin checks verification / order status via bot commands (platform-admin paths).
    • Failed or unauthorized attempts are audit-logged.
    lib/telegram/admin-bot/TELEGRAM_BOT_RBAC.mdRBAC policy SSOT (in-repo)

    Env (verified names)

    Webhook URL shape: https://<your-domain>/api/telegram/admin-bot/webhook (HTTPS in production). Validate secret_token via validateWebhookSecret.

    Member Login OIDC uses different env: AUTH_TELEGRAM_ID / AUTH_TELEGRAM_SECRET — see Authentication.

    RBAC layers

    1. Whitelist — sender Telegram ID must map to a Ring user in PLATFORM_ADMIN_ROLES.
    2. Executor — per-operation checks in ring-api-executor.ts.
    3. Ring HTTP APIs — session/MCP auth re-validates; bot must not bypass SSOT.

    Strict superadmin examples: user delete, platform branding / AI settings mutations. Platform admins: news moderation, selected order/wallet/verification paths — see TELEGRAM_BOT_RBAC.md.

    Related member Telegram (not this bot)

    PathRole
    features/auth/components/telegram-signin-button.tsxLogin via Telegram OIDC
    lib/auth/telegram-oidc.tsAuth.js OIDC provider
    lib/auth/telegram-miniapp-initdata.tsMini App WebAppData HMAC + bot token helper
    features/auth/components/telegram-linking-modal.tsxLegacy Login Widget linking
    app/api/auth/telegram/callback/route.tsWidget callback (session required)
    lib/auth/telegram-login-widget-hash.tsShared widget HMAC
    lib/payments/subscription/providers/telegram-stars-subscription.tsStars XTR invoices

    Ring MCP Server

    See-also: IDE MCP twin for the same clone’s admin operations.

    Admin API

    Depends-on: web admin HTTP surfaces the bot mirrors carefully.

    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...
    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...
    bash
    
ADMIN_BOT_TOKEN=...
ADMIN_BOT_WEBHOOK_SECRET=...
    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 20, 20264 min listen
    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 20, 20264 min listen
    1. Docs
    2. /Features
    3. /Manage via Telegram
    Updated Jul 20, 20264 min listen