Model choice is a business decision
Capability matters, but so do cost, data handling, regional requirements, latency, and existing agreements. Different workflows may justify different providers. A model connection should make those choices explicit, with an owner and an approved purpose.
Bring your own token, clearly defined
In Entergenie’s model, bringing your own token means supplying your own provider API credential through a secure configuration process. It does not mean putting a key in a prompt. The provider charges your account for model consumption, while platform costs are agreed separately.
Replaceable does not mean interchangeable
A shared API shape cannot guarantee equivalent tool behavior, output quality, data handling, or cost. Replacing a model still needs representative evaluation. Switching to a fallback provider also changes where data goes, so fallback routing should be an approved configuration choice.
Keep the workflow anchored in your business
Tasks, ownership, acceptance criteria, tool contracts, and policy should not need to be reinvented every time a better model appears. Use portable formats and standard interfaces where they earn their keep. Avoid building elaborate abstractions before the real requirements are understood.