BlockRun.AI vs SWE-2 Flash

BlockRun.AI 100

x402 v2 on its own gateway, USDC on Base and Solana, and since MCP 0.55.0 (28 October) on Circle's Arc through arc.blockrun.ai (40). Per-token prices per model published without a login, plus a flat $0.001 fee per wallet call on Base (20). Seven free models per the status page's menu, no card or sign-up, and a wallet costs nothing to create (20). An agent can create its own wallet and pay per request with no human sign-up (20). 40 + 20 + 20 + 20 = 100.

SWE-2 Flash 20

Published rubric. No payment protocol (0). Plan prices are public, but no per-token price for SWE-2 Flash is on a readable page; the docs' cost table loads in the browser and the post gives only 'one-fifth the price' of SWE-2 (10). Free through 30 November 2026 on Devin Desktop and CLI, but the docs say Free tier users only have SWE-1.6, so whether the Free plan reaches it, and without a card, isn't confirmed; the in-between value used on the devin listing (10). A person signs in through a browser (0). 0 + 10 + 10 + 0 = 20.

BlockRun.AI 88

MCP reading. 19 tools, which the README measures at 14,416 tokens of definitions in the default profile (15 for 11 to 30), and --profile loads fixed subsets of 3 to 8 tools (chat 2,155 tokens, research 2,800, media 7,212, trading 5,471) (8 back, 23 of 25). Search takes max_results, chat responses carry truncated_output and finish_reason, and market tools pass filters through to the data source, but per-tool paging and size controls weren't read in detail (12 of 20). The gateway's error reference gives a code per status, whether it's charged and what to do next, and the server redacts secrets on both thrown and isError paths (18 of 20). Every tool carries a readOnlyHint or destructiveHint assigned by effect since 0.33.0, with a test that fails on an unannotated tool. Payment settles only after a successful upstream response, and since 0.54.2 a withdrawal that may have moved money is never signed twice (20). Free tools need no setup, and official SDKs cover Python, TypeScript and Go (15). 23 + 12 + 18 + 20 + 15 = 88.

SWE-2 Flash 10

Model reading (tool use, structured output, caching, context, batch, SDKs). Tool use is Devin's harness, not something a caller configures; no context length, output limit or cache price is published for SWE-2 Flash (5 of 25). No documented output-size or reasoning controls for this model; SWE-2's effort levels aren't stated for Flash (0 of 20). No model-level error documentation (0 of 20). No idempotency or retry guidance (0 of 20). One flag or picker selects it and devin -p runs a single turn and prints to stdout, but there is no SDK or direct endpoint (5 of 15). 5 + 0 + 0 + 0 + 5 = 10.

BlockRun.AI 90

MCP reading. All 19 tools take zod input schemas, which the MCP SDK turns into JSON Schema, per the 1 October read of the source (25, was 10 for the gateway's OpenAPI document, which robots.txt still keeps our reader out of under /api/). llms.txt served at blockrun.ai/llms.txt (10). The tool descriptions state purpose and order of use, such as 'discover markets ... with blockrun_markets first' and 'Run action:"setup" FIRST', per the 1 October check (15 of 20). Enums and numeric bounds, but seven fields across six tools take a free-form z.any() JSON body, per the 1 October check (10 of 15). The docs have an error reference with codes per status and recovery steps, and the README has examples for each client (15). A dated gateway changelog, last entry 25 October 2026, and a CHANGELOG.md in the MCP repository through 0.55.0 (15). 25 + 10 + 15 + 10 + 15 + 15 = 90.

SWE-2 Flash 29

Model reading. No model API, so no OpenAPI entry; the Devin v3 OpenAPI file lists SWE-2 agents only, and no model card was found (0). docs.devin.ai serves llms.txt and Markdown copies of every page (10). The launch post says what it is for (automations, code review, feature development, documentation) and the CLI docs say when to pick a SWE model, but the models pages don't list SWE-2 Flash yet (6 of 20). No documented model ID, reasoning settings, context or output limits to type (0 of 15). The CLI pages show --model and /model examples, with no model-specific errors (3 of 15). Named, dated model versions on Cognition's blog and public release notes, but no release note for SWE-2 Flash yet; the newest is 2 November (10 of 15). 0 + 10 + 6 + 0 + 3 + 10 = 29.

BlockRun.AI 85

MCP reading. @blockrun/mcp 0.55.0 published to the official MCP registry on 28 October 2026, and a gateway changelog entry on 25 October (30). 40 registry versions from 0.35.0 on 3 August to 0.55.0 (20). Issue replies couldn't be read, as GitHub's issue pages answered 403; the changelog credits numbered reports fixed within releases (10 of 25). Listed in the official MCP registry as io.github.BlockRunAI/blockrun-mcp, a GitHub-verified namespace, active, with 0.55.0 marked latest (15). CI on Node 20.19 and 22 with typecheck and tests on every pull request, and a Renovate configuration in the repository (10). 30 + 20 + 10 + 15 + 10 = 85.

SWE-2 Flash 53

Model reading. Released 4 November 2026 (30). Churn and notice in place of release counts: SWE-1.6, SWE-1.7, SWE-1.7 Lightning, SWE-2 (10 September) and now SWE-2 Flash in a few months, with no model deprecation notice period found and short names that move to the newest model (10 of 20). Public release notes and a support address, no public tracker (10 of 25). No official SDK for the model (0 of 15). The docs are kept current but don't yet cover this model (3 of 10). 30 + 10 + 10 + 0 + 3 = 53.

BlockRun.AI 65

Read with the local-software lines, as the listing's kind is mcp and the owner runs the server over stdio, though every paid call lands on BlockRun's gateway (the reading assymetrix-mcp and copilot-studio-mcp get). The 1 October check read it as a router. Installs from the official npm package @blockrun/mcp with Node 20.19 or later stated in engines (20). The CI workflow runs typecheck, build and tests on Node 20.19 and 22 on every push and pull request, with a required gate job. Run results weren't readable, as GitHub's pages answered 403 (20 of 25). Open issues couldn't be read. The changelog names numbered reports fixed in releases, such as #176 and #177 in 0.54.3 and 0.54.4 (10 of 25). Semver numbering with breaking changes marked BREAKING in CHANGELOG.md and shipped as minor bumps, as its own entries say (15). Version 0.55.0, pre-1.0 (0). 20 + 20 + 10 + 15 + 0 = 65. For the gateway behind it, blockrun.ai/status still shows live checks of the Base and Solana gateways and says "None recorded on this page yet" under incident history, the terms still say "We do not commit to any particular uptime", and free models are limited to 30 requests a minute and 300 an hour per IP with 429s carrying Retry-After.

SWE-2 Flash 50

Model reading, for the surface it runs on, Devin Desktop and Devin CLI. Status page at www.devinstatus.com (Atlassian Statuspage) with Desktop Agent and Desktop Tab components besides the cloud ones, read on 4 November 2026 (20). The history feed for the 90 days from 6 August lists 'Devin unavailable' for 20 minutes on 13 August with no component named, read as across the board and a major as on the devin listing; Devin Cloud unavailable on 13 August and the web app down on 24 September name cloud surfaces this model doesn't use; the rest are degraded-performance incidents (new sessions on 3 September, 'multiple services' on 17 September, Ask Devin on 26 October, automation triggers on 4 November) and session queuing on 10 and 11 August, read as minor and a scheduled Devin Desktop extension marketplace upgrade on 7 August, read as maintenance. One major (10). No rate limit figures for the model or the CLI; usage is a daily and weekly quota with no numbers (0). No 429, backoff or retry guidance for this surface (0). Cognition publishes an SLA (25 February 2026) with uptime and response times that applies when included in an order form, read as a contractual SLA on Enterprise, as on other listings (10). The launch post makes it available today with no preview or beta label (10). 20 + 10 + 0 + 0 + 10 + 10 = 50.

BlockRun.AI 73

The editorial half. The MCP server and SDKs are MIT and the gateway is closed. The listing is graded as the MCP server, so 30 as assymetrix-mcp got for an MIT server in front of a closed API (was 15 under the router reading). The terms and privacy policy, both last updated 21 October 2026, now name the same entity, BlockRun, Inc., as contracting party and data controller. The privacy policy now says prompts, completions and tool calls to blockrun.ai, arc.blockrun.ai, nano.blockrun.ai and api.blockrun.ai are stored with the paying wallet or account and kept "until we delete it; it has no fixed expiry", usage records and connection metadata for 13 months, while the Solana gateway keeps no request content. The 1 October policy said prompts weren't stored past the request and metadata was kept 30 days. The documents agree with each other, but content has no retention period and no subprocessors are named (18 of 30, was 20). No deprecation policy, and the terms say a provider may withdraw a model at any time. Removals are dated in the changelog, such as Gemma 4 31B delisted on 2 October, the same day (5 of 20). Upstream providers are named and Google Analytics is disclosed with its cookies and retention. Data locations aren't stated, and whether the MCP server sends telemetry wasn't read (10 of 20). 30 + 18 + 5 + 10 = 63.

SWE-2 Flash 64

Editorial half. Closed model under Cognition's platform terms; the weights aren't public and the sharing programme isn't described yet (15). Terms, privacy policy, security page and DPA agree, with training on self-serve data by default and no retention periods, as read for the devin listing (18). The API versioning policy covers API endpoints, not models, and no model deprecation notice was found (5 of 20). Sub-processors listed with purpose and country, per the devin listing's 8 October check (18). 15 + 18 + 5 + 18 = 56.