---
id: "claim-parameter-removal"
type: "claim"
source_timestamps: ["00:00:00"]
tags: ["compute-constraints", "api-design"]
related: ["concept-adaptive-thinking"]
confidence: "medium"
testable: false
speakers: ["Nate B. Jones"]
sources: ["s12-opus-47"]
sourceVaultSlug: "s12-opus-47"
originDay: 12
---
# Anthropic removed parameter controls to manage compute

## Claim

[[entity-anthropic-d12|Anthropic]]'s removal of user controls like **temperature** and **top_p** is a deliberate strategy to manage their compute constraints.

By forcing users into an [[concept-adaptive-thinking|Adaptive Thinking]] paradigm, Anthropic can:
- Throttle demand.
- Optimize their infrastructure utilization.

…at the expense of **developer control**.

## Confidence: Medium

The parameter removal can be verified empirically against API docs; the **motive attribution** (compute management) is speculative.

## Testable: No

Motive cannot be falsified. The fact pattern (parameters removed) can be verified, but "to manage compute" is an inference.

## External Validation Status

**Partially supported / partially refuted** per the enrichment overlay:
- Frontier APIs do trend toward opaque controls (no fine-grained params in some agentic evals).
- However, **Anthropic retains temperature/top_p in Claude 3.5 Sonnet API docs** — no removal confirmed in public APIs as of 2026.
- The removal claim may be specific to a hypothetical Opus 4.7 endpoint that does not publicly exist.

## Open Question

Will controls return? See [[question-parameter-controls-return]].

## Operator Workaround

Use natural-language reasoning triggers: see [[action-force-reasoning]].

## Cross-References

- Concept: [[concept-adaptive-thinking]]
- Action: [[action-force-reasoning]]
- Open question: [[question-parameter-controls-return]]