Soar

# Fix list: Soar

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/soar-travel, the October 2026 research run, assessed 21 October 2026. Grade F, 12.6 out of 100.

This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.

For a coding agent working on Soar: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.

## 1. Reliability, 5 out of 100, up to 19 more on the total

Why it scored 5: Read with the hosted lines. No status page found (0). No readable incident history (5). No rate limits published (0). No overload or retry guidance (0). No SLA (0). The FAQ calls this a beta period (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):

Hosted APIs, MCP servers, models and platforms.

- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).
- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.
- 15, rate limits documented with numbers.
- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.
- 10, an SLA published for any paid tier.
- 10, the surface agents use is generally available, not beta or preview.

Local packages, SDKs, frameworks and stdio MCP servers.

- 20, installs from an official package with supported runtimes stated.
- 25, a public CI and test suite, passing on the default branch.
- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).
- 15, semver discipline and breaking changes called out in a changelog.
- 15, version 1.0 or later, or declared stable.

Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.

## 2. Security & auth, 3 out of 100, up to 17 more on the total

Why it scored 3: Graded on the interface an outside agent can use. With no public interface, the credential, least-privilege, injection and audit lines score nothing. For reviewers, Gmail access is read-only and revocable, and Soar never sends email as the owner. Security programme. The Gmail safety page says Soar passed Google's verification and an independent CASA assessment for the restricted scope, a claim. No security.txt (404), disclosure policy or bounty found, read as for the Zapia listing (3 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-security):

- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.
- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.
- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.
- 0 to 15, audit logs or per-call visibility for the operator.
- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.

Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.

## 3. Schema & documentation, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use. Soar MCP is by private access, with keys set up by the team after a request, so there's no public contract, tool list or documentation to read (0 of 25, 0 of 20, 0 of 15, 0 of 15, 0 of 15). joinsoar.co/llms.txt returns 404 (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):

APIs and MCP servers.

- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).
- 10, llms.txt or Markdown docs served for agents.
- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.
- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.
- 0 to 15, examples and documented error responses.
- 15, versioning and a public changelog.

Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.

## 4. Agent ergonomics, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use. With no public interface, context cost, pagination, errors, retries and defaults score nothing (0 on each line).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):

- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).
- 20, pagination, filtering and output-size controls.
- 20, actionable, documented error responses, codes and messages an agent can recover from.
- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.
- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.

Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.

## 5. Payments & pricing, 20 out of 100, up to 10 more on the total

Why it scored 20: Read with the hosted rule. No x402, MPP or L402 (0). The app is free and no paid plan is published, so the public price is the free plan (10). Free with no card, but the FAQ says free during the beta with paid plans to follow, so the hedged 10 (10). A person installs the app or texts in (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):

The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).

- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.
- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login.
- 20, a free tier or trial that doesn't need a card.
- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).

Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.

Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.

## 6. Transparency & trust, 44 out of 100, up to 4.9 more on the total

Made of editorial 40, provenance 47.

Why it scored 44: Closed service. The terms of 22 May 2025 don't name the company and describe an older product, saying Soar doesn't sell travel or act as a booking agency, while the site books flights and hotels. The entity appears only on the which-soar page and the App Store (8 of 30). The privacy policy of 13 September 2026 gives deletion within 3 months for inbox data, says nothing is sold or used for ads, and names the hotel booking flow. The terms say reading only, which still agrees (20 of 30). No deprecation policy; the privacy policy promises notice of material changes (2 of 20). Google Cloud, Nuitee (LiteAPI) and Stripe are named, and data stays in the US (12 of 20).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):

- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.
- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).
- 0 to 20, a deprecation policy or notices with dates.
- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).

The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.

Provenance checks not met in full (half of this category, computed from checked facts):

- Domain age: joinsoar.co, no registry record we could read (0 of 15)
- Status page: not found (0 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 7. Maintenance & community, 54 out of 100, up to 4 more on the total

Why it scored 54: Read for a closed service. App Store version 1.0.14 on 6 October 2026 (30). Eight versions from 1.0.7 on 23 July to 1.0.14 on 6 October (20). No public changelog. App Store notes say what changed in July and August and repeat one line since, and a support inbox is published (4 of 15). No SDK or public MCP (0). No package to judge (0).

The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):

- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.
- 20, at least three releases or dated changelog entries in the last 90 days.
- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.
- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).
- 10, package health, current dependencies and CI.

Models are read for deprecation notice periods and model churn rather than release counts.

## What we couldn't check

What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.

- What Soar MCP's tools, auth and terms are, and when it opens beyond select partners.
- Whether flight bookings are ticketed by Soar or a partner. The privacy policy covers only hotel bookings.
- The domain's registration date (rdap.org returned no events for .co).

## Weaknesses

- Soar MCP is private, with keys set up by hand after a request.
- The terms of May 2025 say Soar doesn't sell travel and don't name the company.
- No status page, changelog or security contact found.
- US only and iPhone only.

## What costs an agent a turn today

The notes we give agents before they call it. Each one is a workaround an agent shouldn't need.

- Don't plan to call Soar from another agent. Its MCP server needs private onboarding by the team.
- Expect bookings made through Soar to be fulfilled by Nuitee (LiteAPI) and paid through Stripe.

## What the review panel asked for

- self-serve MCP keys
- a published tool list
- publish post-beta prices
- public MCP pricing
- public Soar MCP tool list
- terms that match the product
- publish Soar MCP's auth and scopes

## When it's done

Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.