anomalyco / anomalyco/opencode

API inference blocked while authenticated model catalog remains accessible

Open
#46,219 3 comments 0 reactions 1 assignee View on GitHub

@fwang is already working on this.

Since Aug 30, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

My OpenCode account has a positive balance, but inference is consistently rejected with HTTP 401 and the error code INFERENCE_ACCESS_BLOCKED.

The same API keys can fetch both model catalogs successfully (HTTP 200), so the credentials are valid enough for authenticated catalog access. Minimal inference requests fail for both:

  • OpenCode Go: deepseek-v4-flash via /zen/go/v1/chat/completions
  • OpenCode Zen: claude-sonnet-5 via /zen/v1/messages

I reproduced this with several newly generated API keys on the same account, including on 2026-08-30 UTC. These were isolated one-turn plain-text requests with no tools, files, multimedia, large context, parallelism, or retry loop.

Could you please clarify:

  1. Is the account or workspace blocked from inference?
  2. What policy or event caused the block?
  3. Is it temporary, and what is the process to appeal or restore access?
  4. Is there a private channel where I can provide the account identifier and exact request timestamps without publishing credentials?

No API keys are included in this report.

Plugins

None; reproduced against the documented HTTP endpoints directly.

OpenCode version

Not applicable; direct API request.

Steps to reproduce
  1. Create a new API key from an account with positive balance.
  2. Fetch the Go or Zen /models endpoint: HTTP 200.
  3. Send a minimal single-user-message inference request to one of the documented model endpoints.
  4. Observe HTTP 401 with INFERENCE_ACCESS_BLOCKED.
Operating System

Linux

Terminal

Direct HTTPS client

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.