Abao goes public beta: can one sentence really start a day of errands?
Ant Group is moving Abao from invitation-only testing to public beta, tying payments, travel, bills, and local services into task flows started in plain language.
Alipay announced the public beta of Abao on July 2, 2026. iOS and Android users can search for “Abao” or “Ant Abao” in app stores or inside Alipay without an invitation code. Public reporting confirms an initial guide to 72 life-service skills across travel, bills, shopping, and government services.
It routes services; it does not replace payment approval
In the official provident-fund example, Abao matches the user's request to the relevant mini-program and screen, but the user still signs in and confirms the action. Alipay also says that any step involving money movement or payment remains subject to the user's confirmation.
That boundary matters. The accurate description today is “use natural language to find and connect services,” not “AI completes every errand automatically.” Fewer menu taps can be tested immediately. Reliable handling of complex conditions, city-specific rules, and exceptions requires longer-term evidence that a launch post cannot provide.
Seventy-two skills do not mean seventy-two fully automated tasks
A skill may be a lookup, recommendation, deep link, form assistant, or end-to-end flow. Evaluate the workflow rather than counting labels:
- How many manual steps remain after the request?
- Are source, price, location, and eligibility shown?
- Can the user recover from a wrong interpretation?
- Do identity, money, and government actions have a clear confirmation screen?
For health insurance, provident funds, identity documents, or financial information, a recommendation does not replace the official rule or human verification.
How to test it safely
Start with low-risk tasks such as finding an entry point, locating a bill, or comparing nearby services. Do not begin with payments, identity documents, or an important booking. Check the destination service, the account information used, and exactly what the final confirmation will do.
Abao's value depends on proving three things over repeated use: shorter paths, accurate results, and recoverable errors. Public beta proves availability, not that all three have already been solved.
Sources
Related
STEPX Neo, Step AOS, and Amoo bring the agent-phone idea into focus. The test is not a smooth demo; it is whether cross-app permissions, approval for consequential actions, and recovery from mistakes are real.
PixVerse has shown a game-engine architecture that combines a real-time world model, game rules, and agent orchestration. It may reduce the cost of expressing a prototype, but it has not yet proved itself on latency, rule stability, or cost.