GitHub user richardchen874-sys added a comment to the discussion: AI Integration Discussion: Netbeans MCP for claude code
The part that stands out to me is "AI Integration Discussion: Netbeans MCP for claude code". That is usually where usage and cost visibility starts to matter in practice, because the integration works at small scale but gets harder once real users, retries, and longer sessions show up. I would track provider, model, prompt/output tokens, latency, retry count, and the feature or workflow that triggered the call, so cost can be optimized by task instead of guessed from monthly totals. I am testing an OpenAI-compatible multi-model API layer around official Chinese models, so this kind of usage and cost visibility is directly relevant. For netbeans, is the bigger need exact billing-grade cost, or operational usage signals good enough for routing decisions? GitHub link: https://github.com/apache/netbeans/discussions/8634#discussioncomment-17618136 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
