How to deploy an AI twin inside WeChat and WeCom with Myriad Masters — and how E.I System, XApp, commerce and data boundaries turn expertise into real service.
Is Myriad Masters a chatbot?
No. Myriad Masters is a platform for intelligent service and AI applications. Chat is good for understanding a need, explaining and accompanying; the platform also uses XApp to carry structured delivery — assessments, forms, reports, records, courses and tools — alongside operations, resources, entitlements and developer tools.
Who is it for?
For practitioners, teachers, consultants, shop owners and creators with industry experience or local influence; also for official-account operators, WeCom service teams, course and consulting providers, individual IP, AI app creators and developers who want AI inside real business.
Why call it an operations platform?
Because it does more than generate replies: it manages accounts, assistant configuration, message automation, apps, data, products, membership, resources and orders. AI capability ends up in acquisition, service, delivery and repeat purchase.
Can Vibe Coding ship a commercial product directly?
It lowers the barrier from idea to implementation a lot, but a commercial product still needs identity and permissions, data, publishing, an operations backend, resources, payment and acceptance. The value here is bringing those foundations into one workflow — not promising that generated code goes live without testing.
Can I commission the team to build it?
Yes. A bespoke build can co-create official accounts, WeCom, several XApps, intelligent service and operations configuration — or just one XApp. Scope, responsibilities, milestones and price are assessed per project; WeChat verification, merchant qualification and third-party review are still completed with the client.
Can accounts and WeCom be connected quickly?
The platform tries to pull creation, configuration, validation and operations into one console. A basic workspace and digital staff can start fast, but WeChat-side verification, review and merchant configuration follow the third party's actual process.
Scheduled broadcasts and automatic reach?
Yes — message templates, one-off broadcasts, scheduled broadcasts, automatic rules and multilingual content.
How do accounts and WeCom staff divide the work?
Official accounts suit content reach, follow relationships, menu entry points and membership; WeCom digital staff suit service enquiries, customer follow-up, human collaboration and sales orders. They can share one agent design, but the operating scenarios differ.
What if a user sends images, voice, video or files?
Those inputs become context the agent can understand, so replies do not depend on text alone. Externally, think of it as multimodal service.
I have connected an official account — how do I add a mini program?
Prepare your own mini-program AppID and AppSecret, then go to Operations Centre → WeChat Mini Program, choose the official account, and follow the wizard through credential verification, domain configuration and binding a published XApp. Then get the mini-program builder in the Developer Centre and build native pages with WorkBuddy.
See where each step happens →Does the mini program share accounts and data with the XApp?
Yes. Once a user verifies with the phone number of their existing Myriad account, that account carries over. A bound XApp means the same logic tables and permissions; the web and mini-program front ends are built separately.
Does my existing account need a UnionID?
No. Existing login keeps working; mini-program access does not require UnionID — the first visit links the user to their own Myriad account by phone verification.
Which agent can the mini program call?
Today it uses the text agent already bound to the official account through the native SDK, with the same role, knowledge and quota; web and mini program keep separate conversation context. Multimodal agents are not connected yet, so not every web feature carries over.
Where does the mini-program code live — Myriad or WeChat?
Your machine holds the development project; Myriad's private OSS keeps independent source history; WeChat stores and distributes the compiled runtime package after upload. Pinning a source version is not the same as uploading, submitting for review or releasing.
Do API and file requests need domain configuration?
Yes. In the WeChat console, set the request and downloadFile domains exactly as the Operations Centre wizard shows. Allowing a domain does not replace account, data or private-file authorisation.
Can I just copy the XApp pages?
No — a web Bridge and HTML do not run as a native mini program. The mini program uses native pages, the Myriad SDK and XAUI native WXSS: shared business resources and one visual language, but the front end still has to be written and adapted.
Are product payment and file upload supported?
Today: product and membership queries, plus authorised file downloads. Native payment, runtime user uploads and multimodal agents are not connected yet.
See current capabilities →Does the builder publish to WeChat automatically?
The builder saves source, pins versions and exports the project; uploading, submitting for review and releasing still happen in the authorised channel and the WeChat console, subject to each stage's receipt. WorkBuddy's share panel and Myriad account data access are separate steps.
Is XApp a page generator?
No. An XApp is a cross-agent application that can be distributed on its own or plugged into WeChat and WeCom: workspace, mobile visuals, logic data, assets, private resources, user uploads, agent calls, permissions, products and a release flow.
Can an XApp charge money?
It can use a product showcase, VIP permissions, private-resource licensing and payment callbacks, so an app can grow from free trial into paid content or service. WeChat Pay depends on JSAPI, merchant qualification and actual configuration; other payment methods are assessed separately.
How is it different from an ordinary H5 page?
An ordinary H5 usually only handles presentation. An XApp also handles app identity, access mode, file workspace, data tables, assets, private resources, agent calls, release history and commercial entitlements.
What kinds of XApp can I build?
Today: course learning, surveys, AI image recognition, learning and health records, video courses, material delivery, paid content, light tools and official tutorials.
Does app data flow into agent memory automatically?
Not indiscriminately. App data, private resources and user uploads each have isolation boundaries; only result summaries, stages or events that the user has authorised and the service rules allow are suitable as service context or follow-up signals.
How is a task agent different from a prompt?
A prompt is usually a one-off description. A Myriad Masters task agent is a maintainable service configuration: positioning, tone, service rules, knowledge, FAQ, memory, edge cases and automation.
What is E.I System?
E.I System is the empathic layer for long-term relationship service. It combines timing, layered memory, user state, a stable role goal and multimodal input to understand the present need, then chooses to listen, explain, recommend, follow up or hand over. Memory scope, proactive strategy and generation are authorised, configured and accepted per scenario.
Is SVIP just AI conversation quota?
No. SVIP is a platform-wide entitlement covering accounts, apps, agents, resources, products, developer tools and AI usage quota.
Will the annual price stay the same?
What you see is a limited early-bird annual plan; availability and price may change with platform policy. The checkout page inside the platform is final.
SVIP vs WeChat VIP vs resource entitlements?
SVIP is about how much you create and operate on the platform; WeChat VIP is membership under one official account or WeCom account; resource entitlements licence access to specific course material, files, content packs or digital services.
How are purchased resources delivered?
The platform manages the licence window for resource entitlements. After purchase or membership grant, the user can reach the authorised content in the matching account, WeCom or XApp scenario.
Is a platform subscription the same as a customer buying a product?
No. SVIP is the operator's right to create and operate on the platform; end customers buying courses, resources, consulting or app entitlements are your own transactions. Prices, merchants, entitlements and delivery rules are configured separately.
Does SVIP include bespoke builds?
No. SVIP is a platform subscription; a bespoke build is an official service scoped and quoted per project, for co-building a full IP service product or a single XApp.
Why MCP?
MCP lets AI workbenches such as Codex, WorkBuddy and Claude call platform capabilities inside authorisation boundaries, cutting repetitive clicking and throwaway scripts so AI can take part in app development, agent design and platform administration.
Does the AI tool get full backend access?
It should not be read that way. Think controlled collaboration inside boundaries: AI operates platform capabilities around the current user, current app and an explicit task, while high-impact actions keep confirmation and audit.
Which development work does it suit?
Real platform tasks: creating and iterating XApps, managing files and assets, maintaining logic tables, configuring agents, verifying releases, configuring products and resources, and diagnosing plugin connections.
How are public assets and private resources separated?
Public assets are for display and reuse; private resources are for courses, material, files and paid content that need licensing. Different spaces carry different boundaries and access methods.
How do service context and privacy balance?
By minimum necessity and explicit purpose: isolate app data first, then let user authorisation and service rules decide which result summaries, stages or events may be used later. Sensitive raw data, cross-app use and deletion rules are specified per project.
What about high-risk situations?
The platform supports edge cases, risk records, human collaboration and permission boundaries. AI should not replace every human decision; high-impact moments keep the operator's judgement.
Why not publish more low-level technical detail?
Message flows, resource paths, keys, internal tool names and risk rules are not appropriate to publish. A commercial portal should explain value, boundaries and deliverable outcomes rather than expose implementation.
