asaply vs GAIA

asaply

asaply is a text-only errand assistant in early access that orders, books and pays through Apple Pay after showing the total, and can read and change a connected Google Calendar and Gmail. No outside agent can call it, the service fee isn't published, and no status page or security contact was found.

GAIA

GAIA's source is public, so its approval gate, memory store and token handling can be read. Three approval modes and per-tool overrides exist, but the default mode in the source runs every action unasked, which the privacy policy and release notes do not say. Pro costs $30 a month and self-hosting is limited to noncommercial use.

asaply

1. Don't plan to call asaply from another agent. It answers only texts from the owner's phone number and group chats it joins.
2. Tell the owner each errand adds an unpublished service fee to the order total.

GAIA

1. Set Settings > Approvals to Always ask or Auto before connecting mail. The default in the source runs every action, including send and delete, without asking.
2. Expect no public API on the hosted service. The backend turns off its OpenAPI document in production, so reach GAIA through its apps, bots or CLI.
3. Check the plan before relying on the hosted service. The README and docs describe a Free plan, and the pricing page says GAIA is a paid product.
4. For self-hosting, prepare Docker, Node.js 20, a WorkOS account and a model key first, and confirm the use is noncommercial under the licence.
5. Add outside tools as MCP servers by URL on the Integrations page. GAIA asks before adding a server in every approval mode.