Can Developers Build on AGI, Inc.'s Platform, and What Should They Evaluate?

Updated

Yes—AGI, Inc. explicitly invites developers to build on its platform, and its site claims you can "ship a working action agent in less than a day." That claim is worth testing against your own use case, because the platform's design choices (an on-device action model, no API integrations, screen-level control) shape both what you can build and what you need to verify before committing.

What the platform is built on

AGI, Inc. builds AGI-0, described as a small action model that lives on the device, plus an agent that sees the screen and acts across any app on Android. Two properties follow from that architecture and matter most to developers:

  • No APIs or integrations required. The agent operates through the screen rather than through app APIs, so in principle it can act inside apps that expose no developer interface.
  • Private by design and on-device. The model runs locally, learns user preferences over time, and the company states it works offline, on wearables, and for privacy-sensitive tasks.

The site also reports that AGI-0 scores 100% on AndroidWorld (116/116 tasks). Treat that as a vendor-reported benchmark: it tells you the model handles a defined task suite, not that it will handle your specific workflows.

Evaluate these dimensions before you build

Dimension What the site says What to verify with AGI, Inc.
Time to first agent "Ship a working action agent in less than a day" What "working" means in the platform's terms—scope of a minimal agent, and what setup precedes it
Device and OS coverage Android; also mentions wearables and computer Exact supported devices and OS versions for your target users
App coverage Acts across any app via screen understanding Behavior in your specific apps, including ones with unusual UI or login flows
Integration model No APIs or integrations How your backend or data connects, if at all, given the screen-level approach
Privacy handling On-device model, works offline, private by design Data flows during setup, updates, and any cloud-assisted steps
Access "Get access" and "Book a call" on the site Access conditions, onboarding steps, and any commercial terms

The access row deserves emphasis: the site offers "Get access" and "Book a call" rather than self-serve signup details, and it publishes no pricing. Do not assume free or open access—confirm eligibility and terms directly.

A practical evaluation path

  1. Define one narrow task you would want an agent to complete—for example, ordering a specific set of grocery items in a shopping app, or booking a ride conditionally when a train is delayed (both are task types the site itself illustrates).
  2. Request access and book a call through the site's "Get access" and "Book a call" entry points, and ask specifically about supported devices, app coverage, and privacy handling during onboarding.
  3. Build the smallest agent the platform allows and time it, to test the "less than a day" claim against your team's actual setup effort.
  4. Test on your real apps and devices, not just demo scenarios—screen-based agents are sensitive to UI variation, so check the apps your users rely on.
  5. Confirm the privacy story end to end, since on-device operation is the platform's central selling point and the main reason to choose it over API-based automation.

When this platform fits—and when it doesn't

It is a reasonable fit if you need an agent that operates inside third-party Android apps you don't control, and if keeping action data on the device is a priority for your users or your compliance posture. It is a weaker fit if your workflows already have clean APIs (direct integration will be more predictable), if you need platforms beyond those AGI, Inc. supports, or if you require published pricing and self-serve onboarding before you can start.

The decisive step is the call: the site's claims about speed, coverage, and privacy are specific enough to test, but the access and commercial details you need for a build decision are not on the page.