Allow T3 Chat subscription to power external coding agents (or usage-based API access)

I’d like my T3 Chat subscription’s usage/message limits to apply when using external coding agents (Claude Code, Codex, T3 Code, etc.) not a separate BYOK key with its own billing.

Right now, using any coding agent outside the T3 Chat web UI means bringing a separate API key billed independently by the provider, even though I’m already paying for a T3 Chat subscription. I’d like my existing subscription quota to be the single source of usage, whether I’m chatting in the browser or running a coding agent locally.

Would love to see T3 Chat expose an API endpoint or agent-compatible interface that draws directly from the same subscription limits, rather than requiring a second, separate billing relationship with a model provider.