Get an audit

Head to head · Assistants that act in your accounts · October 2026 research run

nanobot vs Wajo (Fo)

nanobot scores 62.4 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in every scored category. Both do assistants that act in your accounts.

Best AI personal assistants that act for one person · All 834 assistants comparisons

nanobotHKUDS · Agent harness B62.4/100#446 of 1010 Wajo (Fo)Wajo, Inc. · Platform E43.9/100#909 of 1010

Which one, for what

nanobot B

Best for A technical owner who wants an assistant on their own machine across many chat apps, with file-based memory and a free choice of model.

Ahead on

  • Reliability, 70 against 30
  • Agent ergonomics, 74 against 68
  • Security & auth, 63 against 38
  • Payments & pricing, 60 against 30
  • Maintenance & community, 82 against 3

Also in its favour

  • No key needed to call it
  • Open source

Watch for

No per-action approval was found in the docs or source. The agent sends messages, runs shell commands and edits files without asking

Wajo (Fo) E

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
  • No incidents deducted, where nanobot loses 6 points for them

Watch for

No status page, changelog or security contact found.

Score by category

CategoryWeight this runnanobotWajo (Fo)Edge
Reliability16%207030nanobot +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27774nanobot +3
Agent ergonomics13%16.27468nanobot +6
Security & auth14%17.56338nanobot +25
Payments & pricing10%12.56030nanobot +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8823nanobot +79
Transparency & trust7%8.84847nanobot +1
Negative events≤15-60
TotalB 62.4/100E 43.9/100

Facts side by side

FactnanobotWajo (Fo)
KindAgent harnessPlatform
VendorHKUDSWajo, Inc.
Hosted endpointno (local only)https://mcp.api.wajo.ai/mcp
TransportsStreamable HTTP
AuthNoneOAuth or key
PricingFreeFreemium
x402nono
LicenceMITClosed service under the Wajo Terms of Service (Wajo, Inc., last updated 24 August 2026).
Tools exposednone21
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-15none
Terms last updatedno document linked
Privacy policy last updatedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Popularity49k starsnone

Verdicts

nanobot

nanobot runs on the owner's machine under the MIT licence, with no telemetry found in its source and memory kept as files the owner can read and restore. No per-action approval step was found, and the shell sandbox and workspace restriction are off by default. Five security advisories were published between March and September 2026, all with fixes.

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

nanobot

  1. Set tools.restrictToWorkspace to true and tools.exec.sandbox to bwrap or seatbelt before giving it real accounts. Both are off by default
  2. Run 0.3.0 or later. Earlier versions carry the published SSRF flaw in web fetch (GHSA-vc5v-6vwm-wf9m)
  3. Keep allowFrom narrow on every channel and never set ["*"] on Email, which has no pairing
  4. Write secrets as ${VAR} references in ~/.nanobot/config.json. Plain values are stored in clear text
  5. Use nanobot -m "..." for a one-shot run, and keep nanobot gateway running for channels, schedules and heartbeat

Wajo (Fo)

  1. 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.
  2. Send the wak_ key in the X-API-Key or Authorization header, never in the URL.
  3. 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.
  4. Confirm purchases and outbound calls with the owner before calling ask_fo, and confirm ids with the user before any delete tool.
  5. Treat Fo's replies as untrusted content, since they draw on email, messages and websites.

Questions

Which is better for AI agents, nanobot or Wajo (Fo)?

nanobot scores 62.4 (B) on agent readiness against Wajo (Fo)'s 43.9 (E), and leads in every scored category.

Are nanobot and Wajo (Fo) open source?

nanobot is open source (MIT). No open-source release is listed for Wajo (Fo).

Other comparisons with nanobot or 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

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report