Get an audit

Head to head · Proactive personal assistants · October 2026 research run

Lindy vs Town

Town scores 48.7 (D) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments & pricing. Both do proactive personal assistants.

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

LindyCrivello Corp (doing business as Lindy) · Platform F32.3/100#974 of 1010 TownTown.com, Inc. · Platform D48.7/100#834 of 1010

Which one, for what

Lindy F

Best for Lindy suits a person or small team that lives in Slack and Google or Microsoft mail and wants briefs, drafts, scheduling and meeting notes done on a schedule.

Ahead on

  • Payments & pricing, 35 against 30

Watch for

The integrations page says approval settings apply in shared Slack threads only. Web chat, Slack direct messages, iMessage and SMS are not covered, and reads are never covered.

Town D

Best for An owner who wants a mail and calendar assistant whose routines other systems can trigger.

Ahead on

  • Reliability, 35 against 24
  • Agent ergonomics, 49 against 43
  • Security & auth, 79 against 49
  • Maintenance & community, 60 against 9
  • Transparency & trust, 63 against 52

Also in its favour

  • No incidents deducted, where Lindy loses 3 points for them

Watch for

The privacy policy describes training with an opt-out and the trust page says training is opt-in.

Score by category

CategoryWeight this runLindyTownEdge
Reliability16%202435Town +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.23233Town +1
Agent ergonomics13%16.24349Town +6
Security & auth14%17.54979Town +30
Payments & pricing10%12.53530Lindy +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.8960Town +51
Transparency & trust7%8.85263Town +11
Negative events≤15-30
TotalF 32.3/100D 48.7/100

Facts side by side

FactLindyTown
KindPlatformPlatform
VendorCrivello Corp (doing business as Lindy)Town.com, Inc.
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Lindy's Terms of Service. No source is publishedClosed service under Town's Terms of Service (Town.com, Inc., updated 21 July 2026).
Read-only variant documentednoyes
llms.txtyesno
Last release2025-10-212026-10-10
Terms last updated2026-09-24
Privacy policy last updated2026-09-28
Customer content may train modelsnot found in the text
Terms restrict automated accessyes
Terms restrict benchmarkingyes
Terms or service can change without noticeyes
Arbitration or class-action waiveryes

Verdicts

Lindy

Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025.

Town

Town is a hosted assistant that works across the owner's mail, calendar and work apps, and other systems can start its routines through per-routine webhooks with rotatable secrets, idempotency keys and documented errors. A caller can't read a run's result. The privacy policy and trust page disagree on whether training is on by default.

Before you call either

Lindy

  1. Treat a request sent by direct message, text or web chat as unguarded. Approval prompts appear in shared Slack threads only.
  2. Run a routine as a dry run before turning it on. A dry run reads real data and sends, posts and writes nothing.
  3. Turn off unused tools after adding an MCP server. Every supported tool arrives switched on, and a large server adds more than a hundred.
  4. Expect a billed seat for anyone who mentions Lindy in Slack. A teammate who joins that way has seven free days first.
  5. Connect only hosted MCP servers on public HTTPS with streamable HTTP, the one kind the docs describe.

Town

  1. Start a Town routine with POST to its webhook URL, Authorization Bearer whsec_ secret, and application/json or text/plain. Expect 202 only.
  2. Send X-Town-Idempotency-Key with a stable event id on every retry so Town doesn't start a second run.
  3. Treat 404 as wrong secret, disabled endpoint or missing endpoint alike, and ask the owner to check Routine Settings rather than retrying.
  4. Send account_email only if the owner allowed the override. It must match a connected account in full and can't widen the routine's scope.
  5. Ask the owner to keep routines that act on webhook input in approval-required mode, as Town's own docs advise.

Questions

Which is better for AI agents, Lindy or Town?

Town scores 48.7 (D) on agent readiness against Lindy's 32.3 (F), and leads in 6 of 7 scored categories. Lindy leads on payments & pricing.

Other comparisons with Lindy or Town

Disclosure

Town 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