Side-by-side comparison
Choose a model gateway when
A model gateway is usually sufficient when:- The application primarily generates or analyzes content.
- External facts are already supplied by the application.
- The team has separate tool and data integrations.
- The workflow does not need reusable cross-tool Skills.
Choose a broader capability layer when
A broader layer is useful when:- The agent must retrieve current information before answering.
- Several data providers would otherwise require separate integrations.
- Multiple agent clients should share the same task instructions.
- The agent needs machine-readable discovery of available capabilities.
- The workflow may include controlled writes or billable runtime purchases.
They are not mutually exclusive
The model gateway is a capability inside the broader layer. An application can begin with model inference and add APIs or Skills only when a real workflow needs them. This incremental approach avoids unnecessary orchestration:- Use a model for reasoning or generation.
- Add a direct API when current external data is required.
- Package repeated orchestration as a Skill.
- Add authenticated actions only when side effects are necessary.
- Add programmatic payment controls only for runtime purchasing requirements.
Evaluation questions
Before choosing an architecture, ask:- Does the application need one model provider, several models, or models plus external data?
- Who should own endpoint sequencing: the application or a reusable Skill?
- Are any operations writes rather than reads?
- Does the agent need to discover capabilities dynamically?
- What budget, retry, and audit rules apply?