You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 93d994f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs-site/src/content/docs/guides/providers.md
+25Lines changed: 25 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -221,6 +221,31 @@ validates the key, and stores it. Notable entries:
221
221
Most use the `openai-chat` adapter with a bearer key; a few that expose only an Anthropic-compatible
222
222
endpoint (e.g. **Xiaomi MiMo**) use the `anthropic` adapter (`x-api-key`).
223
223
224
+
### A6API credit quota
225
+
226
+
A custom `openai-chat` provider using `authMode: "key"` and the canonical
227
+
`https://api.a6api.com` or `https://api.a6api.com/v1` base URL receives an A6API credit meter in
228
+
the dashboard and from `ocx account refresh <provider>`. The provider name is arbitrary; detection
229
+
uses the canonical HTTPS endpoint. The meter converts A6API token units into USD using the account's
230
+
hard credit limit and displays the percentage consumed plus remaining credit. Token expiration is
231
+
not shown as a quota reset because expiration does not imply that credit replenishes.
0 commit comments