This index exposes the material behind every decision guide: what we reviewed, when we retrieved it, the claim it supports and where the evidence stops.
181decision guides
790source records
782scoped claim notes
How to read this index
A citation is not a transferable result.
Reviewed identifies the part of the source used. Supports states the bounded proposition we draw from it. Retrieved records when time-sensitive material was checked.
Vendor documentation establishes vendor claims and product behavior as documented, not independent performance. Papers establish results only for their stated methods and tested scope. AccessAllGPT recommendations remain labeled analysis.
AccessAllGPT opened Google’s November 11, 2026 launch announcement and the live Decisions API documentation during the November 12 Asia/Kolkata publishing run. We reviewed availability, model identity, pricing, benchmark qualifications, question types, confidence semantics, input handling, best practices and limitations. These are first-party product statements, not independent performance measurements. We refreshed the official release radar, which returned 20 sources without source errors, and checked existing publication coverage before selection. We did not invoke the API, test SDK compatibility, measure latency or independently validate calibration.
AccessAllGPT opened AWS’s Bedrock announcement, live model card and pricing page on November 12, 2026. We reviewed the displayed publication and model-launch dates, inference-profile IDs, endpoint and API support, Standard prices, service tiers, caching rules, reasoning controls and documented limitations. The radar was discovery evidence only: its November 11 feed date differs from the November 10 date displayed on the article. We checked the existing Kimi report, weekly ledger and live research index to distinguish this AWS access story from the earlier Moonshot weight/API release. Availability, capabilities, privacy assurances and performance are vendor statements; source discrepancies are reported rather than resolved by assumption. We made no paid inference call, inspected no AWS account and reproduced no benchmark.
Reviewed: Displayed November 10 publication date; launch overview; Chat Completions and Responses examples; cross-Region profiles; reasoning; Flex; caching; availability
Supports: AWS’s availability statement, Bedrock API and profile identifiers, vendor-attributed speed comparison, service-tier and cache guidance, and inference data-handling assurances. Its narrower reasoning description differs from the current model card.
Reviewed: Moonshot AI on-demand pricing; Kimi K3.1 Pro - Highspeed Global, US and IN CRIS table; cache rates; Priority and Flex footnotes
Supports: Corroborates Standard per-million-token input, output, cache-read and cache-write rates across global and geographic inference, plus Priority’s 75% premium and Flex’s 50% discount.
AccessAllGPT retrieved Tether AI Research’s November 11, 2026 Hugging Face announcement, both official model cards, both public model API records and the source repository LICENSE on November 12. We reviewed the announcement date, base model, artifact names, license, quantization sizes, serving settings, benchmark tables and footnotes, training disclosure and intended-use restrictions. The supplied official release radar was discovery evidence only. We checked the tips file, existing articles, weekly ledger and live research index for duplicate coverage. Repository listings are directly observed registry facts; benchmark scores, runtime compatibility and deployment suitability are vendor claims. We did not download the weight files, run inference, reproduce benchmarks or measure phone latency, memory, energy use or privacy.
Reviewed: Available files; quantization benchmark table; evaluation hardware and footnotes; llama.cpp and QVAC examples; limitations
Supports: Lists three concrete GGUF filenames and approximate sizes, Q8_0 recommendation, vendor quantization scores and the H100 rather than phone evaluation hardware.
Supports: Directly observed public, ungated repository state and the model.safetensors listing, rather than assuming future-tense announcement wording proves availability.
AccessAllGPT opened Google’s first-party November 11, 2026 CarPlay announcement on November 12 and reviewed the article body, rollout instructions, conversation examples, history-sync statement and eligibility footnote. We distinguish those product claims from our recommendations. We checked the existing article library, weekly ledger and live research index to avoid duplicating the earlier Android Auto report. The supplied official release radar identified the candidate; its discovery record was not treated as proof of availability. We did not connect an iPhone to a vehicle, use Gemini Live, inspect account settings or measure driving distraction.
Reviewed: November 11 publication date; opening rollout announcement; Pick up where you left off; Make the most of your drive; Get started today; Daily Brief eligibility footnote
Supports: First-party announcement date, global iOS rollout and supported-language scope, CarPlay entry points, conversation and history-sync claims, Gmail and Calendar examples, setup prerequisites and narrower personalization exclusions. The post does not list a new model ID, API endpoint, numerical compatibility floor or separate CarPlay price.
AccessAllGPT directly retrieved AWS’s November 11, 2026 article and the linked Guidance for Codex on AWS repository README and Native AWS Access quickstart on November 12. We reviewed the rollout choices, model identifiers, example configuration, identity flow, telemetry, billing distinctions and rollback requirements. The official release radar was discovery evidence only. We checked existing articles, dates, the weekly ledger and the production research index for overlapping coverage. This is a primary-source briefing: repository contents are observed documentation, while operational behavior and availability are vendor-described. We did not deploy resources, authenticate to Bedrock, run a Codex task through AWS or measure performance or cost.
Reviewed: Displayed November 11 publication date; rollout choices; Native AWS Access; model IDs; identity isolation; gateways; telemetry and billing; configuration boundaries; cleanup
Supports: AWS’s current deployment guidance, local execution architecture, native pilot recommendation, example model identifiers, Region/access caveats, distinct evidence sources and staged rollout and rollback requirements. Does not establish first availability or a new model launch.
Supports: Documents native SigV4 credentials, workstation tool execution, gateway request flow and the different operating and identity models for native access, LiteLLM, Portkey and AgentCore.
Supports: Documents IAM Identity Center prerequisites and the native access runbook, explicitly describes soft monitoring as alerts rather than blocking, and provides an isolated validation workflow with optional real Codex execution.
AccessAllGPT directly retrieved AWS’s November 11, 2026 announcement, the AgentCore Web Search developer guide and the AgentCore pricing page on November 12. We reviewed the launch date, operation and tool identifiers, authentication, integration requirements, filters, result schema, six-Region availability, quotas, pricing and acceptable-use rules. We checked existing coverage, the weekly ledger and the live research index for duplication. The supplied official release radar was discovery evidence only. Availability, behavior, index operation and privacy properties are AWS documentation or claims, not independently measured outcomes. We did not call the paid API, provision AWS infrastructure, test SDK compatibility or benchmark retrieval quality.
Reviewed: November 11 date; standalone API; IAM policy; Python and CLI examples; SDK versions; filters; CloudTrail; PrivateLink; pricing; availability
Supports: Establishes the announcement date, direct-call integration, identifiers, documented request limits, SDK requirements, vendor privacy claims and the difference from the existing gateway route.
Reviewed: API overview; API versus connector differences; default result counts; publication date semantics; Regions; quotas; acceptable use
Supports: Confirms six commercial Regions, the GovCloud exception, IAM-only API authentication, per-request filters, result defaults, default request quota and citation and bulk-use restrictions.
Reviewed: Web Search on AgentCore; consumption-based pricing; per-query price and no-minimum-fee details
Supports: Lists Web Search at $7 per 1,000 queries with usage-based billing, no minimum fee and no upfront commitment; does not establish a complete agent workload cost.
AccessAllGPT directly retrieved Anthropic’s November 9 launch announcement, AWS’s November 9 availability post and the public OpenRouter Models API on November 10, 2026. We reviewed the announcement’s introduction, performance and efficiency, coding, safeguards, data privacy and availability sections; AWS’s access, retention, invocation and migration guidance; and the two Fable 5.2 registry entries. Vendor claims, platform-specific access facts, registry specifications and AccessAllGPT analysis are distinguished below. This article covers the general-purpose model launch and coding/API implications, not biological applications. We did not invoke either model, run benchmarks, validate customer testimonials or independently inspect the system card or every cloud’s documentation.
Reviewed: November 9 date; introduction; performance and efficiency; coding; safeguards; data privacy; availability
Supports: First-party announcement of the shared underlying model, general versus verified access, standard and fast pricing, vendor-reported coding scores, speed claims, cloud availability, preservation of thinking and retention arrangements.
Reviewed: November 9 date; data retention and Enterprise Frontier Safeguards; getting started; migration; availability
Supports: Confirms Bedrock and Claude Platform on AWS availability, global.anthropic.claude-fable-5-2 invocation, US Geo and Global CRIS, aws_review retention configuration and conditional zero-retention arrangements.
Reviewed: Standard and batch model IDs; context_length; top_provider; architecture; pricing; endpoints; reasoning defaults
Supports: Registry lists standard and batch Fable 5.2 routes, million-token context, 128,000-token maximum completion, modalities, standard and batch token rates, mandatory reasoning and high default effort. This is registry evidence, not an inference test.
AccessAllGPT retrieved Thinking Machines Lab’s November 5 announcement, the OpenRouter model page, public Models API and exact free-route endpoints API on November 10, 2026. We reviewed the announcement introduction, coding discussion and limitations, and the registry identity, creation timestamp, modalities, prices, reasoning settings and provider fields. Coverage is limited to the general-purpose model and API access, not biological applications. Architecture and capability statements are vendor claims; context and routing details are registry observations. No OPENROUTER_API_KEY was set in this publishing environment, so we did not invoke the free model, run the UI test or reproduce benchmark results. We did not inspect downloadable weight artifacts or independently verify the model card.
Reviewed: thinkingmachines/inkling-2-small:free identity, created timestamp, context, completion limit, modalities, pricing, reasoning and supported parameters
Supports: November 9 UTC registry creation, zero input/output token rates, 1,048,576-token context, 131,072-token completion maximum, mandatory reasoning and high default effort.
Supports: Directly observed Thinking Machines provider listing, nvfp4 quantization and zero token rates; tools are listed but explicit tool-choice capabilities are false.
AccessAllGPT opened Anthropic’s November 5, 2026 web report on November 7 and reviewed the complete article, publication metadata, methods, task and field results, acceleration scenarios, discussion, footnotes and authorship. We downloaded and text-extracted the linked technical report and appendix, checked the exact sample construction, sampling weights, classifier pipeline, survey recruitment, scenario assumptions and stated limitations, and opened the public SciNet taxonomy site. All session-use and acceleration results are Anthropic-reported. AccessAllGPT did not access any session transcript, account-level record, classifier output, survey response, Claude Science workspace or underlying SciNet validation set and did not reproduce the analysis.
Reviewed: November 5 publication metadata; summary; methods; field and task results; capability analysis; acceleration scenarios; discussion; footnotes; authorship and citation
Supports: Anthropic reports a privacy-preserving classification study of 207,049 scientific-work sessions from Claude consumer products, a supplemental Claude Science analysis and a survey of 528 researchers. Usage, capability and acceleration results are first-party findings.
Reviewed: Full report; sample construction; task distributions; field and subfield comparisons; theoretical AI capability measure; scenarios; assumptions; limitations; footnotes
Supports: The downloadable report provides the exact sample counts, task shares, field comparisons, scenario assumptions and qualifications summarized in the web article.
Reviewed: Usage sample; privacy-preserving analysis; sampling weights; SciNet mapping; classifier design and validation; survey recruitment; Claude Science sample; capability measure; acceleration model and robustness analyses
Supports: The appendix documents that the main sample covers Free, Pro and Max consumer plans from August 2 through September 30, excludes programmatic Claude Code use, weights sessions for sampling probability and relies on model classifiers and an LLM-built task taxonomy.
Reviewed: Public taxonomy overview; domain, field, subfield, task and step counts; data-exploration links
Supports: The live SciNet site exposes the taxonomy scale used by Anthropic: six domains, 34 fields, 318 subfields, 7,262 tasks and 90,583 steps. It does not independently validate Anthropic’s Claude-session classifications or acceleration estimates.
AccessAllGPT opened Anthropic’s November 6, 2026 Project EVE report on November 7 and reviewed the complete article, publication metadata, experiment descriptions, charts as described in the text, reported results, caveats and footnotes. We separated the replayed EVE Online market experiment from the live EVE Frontier fleet experiment and treated every numerical result as vendor-reported. AccessAllGPT did not receive the simulator, market snapshots, prompts, scaffolds, agent trajectories, private messages, monitor scores or game access, and did not reproduce any run. The report does not expose enough case-level data or repeated-run detail for an independent effect estimate.
Reviewed: November 6 publication metadata; research scope; EVE Online market simulator; two-week and six-month trading results; directional bets; EVE Frontier fleet setup; scaffolds; coordination and sabotage experiments; monitor results; reflections; footnotes
Supports: Anthropic reports vendor-run experiments in which Claude models traded against replayed EVE Online market data and four-agent teams played EVE Frontier, including trials with one prompted saboteur and limited-access monitoring agents.