vs AI model providers
AI providers expose hosted models through APIs and SDKs. The application selects a provider, model, request format, retry policy, and any agent framework built around the response. Provider-native products may also include tools, files, batch processing, evaluations, or managed agent features.
Redgold exposes OpenAI- and Anthropic-compatible request formats backed by Redgold models. It connects model access to metering, provider routing, persistent coding-agent workspaces, repository tools, application data, automated review, and deployment. Clients discover the models available to their account through /v1/models rather than binding the application to an upstream provider identifier.
Criteria
| Criterion | Redgold | Direct AI provider API |
|---|---|---|
| API contract | OpenAI-compatible Chat Completions and Responses plus Anthropic-compatible Messages (model API) | Provider-native endpoints, SDKs, and model identifiers |
| Model selection | Account-scoped model discovery with model routing | Models published by that provider |
| Provider handling | Model API authentication, usage metering, retry, and backend availability | The application integrates provider behavior directly |
| Agent runtime | Persistent isolated coding workspaces with repository and cluster tools (AI agents) | Varies by provider; model access is the common surface |
| Operational record | Conversation, tool-call, token, latency, and cost metadata stored by the platform | Provider usage records plus whatever the application persists |
| Data and deployment | Agents can work against platform datasets and the same GitOps application path | Supplied by the application owner |
| Compatibility boundary | Compatible wire formats; model behavior and supported fields remain Redgold-specific | Native behavior and full provider feature surface |
Redgold scope
A direct provider API ends at model access. Redgold carries that request into an operated agent lifecycle: workspace provisioning, tools, budgets, provider routing, stored run history, code review, and deployment. The model API also remains usable independently through standard client request shapes.