Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is AGI, Inc.?
AGI, Inc. is a company building on-device “action AI” for phones and computers. Its main product, AGI-0, is described as a small action model paired with an agent that sees the screen and acts across apps on Android—handling tasks through the interface rather than through APIs or integrations. The emphasis is on privacy (processing on the device), speed, and hands-free operation. The site also mentions a platform for developers to build action agents.
What it appears to do
- Act across apps by reading the screen and performing actions, rather than relying on app APIs.
- Run locally on the device, which supports offline use and privacy-sensitive tasks.
- Learn user preferences over time and act as a “proactive collaborator.”
- Support examples such as ordering groceries, booking a ride based on travel conditions, scheduling lessons, and finding and playing a playlist from a message.
Who it is for
- Everyday Android users who want to offload repetitive multi-app tasks and reduce screen time.
- Privacy-conscious users who prefer on-device processing to cloud-based agents.
- Developers interested in shipping an action agent using the company’s platform.
Trade-offs to weigh
The screen-based approach can work with apps that lack APIs, but it may be more fragile than direct integrations when interfaces change. On-device processing helps privacy and offline use, though the site’s claim of 100% on AndroidWorld (116/116 tasks) is a benchmark result, not a guarantee for arbitrary real-world tasks.
Next step: If you use Android and have a repetitive multi-app workflow, identify one concrete task—such as reordering a standard grocery list—and check whether AGI-0 supports your device and apps before relying on it for anything time-sensitive.
How does AGI-0 control apps on my Android phone without APIs or integrations?
AGI-0 works by seeing the screen and acting on it the way a person would, rather than connecting to apps through their APIs. According to the product's page, it is an on-device action model that "sees the screen and acts across any app on Android," and the company describes it as needing "no APIs or integrations."
In practice, that means the agent interprets what is displayed—buttons, menus, text fields, lists—and then performs the taps, typing, and navigation that complete a task. Because it operates through the visible interface, it can reach apps that never offered an integration path. The page's own examples show this pattern: ordering ingredients in Instacart, comparing a train against a ride and booking one, finding tennis lessons that fit a schedule, and pulling a playlist from Messages to play in Spotify.
What this design buys you
- Coverage: Any app with a usable screen is potentially in scope, including ones with no public API.
- Privacy: The model lives on the device, so the page states it works offline and on wearables, which suits privacy-sensitive tasks.
- Personalization: It learns your preferences over time, so repeated tasks can get smoother.
The trade-offs to weigh
- Interface dependence: Screen-based control is only as reliable as the screen itself. Layout changes, pop-ups, or unusual states can trip up any agent working this way, so expect occasional supervision on multi-step tasks.
- Platform scope: The page frames this around Android phones and computers; check current device support before assuming your hardware is covered.
- Verification: The page cites a 100% result on AndroidWorld (116/116 tasks), a benchmark of scripted Android tasks. Treat that as evidence of capability on standardized tests, not a guarantee for your particular banking app or a messy real-world flow.
A useful next step: pick one recurring chore—say, a weekly grocery order—and run it with the agent while watching the first few times. If it completes the flow cleanly, expand to tasks with more steps, like the travel example where it checks the train before booking a ride. For background on the Android ecosystem the agent operates within, see Android.
Is AGI-0 private enough for sensitive tasks like banking or messaging?
AGI-0 is designed for privacy-sensitive use: the model runs on the device, and the agent works by seeing the screen and acting across apps without APIs or integrations. That architecture is the main reason it can plausibly handle messaging and other sensitive tasks—your data doesn't need to leave the phone to drive the automation. AGI, Inc. also explicitly positions offline use and privacy-sensitive tasks as supported scenarios.
For banking specifically, treat that as a judgment call rather than a settled yes. On-device processing reduces exposure, but an agent that reads your screen and taps through apps still sees whatever is displayed, including balances and one-time codes. Whether that's acceptable depends on your own risk tolerance and on controls the product may or may not offer (confirmations before actions, app exclusions, logging). The site's evidence covers the privacy model, not a banking-specific guarantee.
A practical way to decide:
- Messaging: a good fit for drafting, finding a playlist a contact sent, or scheduling—low-stakes actions where an on-device agent saves real time.
- Banking and payments: start with read-only or low-value tasks and keep human confirmation on anything that moves money.
- Anything regulated or irreversible: verify what confirmation and audit features exist before relying on it.
As a next step, test one contained task in each category—ask it to find a message and summarize it, then watch exactly what it does before letting it act on a financial app. For comparison on how other assistant approaches handle on-device versus cloud processing, Apple describes its own on-device privacy approach for Apple Intelligence.
How do I get access to AGI-0 or try a demo on my own device?
The site presents AGI-0 as an on-device action model for Android, and its access path is a request rather than a public download: the page offers "Get access" alongside "Book a call," so the practical route is to request access for your device and, if you want to see it first, watch the demo linked from the homepage. There is no indication of a self-serve install or a public trial build, so treat access as something granted after contact rather than something you can set up yourself today.
What to expect from the request
- Device fit: AGI-0 is described as working on Android by seeing the screen and acting across apps, without APIs or integrations. If your target device isn't Android, ask directly whether anything is available for it.
- Privacy claims: the page says the model lives on the device and works offline. Ask how that holds for the specific tasks you care about, since any action that reaches a live service still depends on that app.
- Evaluation evidence: the site cites 100% on AndroidWorld (116/116 tasks). That's a benchmark result, not a guarantee for your own apps and accounts, so plan a small set of real tasks to test.
A useful next step
Before you book a call, write down three tasks you'd want it to complete on your own phone—for example, ordering a specific grocery list, booking a ride conditionally on a delay, or finding something in your messages and playing it. Bring those to the conversation and ask whether they can be demonstrated on your device or a comparable one. If a hands-on trial isn't offered, ask what the demo shows and which apps it covers, so you can judge the gap between the demo and your daily use.
For broader context on on-device assistant approaches, Android covers platform-level automation features, though they differ from a screen-reading action agent.
Can developers build their own action agent using AGI, Inc.'s platform?
Yes. AGI, Inc. presents a platform aimed at developers, and its page states that you can "ship a working action agent in less than a day" by dropping the platform in. The company's own product, AGI-0, is described as a small on-device action model that sees the screen and acts across apps on Android without APIs or integrations, so the platform is positioned around that same screen-based approach rather than app-by-app connectors.
What that means in practice
- Screen-level control: An agent built on this approach would interpret what is on screen and act, rather than relying on each app's API. That suits Android apps that have no public API or where integrations are impractical.
- On-device emphasis: The page stresses that AGI-0 runs locally, works offline, and is "private by design." Developers building privacy-sensitive or offline tools should treat that as the intended design direction.
- Fast prototyping: The "less than a day" claim is a vendor statement about time to a working agent. Treat it as an aspiration to test, not a guarantee; a realistic first milestone is a single, well-scoped task on one app.
A concrete reader scenario
A developer wants an agent that reads a message containing a playlist link and opens it in a music app. With a screen-based agent, the flow is: observe the messaging screen, identify the relevant message, then act in the music app. That is the kind of cross-app task the page highlights, and it is a sensible first project to validate the platform before expanding to shopping or travel workflows.
Decision criteria
| If your priority is… | Consider |
|---|---|
| Apps without APIs, Android-only | Screen-based action fits well |
| Strict data locality or offline use | On-device design is the main draw |
| Deep, reliable integrations in many services | API-based agent frameworks may be more predictable |
| A quick proof of concept | Start with one task, one app, and measure success |
Next step: Define a single test task with a clear pass/fail (for example, "find the playlist message and start playback"), then check the platform's documentation and access terms at AGI, Inc. to confirm device requirements and how to get access before committing engineering time.
How does AGI-0 compare to other phone AI assistants in real-world task performance?
AGI-0's own benchmark claim is unusually specific: the site says it scores 100% on AndroidWorld (116/116 tasks). Treat that as a figure published by AGI, Inc. on its own site, not an independent comparison. The site's pitch is that AGI-0 works by seeing the screen and acting across any app on Android, with no APIs or integrations, and runs on the device. That approach is what would let it handle apps that other assistants can't reach, and it's also where its limits would show.
What the claim does and doesn't tell you
AndroidWorld is a set of scripted Android tasks, so a perfect score speaks to completing those defined flows reliably. It says little about the messier conditions of daily use: apps that change layout, logins and two-factor prompts, payment confirmations, or tasks that need a judgment call. A real-world comparison would look at:
- Coverage: whether the assistant can act in the apps you actually use, rather than only in apps with official integrations.
- Reliability under change: how it behaves when a screen looks different from what it was trained on.
- Privacy: whether actions and screen contents stay on the device. AGI, Inc. says AGI-0 lives on the device and works offline, which matters for banking, health and messaging.
- Recovery: what happens when a step fails halfway through a booking or order.
How to judge it against alternatives
| Criterion | Why it decides the comparison |
|---|---|
| Integration model | Screen-reading agents can reach more apps but are more fragile; API-based assistants are steadier but limited to supported services |
| Where processing happens | On-device favors privacy and offline use; cloud assistants often handle heavier reasoning |
| Task type | Ordering groceries or booking rides suits an action agent; open-ended questions may suit a conversational assistant |
| Failure handling | Ask what it does when a confirmation screen or CAPTCHA appears |
A practical next step: pick three tasks you do weekly, such as reordering groceries, booking a ride when your train is late, and finding a playlist a friend sent. Run each on AGI-0 and on whatever assistant your phone ships with, and note where each one stalls. That tells you more about real-world fit than any single benchmark. For background on the broader assistant landscape, OpenAI and Google DeepMind publish material on their own agent work.
User reviews (0)