# Amp vs Paseo (slim)

> Paseo scores 62.1 (B) to Amp's 55.5 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amp-vs-paseo.md (~5,000 tokens) · this version ~1,730 tokens · JSON https://www.anchorterminal.com/compare/amp-vs-paseo.json · canonical https://www.anchorterminal.com/compare/amp-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Paseo scores 62.1 (B) on agent readiness against Amp's 55.5 (C), and leads in 4 of 7 scored categories. Amp leads on schema & documentation and transparency & trust. Both do agent harnesses.

- Amp: C 55.5, rank #868 of 1510 · https://www.anchorterminal.com/tools/amp.min.md
- Paseo: B 62.1, rank #577 of 1510 · https://www.anchorterminal.com/tools/paseo.min.md
- Amp, good for Teams that want a hosted, multi-model coding agent with shared threads and cloud machines, driven from scripts through execute mode or the SDKs. Ahead on Schema & documentation, 72 against 65; Transparency & trust, 77 against 68.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Reliability, 50 against 23; Payments & pricing, 60 against 35. Also No key needed to call it; Open source.

| Category | Amp | Paseo |
| --- | --- | --- |
| Reliability (16%) | 23 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 72 | 65 |
| Agent ergonomics (13%) | 69 | 70 |
| Security & auth (14%) | 57 | 58 |
| Payments & pricing (10%) | 35 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 75 |
| Transparency & trust (7%) | 77 | 68 |

| Fact (where they differ) | Amp | Paseo |
| --- | --- | --- |
| Vendor | Amp Frontier Corporation | Mohamed Boudra |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| Licence | Proprietary, under the Amp licence terms (Amp Frontier Corporation). The npm packages are marked Amp Commercial License and the source repository is private | Apache-2.0 |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-11-07 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | 2026-09-10 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 41k npm/wk | none |

Why the edge:
- Reliability, Paseo +27: Amp 23 (Local-package reading, as for the other closed-source harnesses. An install script that verifies a SHA-256 checksum, and an `@ampcode/cli` npm package of prebuilt binaries, for macOS, Linux and Windows through WSL, per the 8 October check (20). The source repository is private, so there is no public CI or test suite (0). There is no public issue tracker, and bug reports go to the vendor from inside the product. The 8 October reading of the status page's incident feed is struck, because ampcodestatus.com's robots.txt now disallows ClaudeBot, Claude-Web and anthropic-ai, so nothing is left to count crash or regression reports against (0). Versions are build stamps such as 0.0.1792627309-g98c009 with no per-version notes, and the introduction says "No backward compatibility", though removals are announced with dates in the Chronicle (3). The version line is 0.0 and we found no statement that the CLI is stable (0).); Paseo 50 (Local software. Desktop builds, an Android APK, a Docker image and a Nix package (20). ci.yml on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). CHANGELOG.md (15). Version 0.15.3 (0). 20 + 15 + 0 + 15 + 0 = 50.)
- Payments & pricing, Paseo +25: Amp 35 (Harness reading of the published rubric. No payment protocol (0). The pricing page is public. Hobby is free, Megawatt is $20 a month with 45,000 orb minutes, orbs are priced per hour by size from $0.08, and paid credits are charged at provider API prices with no markup outside Enterprise. Gigawatt is $200 a month with $200 of agent usage and 1,000 hours of a1.xxlarge orbs, per the pricing docs (20). Hobby is free when you bring your own model key or subscription and run locally or on your own runner. The pricing page does not say whether sign-up asks for a card, and inference served by Amp is never free (15). A person signs in through a browser to create the access token (0).); Paseo 60 (Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.)
- Transparency & trust, Amp +9: Amp 77 (Closed source under the Amp licence terms from Amp Frontier Corporation, with the npm packages marked Amp Commercial License. The terms page shows no date (15). The security reference lists 19 providers and what each sees, says deleted threads are removed within 30 days, diagnostic data after 7 days and audit logs kept at least 30 days, and the privacy policy (modified 10 September 2026) agrees, with account data kept while the account is active (24). No deprecation policy. The terms allow any part of the Services to be discontinued without notice, while removals so far were announced with dates, such as the old npm package names on 14 May 2026 for removal on 15 June (8). Amp is local software tied to a hosted service. Providers and US hosting are disclosed in detail, but the usage data the client sends is not itemised and has no documented opt-out (12).); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)
- Schema & documentation, Amp +7: Amp 72 (Framework reading. A JSON Schema for the settings file at ampcode.com/cli-settings.schema.json (22 properties), TypeScript types for every stream message, and a generated reference for the plugin API, but no OpenAPI for the server (18). ampcode.com/llms.txt indexes a raw Markdown rendition of each of 55 docs pages (10). The docs say when to use execute mode, orbs, runners, the oracle and the Librarian, and what each mode is for (15). Settings carry types and defaults, and the stream schema enumerates stop reasons, result subtypes and MCP server states (12). Examples on nearly every page and two result error subtypes (`error_during_execution`, `error_max_turns`), with no exit codes or error catalogue (9). Dated Chronicle posts with an RSS feed and a lastModified date on each docs page, but no changelog by CLI version (8).); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)