Repository navigation
Roadmap
agentstat is in its initial 0.1 stage. This page describes the current direction and backlog, not a release schedule or commitment. Check GitHub Issues and Provider Coverage for current work.
- Validate implemented adapters against real accounts. Synthetic fixtures check request construction and normalization, but provider APIs and account plans can change. Provider-check reports are especially useful for OpenCode Go and Zen, Ollama, and other less-verified paths.
-
Release source changes after
0.1.0. The current checkout includes adapters and behavior that registry consumers cannot get from0.1.0, including OpenCode Go. A future release needs the normal tests, feature checks, packaging, and release review. - Maintain provider behavior. Keep endpoint, credential, scope, error, and normalization fixtures aligned when a provider changes its API. Preserve unknown values instead of inventing limits or spend.
- Improve documentation and examples. Clear credential paths and real-account validation instructions make integrations easier to use and maintain.
The catalog currently has 60 planned integrations. They have IDs and Cargo features, but no working fetch adapter. Examples include Alibaba Coding Plan, Qwen Cloud, Fireworks, Devin, MiniMax, Kimi, Kiro, Vertex AI, Windsurf, Zed, Perplexity, Mistral, AWS Bedrock, Grok, Groq, LiteLLM, Deepgram, and Hugging Face. The full table is authoritative for status; no priority or date is promised for an individual provider.
To propose an adapter, open a provider request describing a read-only usage, quota, balance, or spend interface. A feature flag alone does not make a provider supported. Implementation requires a request path, normalization fixture, account and credential rules, and coverage documentation.
- The crate is a library, not a tray app, dashboard, login service, or background scheduler.
- It does not estimate costs from local transcripts or run inference to test access.
- The currently unsupported Azure OpenAI, Doubao, Muse Code, and Pi entries have specific interface or scope barriers described in Provider Coverage.
- Provider private APIs may change; live validation remains separate from fixture and CI coverage.
See Contributing and Development for a concrete path to help.
Repository · Rust API docs · Issues · Releases · Security