Choose the provider
Review capability, terms and the task’s requirements.
CAPABILITY · ACCEPTANCE REQUIRED
Model routing
Choose an approved provider protocol, context and usage boundary.
Define the scope first.
- An authorised provider and model
- Selected task context and data-handling terms
- Explicit usage limits and accepted error/revocation behavior
Bound execution
Keep credentials server-side and agree the permitted usage.
Verify a real result
Protocol fixtures are not provider acceptance.
Keep this boundary visible.
A configured key is not proof that a model works safely or within an agreed spend boundary.
See the related workflow ↗