Access guidance · R3 · 20 Sep 2026 UTC
Do not configure a retired or unlisted Union Alpha identifier
This is route-status guidance, not a success recipe. R3 made no request and does not establish access, quota, price, privacy, capacity, or behavior for any route.
A. Former OpenRouter preview
Status
- Do not start a fresh integration on the retired ID or present its historic $0, context, modality, or retention text as current availability.
- Do not treat generic OpenRouter free-variant policy as a model quota. The rule is scoped to free variants; a catalog field such as
per_request_limits: nullis not “unlimited.” R3-S04
B. Current paid Pareto route
- If a Pareto evaluation is separately authorized, review its current listing, access terms, pricing, and route-specific data terms before use.
- Do not send sensitive code based on the former preview’s historical retention wording. R3 did not locate a current Pareto-specific assurance in its narrow audit.
- Do not call paid Pareto an immutable Union Alpha replacement: component models, weights, routing, version and snapshot equivalence are unverified.
C. Former OpenCode Go alias
Status
- Do not rely on R2’s “Free (limited time),” “Unlimited,” “Not used,” or “0 days” language. Those are dated historical documentation, not present route policy or entitlement.
- If OpenCode officially re-lists the alias with an explicit route mapping, only an already-authorized subscriber should make one tiny non-sensitive text request.
- For that future single request, save UTC, model, settings, status, redacted headers/response and latency; stop on any error or limit. One result would be
n=1, not a quota, capacity, SLA, or equivalence result.
R3 observation: zero Go requests were sent because both prerequisites failed—no current alias listing and no pre-existing authorized credential. No account, subscription, purchase, retry, or sensitive-code request was made.
Evidence and precise boundaries: current availability audit · preserved R2 report · current summary.