Head to head · Assistants that act in your accounts · October 2026 research run
IronClaw vs Wajo (Fo)
IronClaw scores 66.7 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in 6 of 7 scored categories. Both do assistants that act in your accounts.
Best AI personal assistants that act for one person · All 314 assistants comparisons
Which one, for what
IronClaw B
Best for One technical owner who wants a self-hosted assistant over Gmail, Calendar, Slack and Telegram with credentials kept out of the model's reach.
Ahead on
- Reliability, 67 against 30
- Security & auth, 66 against 38
- Payments & pricing, 60 against 30
- Maintenance & community, 74 against 3
- Transparency & trust, 75 against 47
Also in its favour
- Open source
Watch for
Global auto-approve defaults to on in the 1.4.1 source, so tools marked ask (send, trash, delete) run without a prompt. Only financial, approval and budget effects always ask
Best for An agent or AI app that needs to hand a person's errands, calls and purchases to a hosted assistant over MCP.
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
No status page, changelog or security contact found.
Score by category
| Category | Weight this run | IronClaw | Wajo (Fo) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 67 | 30 | IronClaw +37 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 74 | 74 | even |
| Agent ergonomics | 13%16.2 | 69 | 68 | IronClaw +1 |
| Security & auth | 14%17.5 | 66 | 38 | IronClaw +28 |
| Payments & pricing | 10%12.5 | 60 | 30 | IronClaw +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 74 | 3 | IronClaw +71 |
| Transparency & trust | 7%8.8 | 75 | 47 | IronClaw +28 |
| Negative events | ≤15 | -2 | 0 | |
| Total | B 66.7/100 | E 43.9/100 |
Facts side by side
| Fact | IronClaw | Wajo (Fo) |
|---|---|---|
| Kind | Agent harness | Platform |
| Vendor | NEAR AI | Wajo, Inc. |
| Hosted endpoint | no (local only) | https://mcp.api.wajo.ai/mcp |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT OR Apache-2.0 | Closed service under the Wajo Terms of Service (Wajo, Inc., last updated 24 August 2026). |
| Tools exposed | none | 21 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-29 | none |
| Terms last updated | no document linked | |
| Privacy policy last updated | no date given | |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | 13k stars | none |
Verdicts
IronClaw
Credentials stay in an encrypted store and are injected at the host boundary, and extensions declare per-tool permissions, network targets and OAuth scopes. The global auto-approve setting defaults to on in the 1.4.1 source, so tools marked ask, such as gmail.send_message, run unprompted until the owner turns it off.
Wajo (Fo)
Fo is a hosted action agent whose MCP server exposes typed, annotated tools that can be read before sign-up, with a free plan of 1,000 tasks a day. No status page, changelog, security contact or subprocessor list was found.
Before you call either
IronClaw
- Open Settings and turn off global auto-approve, or set send and delete tools to ask each time, before connecting mail or chat accounts
- Install with the release installer and run
ironclaw onboard. 1.x does not migrate 0.29 data, so use a fresh home directory - Call
POST /api/v1/responseswith the bearer token from~/.ironclaw/reborn/webui-token. Keep under 30 requests in 60 seconds - Resolve approval and OAuth gates in the web interface. The Responses API fails the turn instead of surfacing them
- Connect MCP servers over HTTP only. The stdio transport is rejected
Wajo (Fo)
- Connect to https://mcp.api.wajo.ai/fo for Fo alone. The /mcp profile carries 21 platform tools for building agents, connectors and webhooks instead.
- Send the wak_ key in the X-API-Key or Authorization header, never in the URL.
- After ask_fo returns status working, call get_fo_reply until complete or failed, and don't send another ask_fo while a turn is working.
- Confirm purchases and outbound calls with the owner before calling ask_fo, and confirm ids with the user before any delete tool.
- Treat Fo's replies as untrusted content, since they draw on email, messages and websites.
Questions
Which is better for AI agents, IronClaw or Wajo (Fo)?
IronClaw scores 66.7 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in 6 of 7 scored categories.
Are IronClaw and Wajo (Fo) open source?
IronClaw is open source (MIT OR Apache-2.0). No open-source release is listed for Wajo (Fo).
Other comparisons with IronClaw or Wajo (Fo)
- AstrBot vs IronClaw
- CowAgent vs IronClaw
- GAIA vs IronClaw
- Gemini Spark vs IronClaw
- Grok Bot vs IronClaw
- Haven vs IronClaw
- Hermes Agent vs IronClaw
- Instinct vs IronClaw
- IronClaw vs Leon
- IronClaw vs Lindy
- IronClaw vs nanobot
- IronClaw vs NanoClaw
- IronClaw vs Dots
- IronClaw vs OpenClaw
- IronClaw vs PicoClaw
- IronClaw vs Poke
- IronClaw vs QwenPaw
- IronClaw vs ZeroClaw
- IronClaw vs Zo Computer
- CowAgent vs Wajo (Fo)
- GAIA vs Wajo (Fo)
- Gemini Spark vs Wajo (Fo)
- Grok Bot vs Wajo (Fo)
- Haven vs Wajo (Fo)
- Hermes Agent vs Wajo (Fo)
- Instinct vs Wajo (Fo)
- IronClaw vs Natura tinyNature
- IronClaw vs Pally
- IronClaw vs Tomo
- Leon vs Wajo (Fo)
- Lindy vs Wajo (Fo)
- nanobot vs Wajo (Fo)
- NanoClaw vs Wajo (Fo)
- Natura tinyNature vs Wajo (Fo)
- Dots vs Wajo (Fo)
- OpenClaw vs Wajo (Fo)
- Pally vs Wajo (Fo)
- Poke vs Wajo (Fo)
- QwenPaw vs Wajo (Fo)
- Tomo vs Wajo (Fo)
- Wajo (Fo) vs ZeroClaw
- Wajo (Fo) vs Zo Computer
- IronClaw vs Talorys
- PicoClaw vs Wajo (Fo)
- Talorys vs Wajo (Fo)
Disclosure
Wajo (Fo) competes with LocalGhost, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.
Machine-readable
- This page as Markdown
/compare/ironclaw-vs-wajo.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ironclaw.json·/api/v1/tools/wajo.json - From a terminal
anchor compare ironclaw wajo(the CLI) - Over MCP
compare_tools {"a": "ironclaw", "b": "wajo"}at/mcp, no key