Credit Guide
The navigation label stays as Credit Guide, but the public model should be understood as a quota model.
Current mental model
Key capability usage may depend on both:
- Skill quota
- Underlying service quota
Why both layers matter
Some actions count as both a Skill usage and an underlying service consumption. The workflow only continues when both layers are available.
What this means in practice
- A user may be blocked even if one quota layer still has room
- Upgrade messaging should explain which layer failed
- Legacy standalone credit assumptions should not be reused
- Some current API-backed CLI responses may still include a legacy
creditscompatibility field - Treat
noxinfluencer quotaand the quota response data as the canonical Skill quota snapshot - Remote MCP read tools use the same quota accounting model as the matching API-backed read tools
Old assumptions to stop reusing
- The old standalone API product credit model
- The idea that only one quota layer matters
- Legacy prototype pricing or call-cost wording
