Paid subscription blocked by expired API key (HTTP 401) despite remaining time and 32% unused monthly quota #56620

Description

Paid OpenCode Go subscription became unusable before expiration

My paid OpenCode Go subscription was still active when my API key suddenly expired, preventing my Hermes AI agent from accessing the service.

My dashboard clearly showed:

• Monthly usage: 68% used — 32% remaining
• Weekly usage: 36% used — 64% remaining
• Rolling usage: 0% used
• Subscription: Cancelled, but the paid period had not ended

Incident timeline — October 18, 2026 (UTC+8)

• 01:12 AM: My Hermes agent (Velos) was actively working.
• 01:14 AM: OpenCode Go suddenly returned HTTP 401.
• 01:19 AM: Repeated requests failed.
• 08:44–08:45 AM: The service was still inaccessible, despite the subscription dashboard displaying remaining time and quota.

Exact error

HTTP 401: This API key has expired. Create a new API key in OpenCode Console and replace it in your client or secret store. Signing in again will not renew this key.

Additional problems

The new Console interface offers no clearly discoverable Go API key replacement path.

I also expected a $5 credit allocation, but the dashboard shows $0.00. Please clarify whether that credit applied to my account and what happened to it.

Requested resolution

1. Explain why my API key expired before my paid subscription ended.
2. Restore access or provide a working replacement method for external AI agents.
3. Explain whether this was caused by recent authentication or platform changes.
4. Compensate affected subscribers for paid service time lost due to this interruption.
5. Clarify the missing $5 credit.

This is a paid-service reliability issue, not simply a documentation problem.

Customers should not lose access to services they have already paid for while their subscription remains active and usage quota is available.

Related GitHub issues

• The API keys disappear from the account, and the agent stops working, reporting: "This API key has expired..." #56556
• auth: expired Go API key error gives no recovery path and misdirects users #56586
• auth: Go API key creation is undiscoverable in the v2 Console and docs still say "copy your API key" #56498
• Go API key is not available in the new v2 Console #52227

Plugins

N/A — External Hermes AI agent using OpenCode Go as its model provider.

OpenCode version

N/A — The affected client is Hermes, not the OpenCode CLI. OpenCode Console V2 web interface.

Steps to reproduce

1. Use an active paid OpenCode Go subscription with remaining usage quota.
2. Configure an external AI agent (Hermes) with a previously working OpenCode Go API key.
3. After the API key expires unexpectedly, send a model request.
4. Observe HTTP 401: "This API key has expired."
5. Check the subscription dashboard and confirm the paid period has not ended.
6. Attempt to locate a replacement Go API key in the updated Console interface.

The exact server-side key expiration cannot be manually reproduced on demand.

Screenshot and/or share link

I have screenshots showing the remaining subscription time, unused quota, updated Console interface, and timestamped HTTP 401 errors.

I also recorded the incident on video and can provide it for investigation.

No OpenCode /share link is available because the affected client is an external Hermes agent.

Operating System

Windows desktop / Firefox browser. Hermes is running on a remote VPS; server OS version not confirmed.

Terminal

Hermes AI agent interface. Terminal and shell details not confirmed.