OpenAI API vs SWE-2 Flash

OpenAI API 98

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and forced tool choice, 18 of 20 because GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra call tools only through the Responses API (18). Strict structured outputs (15). Automatic prompt caching with cached input at 0.1x on Astra and Luna ($0.01 per million on Luna) and 0.05x on GPT-6.1 Sol ($0.10) and GPT-6.1 Terra ($0.05), and a 12-hour cache lifetime in the Responses API since 20 October (15). 1.05M context on Astra, GPT-6.1 Sol, GPT-6.1 Terra and Luna (15). Batch at half price (10). Official SDKs in Python, JavaScript and more (10). Documented error codes with retry guidance (15).

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.

OpenAI API 100

Official OpenAPI document (openapi.yaml and openapi.json) in the openai/openai-openapi repository, whose openapi.yaml (version 2.3.0, updated 31 October) lists gpt-6.1-terra (25). llms.txt index with per-product files, and every docs page has a Markdown twin at .md (10). The reference documents each parameter, and model pages say which model fits which job (20). Structured outputs with strict: true on schemas and function tools (15). Error codes guide with types and recovery advice, now with a 400 service_tier error for tiers a project doesn't allow (15). Dated model snapshots and a dated changelog, last entry 30 October (15).

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.

OpenAI API 100

Model reading. Project keys with All, Restricted (per-endpoint None, Read or Write) and Read Only permissions, service accounts, and mutual TLS with X.509 workload identity GA since 26 August, per the 1 October check. The changelog adds project key expiry dates on 10 September, key-creation controls on 15 September and, on 21 October, organisation and project settings that limit which service tiers a project may use (30). API data not used for training unless the customer opts in, since 1 March 2023 (20). Abuse-monitoring logs kept up to 30 days, and Zero Data Retention or Modified Abuse Monitoring by approval. The data-controls guide re-read on 1 November lists Chat Completions, Responses, Decisions and ten other endpoints as ZDR-eligible; /v1/agents, Conversations, Files and vector stores aren't (15). Usage and Costs filter by API key since 4 August, with Admin APIs to match, and audit logs for enterprise (15). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 per the 1 October check, not re-read on 1 November, a Bugcrowd bug bounty and a coordinated disclosure policy, both linked from a signed security.txt. That security.txt had no Expires field on 27 October, which RFC 9116 requires, so the disclosure policy carries this line. It wasn't re-read on 1 November (20).

SWE-2 Flash 53

Read as a hosted model reached through Devin's local clients. The CLI signs in through a browser, or the enterprise identity provider, and stores an API token in credentials.toml that by default is persistent and does not expire and carries the user's access, with no scopes found for it (10 of 30). Devin CLI documents an OS-level sandbox with network filtering, hooks that can block tool calls, and enterprise model allowlists and team settings (14 of 20). Guardrails against prompt injection are Enterprise only and cover user messages, as on the devin listing (8 of 15). Enterprise analytics count tool calls and consumption by model and user; no per-user audit log for the CLI was found (8 of 15). SOC 2 Type II and ISO/IEC 27001:2022, a disclosure address, no bug bounty and no security.txt, per the devin listing (13 of 20). Training: self-serve customer data may train Cognition's models by default, with an opt-out on paid plans that also turns on zero data retention at model providers. Cognition withheld the weights over cyber misuse, which is recorded as a fact, not scored. 10 + 14 + 8 + 8 + 13 = 53.

OpenAI API 87

Model reading. GPT-6 Rosalind, a life-sciences model for approved organisations, launched on 30 October, after GPT-6.1 Terra on 26 October and the Decisions API GA on 22 October (30). Published minimum notice of 6 months for GA models, 3 months for specialised variants, as little as 2 weeks for previews. On 14 October GPT-4o (gpt-4o-2024-08-06, gpt-4o-2024-11-20), GPT-4o mini, GPT-4.1 and GPT-4.1 mini were given a shutdown date of 14 January 2027, 92 days, with no safety or compliance reason stated. These are GA models, so the page's own 6-month minimum wasn't kept, as with gpt-5.4-cyber's 20 days in September. 8 of 12, the award for a minimum of two to three months in practice. Five shutdown dates in the 90 days to 1 November, the Assistants API on 26 August (announced in August 2025), gpt-5.2-chat-latest and gpt-5.3-chat-latest on 10 August (announced 8 May), gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 on 28 September (announced 26 September 2025, missed in the 27 October count), gpt-5.4-cyber on 1 October and the legacy snapshots on 23 October (announced 22 April). Sora 2 and the Videos API (24 September) are scored on the openai-sora listing. Four of the five kept the published notice, so 4 of 8 as before, as amazon-bedrock has for four dates after full notice. Dated changelog several times a month and a help centre (15 of 15). openai-python had 215 open issues per the 1 October check, replies not sampled (5 of 10). Current official SDKs, openai 3.42.0 on PyPI (31 October) and npm openai 7.47.0 (15). Supported runtimes stated, Python 3.10 or later and Node 22 or later, the npm package's engines re-read on 1 November (10).

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.

OpenAI API 90

Closed service with clear terms, SDKs Apache-2.0 (15). The data-controls guide, re-read on 1 November, gives retention periods per endpoint, the training default and the ZDR route. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum for transfers, and nothing in it conflicts with the guide, per the 4 October check, not re-read on 1 November (30). Deprecations page with announcement and shutdown dates, and GET /v1/models returns each model's shutdown_date (20). The subprocessor list, updated 9 July 2026, names its third-party subprocessors and OpenAI affiliates with the processing countries for each and a form to get notice of new ones, and data residency regions are listed, per the 4 October check, not re-read on 1 November (20).

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.

OpenAI API 75

Status page at status.openai.com with component history (20). Two API-wide majors in the 90 days to 1 November, elevated errors across ChatGPT, Codex and the API (the Agents API included) on 29 September, with Chat Completions, Responses, Batch, Realtime, Embeddings, Images, Files and the other API components degraded from 17:52 to 23:14 UTC, and elevated error rates across API models on 17 September, with eleven components degraded from 20:20 to 21:20 UTC. Two majors give 5 of 30. The 25 July incident is now outside the window. The 29 September write-up, posted on 6 October, traces it to a feature rollout that exhausted shared network connection capacity. Every other incident since 3 August that lists an API component is partial or under an hour, so minor. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed every API component but ran 22 minutes (02:26 to 02:48 UTC). Single-model incidents were GPT-5.6 Sol errors on 11 September (09:08 to 11:21 UTC), gpt-5.6-luna errors on 21 October (70 minutes) and GPT-6.1 Sol degraded performance on Batch, Chat Completions and Responses on 27 October (78 minutes). Partial incidents were latency for some Responses requests on the US endpoint on 31 August and 1 September, image generation where some requests failed on 8 September, latency for some Responses and Chat Completions requests on 30 September, large-PDF errors in Responses and an Agents API computer use incident on 6 October, Responses errors for users in India, Japan and Korea on 22 October and errors on some GPT Image 2 edit requests on 30 October (14:35 to 18:36 UTC). Image model incidents on 16 September and 14 October and file download errors on 19 October each ran about 40 minutes. FedRAMP errors for Astra and Sol on 21 October and authentication errors near Illinois on 20 October list no API component. Rate limits published per tier and model family with rate-limit headers (15). 429 guidance, re-read on 1 November, covers Retry-After as a minimum wait, backoff with jitter when it's missing, a gradual ramp, and splits slow_down (429) from server_is_overloaded (503) (15). Scale Tier carries a 99.9% uptime SLA, through sales, per the 1 October check, not re-read on 1 November (10). Responses and Chat Completions are GA (10). 20 + 5 + 15 + 15 + 10 + 10 = 75.

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.