Reviews

Pros

• Free tier has a kill switch and spend caps
• Modelled savings are never billed
• No seat, per-agent or setup fees

Cons

• Terms leave prices, taxes and refunds as TBD
• Fee depends on savings Navige measures itself
• No rate-limit numbers published
• Sign-up needs a person, and the Terms forbid account creation by automation

Pros

• The 3.0.0 README names the methods that now throw
• Health and readiness endpoints answered when checked on 17 October

Cons

• 2.x SDK broken by a backend rebuild with no notice found
• Status page monitors a retired host
• No changelog or deprecation policy
• DPA revised three times since 6 October 2026

Pros

• No account, key or hosted data path
• Tool results rendered in their own tool role
• The template rejects unknown options with named errors

Cons

• Remote code runs on the host in every documented launch command
• String tool results go in raw, with no special-token escaping found
• No security contact, security.txt or safety evaluation
• The template inserts an identity system prompt when none is sent

Pros

• Template rejects bad options with named errors
• Cards state intended use, out-of-scope uses and limitations
• Python examples for a reasoning call and a tool loop

Cons

• A missing or null thinking field on a prior turn makes the template raise an error
• No error reference for a served model, and structured output undocumented
• 375B card disagrees with the template on medium effort

Pros

• Nothing to buy, no card and no sign-up
• Smallest model is 2.2 GB and runs on one H100
• FP8, GGUF and MLX builds shrink the footprint, such as 25.5 GB for 32B 4-bit

Cons

• No hosted provider found, so no per-call price to compare
• Output tokens dominate at the recommended settings
• No throughput figure for GPU deployments was found
• 375B-A23B needs 16 H100 or 8 H200

Pros

• Public commit history on Hugging Face
• vLLM and SGLang recipes merged upstream
• FP8, GGUF and MLX builds from the makers

Cons

• Template behaviour changed without a changelog
• No version tags or deprecation policy
• llama.cpp support on master only
• No CI or test suite found

Pros

• Keys revocable at once through the API and holdable to one workspace
• Per-turn caps on steps, time and spend
• UHP puts prompt injection in scope and secrets are redacted from streams and traces

Cons

• No approval step for harness actions
• disabled_tools is only a prompt instruction on some bases
• Cross-workspace and internal-route flaws fixed in October 2026
• No security.txt, SOC 2 or ISO 27001 found

Pros

• Idempotency-Key on every task call, with a recovery rule for dropped streams
• Closed error codes with a retry rule per code
• Per-turn budgets of 400 steps, 7,200 seconds and $10 by default

Cons

• No status page found, so no incident record
• No request rate limit published, only concurrency and task length
• No SLA outside a signed order form

Pros

• A 422 example names every failed field without echoing the body
• llms.txt, a 230 KB llms-full.txt and Markdown copies of the quick start, pricing and harness catalogue
• 26 enums and 134 required lists in the schema, and docs that say what to send and what not to

Cons

• Seven same-day patches changed the 2026-10-04 schema while the schema page calls a published version immutable
• The conformance page says 76 checks, the YC post 95 and the suite source 98
• Docs pages are short, and the OpenAPI file holds only 14 examples
• No official SDK, only the OpenAI Responses shape and generated clients

Pros

• Four dated protocol versions since 11 August
• Discovery document lists the supported versions
• Idempotency-Key and Retry-After make task retries safe

Cons

• Spec version 2026-10-04 changed seven times without a new date
• Hosted API defaults to 2026-09-28 while the spec is at 2026-10-04
• No status page or product changelog
• Several tags a day, with open issues unchecked

Pros

• Agent-start switch that an agent can't turn on
• At most four live harnesses per agent, closes limited to its own
• Remote traffic end-to-end encrypted

Cons

• Writes allow rules into Claude Code and Codex settings
• Codex runs Harness commands outside its sandbox
• The daemon updates itself without asking
• No per-call audit log, security.txt or bug bounty

Pros

• Short instructions that say when not to start a harness
• Exit codes 0 to 5 and 124 documented, with a Next: line after each answer
• Annotations on reads, starts, sends and closes

Cons

• machine, folder and project are free strings
• No pagination on lists
• README names an unpublished npm package

Pros

• Semver tags per component
• CI suites for the CLI, desktop, backend and OS
• Provider protocol has a dated changelog

Cons

• No changelog for the app or CLI
• Self-updating daemon amid several hundred tags
• Named npm MCP package never published
• No status page for accounts and relay

Pros

• Local use on one computer needs no account and no card
• The software is free under MIT
• Agents use the person's existing Claude Code or Codex credentials
• harness whoami tells an agent whether it may start harnesses

Cons

• Agents starting harnesses need a signed-in person and an off-by-default experimental switch
• The CLI agents call is version 0.4.18, and the npm MCP package in the repository was never published
• Installing Harness adds its commands to Claude Code's and Codex's permission rules
• Autonomous's terms forbid accessing its services by automated means, and whether they apply to Harness was not established

Pros

• Send-only and read-only presets for keys and MCP connections
• Send keys limited to named domains
• One-hour OAuth tokens with refresh-token reuse detection
• Connected agents listed with scopes and revocable

Cons

• An OAuth request without a scope receives full access
• No server-side confirmation before a send
• Inbound mail bodies returned with no injection guidance
• No security.txt, disclosure policy or certification

Pros

• Plan prices and volume tiers published without a login
• Inbound mail isn't billed as a send
• Sandbox sends work without a card, to the account email only

Cons

• Card on file needed to send to others, even on Free
• MCP send_email has no idempotency key, so a retried call can send twice
• Whether refused sends count against quota wasn't found
• Launched 16 October 2026, with no billing history to read

Pros

• Registered under the GitHub-verified io.github.Groundmail namespace
• Current MCP SDK dependency
• Sending quotas exposed in ratelimit headers

Cons

• No changelog across 15 versions in two days
• No status page or incident history
• README lists tools the package lacks
• Public repositories are mirrors with no CI

Pros

• Sandbox send to the account email needs no card or DNS
• Free covers 3,000 emails a month and 100 a day
• Keys can be Send only, with allowed_domains limits
• The new-account ramp-up from 500 to 50,000 a day is published

Cons

• A card on file is needed to send to anyone but the account owner
• Domain verification needs DNS records a person must publish
• An OAuth request that names no scope gets full
• No x402, MPP or L402, and billing is through Stripe

Pros

• No write actions
• No account, key or gate to leak
• IBM security.txt valid, with PSIRT and HackerOne
• Decision adapters in Granite Libraries signed with certificates

Cons

• The vLLM server has no authentication unless the operator adds it
• The composed 4.1 checkpoints have no signature file
• No guidance on hostile text steering a decision
• The card warns a mistranscription can silently change an adapter's answer

Pros

• Cards say what each adapter does and where a decision is only a prior
• Python and curl examples for both adapters and audio
• 128-id limit and audio prompt-length error documented

Cons

• No typed decision request and no Mellea decision call yet
• Card and pyproject.toml disagree on Python and vLLM versions
• No llms.txt or specification file

Pros

• Free under Apache 2.0 with no account or card
• Weights are not gated
• A decision is one prefill and one output token
• Options beyond 128 add one request per 128

Cons

• No hosted endpoint, so the owner pays for GPUs
• Hardware sizing is unchecked
• The card and package disagree on supported Python and vLLM versions
• No payment protocol

Pros

• Keep a Changelog format with semver declared
• Pull requests from more than ten authors merged within days
• CI runs CPU unit tests on every push

Cons

• 8B preview replaced in place under the same name
• No tags and no changelog entry for 0.1.1
• Card says vLLM below 0.28, pyproject.toml below 0.31
• Composer API declared not yet stable

Pros

• No browser client secret, so the key never reaches a browser
• Per-permission keys such as api.decisions.write
• Guardrail guidance covers transcript checks and blocking actions until checks pass

Cons

• WebRTC data channel allows every event unless an allowlist is set
• Responses delegation can run hosted shell, computer use and local shell
• No guidance on injected content in hosted tool results
• No public endpoint to delete a stored session recording

Pros

• Concurrent session limits stated per tier
• 429 and 503 on session creation, with Retry-After guidance
• Sideband replays 3 seconds with original event IDs, and stored sessions can be forked after a drop

Cons

• Status component has data only from 16 October 2026, five weeks after general availability
• No idempotency key on session creation, and a retried outbound call can place a second call
• No SLA found, and whether failed creations are billed is unchecked

Pros

• Guides say when to choose WebRTC, WebSocket or SIP, and when to delegate to Responses, the client or Decisions
• Errors carry code, param and the client_event_id of the failed command
• Python and JavaScript examples on every guide, with llms.txt and a Markdown twin of each page

Cons

• No full catalogue of Live error codes was found
• Three JavaScript examples in the Markdown twins are empty
• Several voice guides hold GPT-Live and Realtime text on one page under an api switch, which a model can confuse
• Not an AsyncAPI document, so the WebSocket channels appear only as event schemas

Pros

• $0.05 a minute, billed per second with no rounding up
• Price published on the model and pricing pages without a login
• The vendor's example prices a 90-second session with $0.02 of backend work at $0.095
• Concurrent session limits published, 50 on Build, 300 on Launch, 500 on Grow

Cons

• Silence and backend waiting time are billed
• Backend models and tools are billed separately
• The Free usage tier is not supported
• No statement on whether failed session creations are billed

Pros

• Per-key credit limits on OpenRouter
• Together's endpoint shown as no training and no prompt retention
• OpenRouter's security.txt valid at its last check

Cons

• No key scopes on either route
• Elorian's terms licence submitted content for training
• Whether Elorian receives OpenRouter prompts is unchecked
• No Elorian security.txt, bug bounty or certification

Pros

• Retry-After documented by OpenRouter on 429 and 503
• Per-key credit limits and a key endpoint reporting what is left

Cons

• Single provider on a dedicated Together deployment, so a 503 has no fallback
• No rate limit published for this model
• Research preview with no SLA, changelog or deprecation policy

Pros

• OpenRouter documents video input, Retry-After and error codes in Markdown
• Launch post names the jobs and states token cost and the lack of action outputs
• Standard OpenAI-compatible request shape

Cons

• No Glimpse-specific examples or limits on video length or image count
• native_tools is empty, so the tools the post describes are not exposed
• Structured output enforcement depends on Together and is undocumented by Elorian

Pros

• Input, cached and output rates published without a login
• Cached input is a tenth of the uncached rate
• Rates on OpenRouter match Elorian's published rates

Cons

• A single call can emit up to 256,000 output tokens, about $0.77 at the output rate
• No free variant on OpenRouter
• Elorian's terms allow training on free use by default
• Volume access runs through sales

Pros

• Empty environment plus nine named variables, so supervisor keys are not inherited
• Default deny list for common secret paths
• File changes wait for commit or abort

Cons

• Default network mode allows every destination
• read-write profile and pi-deltabox default bypass isolation
• Install prompt asks the agent to act on the user's GitHub account
• No SECURITY.md, security.txt or disclosure policy

Pros

• Closed enums for fs_mode, durability, execution_profile and review kind, and TypeScript declarations for the Node binding
• The README shows the right and wrong forms of shell redirection
• exec returns stdout, stderr, the exit code, the duration and a truncated flag

Cons

• One error code covers 15 typed error variants
• install-prompt.txt step 5 asks the agent to star the repository, which is not part of installing
• No JSON Schema or llms.txt, and the docs are four Markdown files
• docs/protocol.md names an MCP server among the adapters, but none was found in the repository or on npm

Pros

• Keep a Changelog with dated entries and semver
• Cargo.lock and a pinned Rust 1.87 toolchain
• Checksummed packages on npm, Homebrew and releases

Cons

• Test suite not run in CI
• Old Homebrew tap still named after the repository move
• No Dependabot configuration or npm provenance
• Issue history unchecked

Pros

• No account, key or card at any step
• One command runs a task and commits or aborts its file changes
• Diff, commit and abort give a cleanup step for every session

Cons

• Step 5 of install-prompt.txt has the agent star the repository through the user's authenticated GitHub CLI
• An unquoted > is handled by the host shell and writes outside the sandbox
• Linux needs glibc 2.39 and FUSE for the default mode, or falls back to copy-private

Pros

• Both endpoints read-only
• Fetch rejects URLs that carry credentials
• The key travels in a header, not a URL

Cons

• One unscoped key covers search and model spend
• No prompt-injection guidance for returned page text
• No audit log, security.txt or bug bounty found
• Inputs used for training unless the customer opts out by email

Pros

• Snippet, model-length summary and optional full text on every result
• Rerank score and authority tier with documented thresholds for quality and authority
• Fetch returns a single page as Markdown with its title
• Failed calls and empty results are not billed, so a retry costs nothing

Cons

• Site, language and date filters are operators inside a query capped at 128 characters
• The privacy policy of 10 February 2026 says search uses third-party APIs, against the in-house engine in the change log
• No OpenAPI file or llms.txt
• Index size and daily volume are DeepSeek's figures, not ours

Pros

• Typed fields with limits and defaults on both endpoints
• Error table with ten codes and retry guidance
• Guide says which result field suits a model and gives thresholds for quality and authority

Cons

• No OpenAPI file, llms.txt or Markdown twin
• Filters live in a 128-character query string, not typed fields
• Reference shows only the 200 response

Pros

• Same price at 1 or 50 results
• Only successful non-empty calls are billed
• Price published without a login on the guide and pricing page

Cons

• No free tier for direct calls
• One key can spend search and model balance, with no scopes
• Console top-up details weren't read
• Fetch has a per-domain limit with no published number

Pros

• Delegated Entra scopes requested per step
• Tokens held only in memory
• Connector writes need a plan ID and confirm: true
• Requests pinned to the expected Power Platform hosts

Cons

• No read-only mode
• No confirmation found for workflow tests that run live workflows
• The borrowed VS Code client can't be restricted as a dedicated app
• Service tool schemas and annotations unchecked behind sign-in

Pros

• Local inputs are tightly typed with required fields
• Descriptions say when to call and when not to
• Errors say whether a write may have completed and whether to retry

Cons

• Service tools are dispatchers whose contract is read at run time
• About 16,000 characters of definitions and instructions before any work
• No changelog or error catalogue

Pros

• Listed in the official MCP registry as com.microsoft/copilot-studio
• Bundle pins current dependencies
• Semver numbering

Cons

• No release notes for either version
• Repository holds no source or tags
• No support channel named
• Service tool schemas readable only after sign-in

Pros

• Install is one npx -y @microsoft/copilot-studio-mcp@latest line with no client ID or tenant to set
• Delegated scopes are requested per step
• Tokens are held only in memory
• Listed in the official MCP registry under the com.microsoft namespace

Cons

• Each restart needs a new browser sign-in
• Personal Microsoft accounts are refused
• Client ID and tenant overrides are not supported
• The five service tools' schemas load only after sign-in and were not read

Pros

• Confirmation on every DELETE, with exit 1 when --force is missing in a non-interactive run
• Global API Key refused, and no flag takes a token
• --dry-run prints each request before it is sent

Cons

• No read-only mode
• OAuth credentials stored as plain JSONC, keyring support is future work
• --force doubles as an API parameter on some commands
• No guidance on untrusted content in API data or docs search results

Pros

• cf cli search returns at most five matches, and cf schema and --dry-run need no credentials
• A hidden cf tools prints MCP tool definitions with JSON Schema inputs for every command
• The agents page says when to use cf, when to keep Wrangler and which search to use for what

Cons

• The README and launch post say JSON is condensed for agents, but the source indents it with two spaces
• List output strips result_info, so an agent can't tell whether more pages exist
• The agents and CI docs lag the source on the exit status of an aborted delete
• Body field lists are incomplete or empty for some generated commands

Pros

• Changelog marks breaking changes, such as the beta.16 renames
• Wrangler promised 18 months of maintenance after the beta ends
• Releases published from GitHub Actions with provenance

Cons

• 42 generated commands renamed in one prerelease
• Agents and CI docs still give exit status 0 for an aborted delete
• Outside pull requests closed during the beta unless coordinated
• Issue tracker and CI run results unchecked

Pros

• Request planning works before sign-in
• CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID cover unattended runs
• --scopes limits what an OAuth grant can do
• The Global API Key is refused

Cons

• Account access needs a person to sign up and approve OAuth or create a token
• cf auth login needs a browser approval
• Telemetry on by default sends the text of search queries
• Beta at 1.0.0-beta.18 with breaking renames between prereleases

Pros

• Tokens take Read, Run or Edit levels with expiry and IP filters
• Public endpoints are switched on per path
• Docs include a human-approval pattern for agent writes

Cons

• Public endpoints, including MCP, answer anyone with the URL by default
• Default hostname stays open after Access is set unless disabled
• Permission is per account, and the search guide asks for Edit and Run
• No prompt-injection guidance for retrieved chunks

Pros

• Hybrid vector and BM25 search on by default, with metadata filters applied before retrieval
• Each result chunk carries a key, a score and scoring details
• Sync intervals, the 30-second manual sync limit and the 31-day pause are documented
• llms.txt and a Markdown copy of every docs page

Cons

• At most 50 results a query, with no pagination
• The MCP tool's default description is a generic six-word line that names no content
• The MCP tool's input schema and annotations were not checked, since no public instance was found

Pros

• Error catalogue lists each code with its HTTP status, meaning and recommended action
• Docs say when to use search and when chat completions, and when vector, keyword or hybrid search fits
• Bounds on max_num_results, match_threshold and context_expansion, with required fields marked

Cons

• filters is a free object in the OpenAPI
• OpenAPI descriptions are one line
• The MCP tool's input schema and annotations are unchecked, since no public instance was found
• The OpenAPI still tags operations beta after the general availability notice of 1 October 2026

Pros

• Unit prices for ingestion, storage and both query types are public without a login
• Free allowances are set per month for every account
• Full-text queries are $0.10 per 1,000
• Limits are published with numbers, including 120 requests a minute on public endpoints

Cons

• Billing has not started, so the rates are unexercised until 1 November 2026
• Generation and query rewriting bill separately through Workers AI or AI Gateway
• Whether failed queries count against the quota wasn't found
• Whether signup on the Workers Free plan asks for a card is unchecked

Pros

• 18 permissions with widget and channel scoping
• Argument-bound confirmation tokens on five tools
• Per-connection audit log kept after disconnect
• Only owners and admins can connect

Cons

• send-message reaches the customer with no confirmation
• Untrusted-data guidance missing from the developer docs
• No security.txt, bug bounty or certification
• Served tool definitions unchecked behind OAuth

Pros

• Request limit stated and counted per connection
• Confirmation tokens bound to exact arguments for 300 seconds
• Batch calls take up to 100 conversation IDs

Cons

• No status page, and status.chatway.app doesn't resolve
• No Retry-After figure on 429
• No SLA, and a repeated send-message call does the work twice

Pros

• Typed parameter table, return shape and errors for each tool
• Troubleshooting table maps 401, 403, 405 and 429 to fixes
• Four common workflows documented

Cons

• tools/list needs OAuth, so descriptions and annotations are unchecked
• No tool examples and no server changelog
• MCP overview and OpenAPI description disagree on REST operations

Pros

• MCP is on every plan, including Free with no card
• OAuth 2.1 with PKCE and dynamic client registration, so no key is pasted
• Each connection is limited to chosen widgets, channels and 18 permissions
• Only tools for granted permissions are published, so a connection can be read-only

Cons

• Only an owner or admin can authorise a connection
• The tool definitions are served after OAuth and were not read
• No tool is idempotent, and a repeated call does the work twice
• No x402, MPP or L402

Pros

• Keys scoped per action and sending domain, with IP allow lists and sandbox mode
• Campaign send and schedule need an elicited confirmation
• Received mail hidden by default and marked untrusted when allowed
• No MCP tools for keys, billing or team members

Cons

• delete_domain and other deletes rely on the client's approval
• No security.txt or bug bounty, and ISO 27001 not yet certified
• Contact fields and bounce reasons still reach the model
• Live MCP tool list unchecked, read from the v0.1.1 source

Pros

• Per-component status history for 90 days
• 99.9% uptime SLA with service credits
• Idempotency-Key with written rules for retrying a send

Cons

• No status component for the MCP server, launched 14 October
• Error bodies carry no stable error codes except for campaign issues
• October 2026 shipped a breaking API v2 change despite a no-breaking-changes promise

Pros

• Descriptions say when to use a tool and what to use instead
• Typed inputs and outputs on every MCP tool, plus an OpenAPI 3.1 spec of 101 operations
• Hosted server lists only the tools the connection's scopes allow

Cons

• Limits not expressed as schema constraints
• No stable error codes outside campaign checks
• llms.txt contradicts the facts page on port 465

Pros

• Free plan with no card and no expiry
• Sandbox sends use no credits
• Terms credit 5% of the monthly fee per 30 minutes below the 99.9% uptime commitment
• Overage tiers published without a login

Cons

• Whether rejected sends count against the allowance wasn't found
• Token cost of the 82 MCP tool definitions is unchecked, since the live tool list needs sign-in
• Hourly sending limits start low for new accounts
• No x402, and sign-up needs a browser

Pros

• Read-only tool, with no search key in the agent's hands
• OAuth JWT or IAM SigV4 scoped to one gateway ARN
• Owner-set domain include and exclude lists the agent cannot relax

Cons

• No prompt-injection guidance on the Web Search pages
• A no-authorisation gateway mode exists, which AWS warns against for production
• No retention period for queries found

Pros

• Every result carries snippet text, URL, title and published date
• Owner-set domain include and exclude lists of up to 100 domains that the agent cannot relax
• The full input JSON Schema is published, with only query required

Cons

• The default connector 1.1.0 lacks request-level domain and date filters
• At most 25 results, with no pagination, country or language targeting and no full page text
• No error responses for the tool are documented
• Index size and freshness are AWS's claims, and tools/list output was not read

Pros

• One tool with three inputs, query, maxResults and filters, of which only query is required
• Each result comes as a JSON string in a text block and again as structuredContent
• An llms.txt of 993 lines and Markdown for every page, with connector versions that follow semver

Cons

• No error responses for the tool are documented, and the only response example has isError false
• The default connector 1.1.0 exposes only query and maxResults, so request-level filters need a target pinned to 1.2.0
• The response to the service's own Web Search quota is not documented
• The June release note links to a page that now redirects to the guide's front page

Pros

• Per-query price published without a login
• AWS's worked example shows the Gateway charge added to the query charge
• No minimum
• New AWS accounts get up to $200 in Free Tier credits

Cons

• No Web Search allowance
• Whether failed, empty or throttled searches are billed wasn't found
• Setup needs an AWS account, a Gateway, a target and IAM, with no machine payment route
• Credit eligibility for payment-method-free signup is AWS's general statement, not specific to Web Search

Pros

• 429 carries Retry-After and successful responses carry x-ratelimit-* headers
• The guide says to retry 5xx with backoff, and a decision has no side effects
• Error table covers 400, 401, 404, 405, 413, 429 and 5xx with a cause and an action

Cons

• The FAQ says Perplexity does not guarantee uptime or recovery time
• The token limit has no published number, and the 10 requests a second is shared with the 27B model
• 404 and 405 have empty bodies, 504 can be HTML, and an oversized image waits about a minute before a 504
• No Decisions component on the status page, and the model's record is a day long

Pros

• OpenAPI 3.1.0 description with questions discriminated on type and unknown fields rejected
• Error table gives a cause and an action for each status
• Examples in Python, TypeScript and curl, and Markdown twins listed in llms.txt

Cons

• 404 and 405 have empty bodies, and a 504 can be HTML, which a model can't parse for a cause
• model is a free string, and the response echoes the name sent rather than the version that answered
• The official SDK examples name the 27B v1.1 model, not Flash
• No page lists supported languages

Pros

• $0.01 per million input tokens, half the 27B model's price, with free output
• Price is published without a login and has no per-request fee
• Same request and response as pplx-decider-v1.2, so switching is a change to model
• Weights are Apache-2.0 for teams that would rather pay for a GPU than tokens

Cons

• Advised one question per request bills the state again for every question
• Prepaid credits need a card, and no free allowance was found
• No x402, MPP or L402, so an agent cannot pay for itself
• No per-key spending limits found, and no batch route or caching

Pros

• Flash v1.2 has a changelog entry under October 2026
• Versioned model name and a /v1 path
• Python SDK 0.44.0 and TypeScript SDK 0.39.0 carry Decisions methods from 15 October
• Repository pins torch 2.14.0 and transformers 5.17.0

Cons

• A retired name routes to its replacement with no notice period
• Responses echo the name sent, not the version that answered
• The pplx-decider-flash-latest alias can move, and the status page has no Decisions component
• Model card and release manifest still call the public repository private, and the repository has no lock file or CI

Pros

• tools_filter allowlists MCP tools and tools_arguments pins values the model cannot change
• No telemetry found in the source, and OpenTelemetry tracing is off by default
• Advisories are published on GitHub with CVEs and fixed versions
• The framework holds no credential of its own

Cons

• On 1.12.0 a missing api_key sends OPENAI_API_KEY to another provider, fixed on main and unreleased
• No tool-approval or confirmation primitive, and a caller's speech and MCP results go straight to the model
• Three high or critical advisories since November 2025, in the deprecated LiveKit serialiser and the development runner
• The development runner's /start, /daily and dial-in endpoints take unauthenticated requests by design

Pros

• Error categories separate permanent failures from transient ones
• Per-tool timeouts, with cancellation on interruption by default
• is_usable flag per service and a policy for unusable processors

Cons

• No idempotency guidance for tools with side effects
• Open regressions include Anthropic streaming dropping tool calls (6084) and failing default requests (6107)
• Whether CI passes on main is unchecked, and GitHub reply times were not readable
• No latency or rate-limit figures found in the reviewed evidence

Pros

• Provider-neutral FunctionSchema and Pydantic Settings classes per service
• ErrorCategory separates permanent failures from retryable ones, and MCP failures return to the model as text
• tools_arguments pins values and removes them from the model's schema
• llms.txt (113 KB), Markdown per page and llms-full.txt (4.2 MB)

Cons

• OpenTelemetry reference states enable_tracing True, while the 1.12.0 source defaults it to False
• No idempotency guidance for tools with side effects
• No prompt-injection guidance found for tool results that reach the model

Pros

• Eight PyPI releases in 90 days, the latest 1.12.0 on 26 September 2026
• Dated Keep a Changelog file with pull-request links and breaking changes flagged
• Deprecated sections in most releases, with removal named for 2.0.0
• A migration guide to 1.0, a uv lockfile and trusted publishing to PyPI

Cons

• 16 breaking or behaviour changes in 1.8.0 and 4 in 1.10.0, both minor releases
• Deprecation notices name 2.0.0 but give no removal dates
• Two security fixes on main were unreleased on 17 October 2026
• No Dependabot or Renovate configuration found, and a passing main is unchecked

Pros

• No OSV advisories for livekit-agents or @livekit/agents on 17 October 2026
• record=False and TurnDetector(version="v1-mini") keep uploads and turn audio off LiveKit Cloud
• security.txt with a PGP key, and a disclosure policy with safe harbour
• MCP allowed_tools and tool_result_resolver limit tools and trim results (Python only)

Cons

• No built-in approval step or read-only mode, and no prompt-injection guidance found in llms-full.txt
• In dev mode the source sends the LiveKit key and secret to agent-gateway.livekit.cloud when both are set, unless LIVEKIT_INFERENCE_URL is. Self-hosted keys unchecked
• Agent Observability keeps PII redaction off by default, and whether Observability is on for new Cloud projects is unchecked
• No SECURITY.md in the repository, and security.txt has no Expires field

Pros

• Interrupted tools keep their result, and disallow_interruptions() protects writing tools
• Four on_duplicate modes, including reject and confirm
• Build plan limits are published, with allowances as a hard cap

Cons

• Duplicates are matched by tool name only, and there are no idempotency keys
• 41 of the 68 open issues among the latest 100 had no comment
• LiveKit Cloud's status page lists a critical incident on 13 October 2026 (observability uploads)
• What an agent sees at a LiveKit Inference limit, such as a 429, was not found in the dossier

Pros

• Tool schemas come from typed signatures and docstrings, with raw JSON Schema accepted
• Invalid arguments return as a ToolError that names the tool
• Pages say when to use a realtime model or a pipeline, and when to choose v1 or v1-mini
• llms.txt, .md on every page, llms-full.txt and a docs MCP server

Cons

• The llms.txt link to the Python API reference's Markdown returns 404
• The quickstart still ends with agents.cli.run_app(server), deprecated in 1.8.8
• No changelog file, and release notes only on GitHub, which the dossier couldn't read
• on_duplicate matches by tool name only, and MCP tooling is Python only

Pros

• 17 PyPI releases in 90 days, the latest 1.8.8 on 15 October 2026
• Python 1.8.8 and Node.js 1.9.3 released on the same day
• Renovate, pinned actions and a lockfile that holds new dependencies back seven days
• Deprecations flagged in code and docs, including mcp_servers and cli.run_app

Cons

• No CHANGELOG file, and the GitHub release notes are unchecked
• 2.0.0b1 on PyPI since 12 October 2026 with no migration guide found
• A removal dated 30 April 2026 for api_version is still pending in 1.8.8
• 41 of the 68 open issues among the latest 100 had no comment

Pros

• The SDK holds no credential of its own and opens no port
• lite mode makes no LLM calls and sends text only to the embedder
• History and pipeline-trace logging can be switched off by environment variable
• CI pins its actions by commit with read-only contents permission

Cons

• The local server has no authentication and allows any web origin, delete routes included
• No read-only mode, and delete_all() confirms only through the OpenClaw plugin
• delete() leaves the raw conversation and logged copies, and can reactivate a superseded fact
• Users are kept apart only by the user_id the caller passes

Pros

• Each result carries a score, and limit, min_score and layers size the output
• Filters by user, agent, session, source, workspace and branch apply in the store before results are cut to the limit
• On by default, history.db and the pipeline traces record each write, update and delete for later inspection

Cons

• A failed reader returns empty buckets that look the same as no stored memories
• Deleting a fact's newest version makes the superseded version active again
• Results are untyped Dict[str, Any], with docstrings and every guide under docs/ in Chinese
• LoCoMo 72.6% and MemoryArena 55.31% are the vendor's figures, not checked

Pros

• Docstrings on add() and search() say when each scene and search mode calls an LLM
• Worked examples in the README and guides, and an English README with a mode table
• Invalid arguments raise ValueError with a message, and evolve() returns success: false with an error

Cons

• Every result is an untyped Dict[str, Any], with its shape described only in docstrings and guides
• Docstrings and every guide under docs/ are in Chinese, which limits what a model or operator can read
• No error catalogue, and a failed reader returns empty buckets that look like no memories
• No llms.txt, and docs/usage.md still pins 2.0.1 for every optional extra

Pros

• CHANGELOG.md has dated entries for 2.0.1 and 2.0.2, and 2.0.2 corrects the licence metadata
• CI pins its actions by commit and runs the pytest suite on pushes to main and on pull requests
• Source went public under Apache-2.0 on 16 October 2026, so future changes are readable in the repository

Cons

• No notes on breaking changes for the 34 releases of the 1.x line or for the move to 2.0
• No deprecation policy, and the environment reference says older settings no longer take effect, without dates
• Core dependencies such as pydantic, numpy and chromadb are unpinned above a floor, with no lockfile
• CI tests Python 3.12 only against a declared floor of 3.9, and Actions results are unchecked

Pros

• Passkey approval recorded on every purchase instruction
• Mandates cap amount, merchant, category code, expiry and recurrence
• Per-request RFC 9421 signatures with a nonce and 8-minute window
• Disclosure through HackerOne with a safe-harbour promise

Cons

• No documented way to revoke an agent's TAP key
• No prompt-injection guidance in TAP, the guide or Visa's agent skill
• Visa's demo agent kept PAN and CVV in state and logs until June 2026
• Ten credentials and keys to keep out of the agent's context

Pros

• No fee to read or implement the Trusted Agent Protocol
• Visa Developer sandbox is free
• The MIT-licensed visa/ai kit and the Acceptance guide are public

Cons

• No Intelligent Commerce prices published
• Production fees sit in a Visa Developer agreement
• Sandbox needs approval of a restricted product, with no timeline found

Pros

• Dated monthly release notes on the Developer Centre
• The Acceptance guide carries numbered revisions (25.09.01 pilot, 25.11.01 passkey service)
• The June 2026 security fixes to the visa/ai kit were committed in public

Cons

• No VIC release note, TAP change or VIC client change in the last 90 days
• The TAP specification is unversioned and undated, with updates mandatory within six months
• Neither repository has CI, and visa/ai pins turbo to latest
• GitHub issue activity is unchecked, and the restricted VIC docs couldn't be read

Pros

• The Trusted Agent Protocol specification, sample code and visa/ai kit are public
• A documentation MCP server and llms.txt can be read without Visa approval
• Visa Developer sandbox access is free

Cons

• VIC is a restricted product, so credentials come only through Visa onboarding
• Ten credentials and keys are needed for Visa's MCP example
• Visa gives no review timeline for the restricted request
• A consumer's passkey approval is needed on each purchase instruction

Pros

• The card number never reaches the agent
• Tokens can be single-use, merchant-specific or time-limited
• Verifiable Intent key-binds each layer through cnf
• Mastercard runs a public bug bounty on Bugcrowd

Cons

• Verifiable Intent v0.1 defines no credential revocation
• No public token revocation for Agent Pay
• No prompt-injection guidance in the guides or the specification
• The key directory and security.txt couldn't be read

Pros

• Verifiable Intent specification and SDK are free under Apache-2.0
• Merchant guides are readable without an account

Cons

• No fee schedule for registration, agentic tokens or Agent Pay for Machines
• No public sandbox or trial
• Onboarding terms are not published

Pros

• Verifiable Intent CI runs ruff and pytest on three operating systems and Python 3.10 to 3.13
• Verifiable Intent pins its CI actions to tags and keeps a CHANGELOG.md
• Verifiable Intent v0.1.0 is tagged, dated 5 March 2026

Cons

• Early preview docs removed with no notice and still linked from Mastercard's own post
• The 17 April 2026 breaking change is missing from the Verifiable Intent changelog
• No Agent Pay changelog, status page or deprecation notices
• Verifiable Intent issues and any Agent Pay docs behind a login are unchecked

Pros

• The merchant guides and llms.txt on Mastercard Developers need no account
• The Verifiable Intent specification and Python SDK are Apache-2.0 and can be cloned
• Mastercard's documentation MCP server is public

Cons

• No self-serve registration, published process or fee schedule was found
• No public Agent Pay sandbox or API reference
• Tokens are provisioned per cardholder after authentication with the agent platform
• No keyless or x402 route

Pros

• Five-minute OAuth tokens with a revoke endpoint over mutual TLS
• Credentials issued only against a passkey-approved intent
• Issuer risk check before any credential is issued
• A cap on credentials issued per intent

Cons

• Card Member intent revocation is not yet available
• No security.txt, disclosure policy or bug bounty found
• Specification unread, so field-level controls are unverified
• No prompt-injection guidance for the agent side

Pros

• A developer portal account costs nothing
• The overview states the access conditions plainly

Cons

• No fee published for ACE
• Specifications need a confidentiality agreement before they can be read
• Commercial terms are set in an unpublished registration agreement
• No free tier, and sandbox access needs approval

Pros

• The overview carries a last-updated date of 10 April 2026 and the product record a version
• The 13 October 2026 post sets out the Intent Intelligence design
• Support by email and the portal's support form

Cons

• The overview says ACE materials change without notice
• Two of five specifications still under development six months after launch
• The portal marks retired products deprecated without stated notice periods
• No SDK, and purchase protection and the registered-agent list have no date

Pros

• The route in is stated, with a form, an agreement and a portal project
• The overview and API security docs are public
• A developer portal account costs nothing

Cons

• The specifications and guide sit behind a confidentiality agreement
• Registration approval isn't guaranteed
• A CA-issued mutual TLS certificate is needed for the sandbox
• No SDK, MCP server or self-serve sandbox exists yet

Pros

• Both tools carry readOnlyHint: true
• OAuth scopes split public and private search
• Activity log records tool calls and arguments
• Valid security.txt

Cons

• API key accepted as a URL query parameter
• ref_read_url returns arbitrary third-party pages
• Key rotation and revocation not described
• SOC 2 in progress, and Centure.ai not in the subprocessor table

Pros

• Two tools with one string parameter each
• About 600 characters of definitions in all
• readOnlyHint: true on both tools
• Separate OAuth scopes for public and private docs

Cons

• Private search triggered by query text, not a parameter
• Injection screening is an untested vendor claim
• No documented rate limit or 429 guidance
• 200 one-time free credits

Pros

• One-business-day support reply promised
• Legacy subscriptions continue unchanged
• Registry entry under Ref's own domain

Cons

• npm package unchanged since 4 November 2025
• Changelog index stops at July 2026
• No deprecation policy found
• Status page is hand-written

Pros

• Two tools and about 600 characters of definitions
• Both tools marked readOnlyHint
• README shows worked search and read sequences

Cons

• Private search triggered by text inside the query
• No documented errors
• A 401 is reported as an email verification message
• No guidance on when not to use a tool

Pros

• One required field on Create Bot
• MCP page lists a use case for each of 45 tools
• Errors carry a code and detail

Cons

• Create Bot reference is about 740 KB
• 400 response has no body schema
• Transcription settings are open objects
• No running API changelog

Pros

• Idempotency-Key on all writes for one hour
• Per-endpoint limits published
• Scheduled bots get a dedicated instance

Cons

• No public status page or incident history
• Ad-hoc bots can fail with 507
• Uptime guarantees on Enterprise only, no figure
• No health-check endpoint

Pros

• Markdown twin and OpenAPI 3.0.3 on every page
• Agent quickstart names the steps that need a person
• States that it returns no summaries
• Idempotency keys on writes

Cons

• Create Bot page about 740 KB
• Create Bot documents 201, 400 and 507 only
• No REST API changelog
• MCP schemas unchecked

Pros

• Five free recording hours
• Self-serve with no contract
• One POST for the first call

Cons

• Signup form card question unchecked
• Webhooks need a public URL
• Keys carry no scopes

Pros

• No incident in the last 90 days
• 100 calls per 15 seconds, with headers
• Webhooks retry hourly for up to 72 hours
• Check by processor_id before retrying a POST

Cons

• No idempotency keys
• No Retry-After or backoff guidance found
• SLA applies to a tier the pricing page doesn't list
• Monthly API cap of ten times plan transactions

Pros

• Free sandbox with its own credentials
• 7-day trial needs no card
• No sales approval found

Cons

• Browser signup required
• Key rotation unchecked
• Sandbox capped at 200 documents