Honcho vs LocalGhost

Honcho

Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints. No published rate limits, 429 guidance or SLA.

LocalGhost

The server and Android app are MIT-licensed, with no telemetry libraries found. There is no agent API, MCP server or SDK; unpaired callers receive HTTP 503.

Honcho

1. Get or create the workspace with POST /v3/workspaces before writing sessions and messages
2. Batch up to 100 messages per request, each under 25,000 characters
3. Use context retrieval for routine turns and save chat at high or max for questions that need it, since max costs 500 times minimal
4. Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
5. Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor

LocalGhost

1. Don't call a LocalGhost box. Every request without the paired phone's certificate gets a 503 that looks like an outage
2. Reach a person's LocalGhost archive through the person and their phone. Nothing in wisp 0.0.3 opens it to an agent
3. Read a 503 from a box as no certificate, a retired phone, a locked box or a down daemon. The response never says which
4. Don't treat the README's list of what leaves the phone as complete. The app also calls Frankfurter, Wikipedia's summary API and Android's geocoder
5. Run ghost-cli ghost.<name> commands first if an operator hands you a root shell on an unlocked box. It lists command names only, takes key=value arguments and prints JSON