Skip to main content
TrueFoundry allows you to connect and use models from providers like OpenAI, Anthropic, AWS Bedrock, Google Vertex AI, and many other providers from a single place. Once added, these models can be used in TrueFoundry AI Gateway and your applications. The models are saved as provider integrations in TrueFoundry. The group of models are saved as a provider account. You can add multiple models to a single provider account; the models in the same provider account are called integrations.
Replace YOUR_CONTROL_PLANE_URL with your actual TrueFoundry control plane URL and YOUR_API_KEY with your API key throughout this guide.

Add Models

API Overview

Here is the curl command example to add a model as a provider account:

Request Schema

The Apply API accepts a TrueFoundryApplyRequest object with the following structure:
ModelProviderAccount | ModelManifest | ArtifactManifest | Service | ...
required
The manifest object defining the resource to be created or updated. For model provider accounts, this should be a ModelProviderAccount object.
boolean
default:"false"
When set to true, performs a dry run without actually creating or updating the resource. Useful for validation.

ModelProviderAccount Schema

For creating model provider accounts, the manifest should be a ModelProviderAccount object. This is a union type that can be one of any of the following provider account types: Supported Provider Account Types: Common Fields for All Provider Accounts:
string
required
The provider account type (e.g., “provider-account/openai”, “provider-account/anthropic”, etc.)
string
required
Name of the provider account. Must be 3-32 characters, lowercase alphanumeric with hyphens, cannot start with a number.
object
required
Authentication data specific to the provider (API keys, credentials, etc.)
array
required
List of model integrations available through this provider account
array
Optional list of users who have access to this provider account

Response Schema

Response Fields

string
Unique identifier for the provider account.
string
Name of the provider account.
string
Fully qualified name of the provider account (tenant/provider/name).
string
The provider type (e.g., “openai”, “anthropic”, “aws-bedrock”).
object
The provider account manifest that was applied, excluding integrations.
array
List of provider integrations (models) associated with this account.
object
Information about the user who created the provider account.
string
Timestamp when the provider account was created.
string
Timestamp when the provider account was last updated.
string
The action performed: “CREATE” for new resources, “UPDATE” for existing ones.

Examples

Error Handling

The Apply API may return various error responses. Common scenarios include:
  • 400 Bad Request: Invalid manifest structure or missing required fields
  • 401 Unauthorized: Invalid or missing API key
  • 403 Forbidden: Insufficient permissions for the operation
  • 404 Not Found: Provider account not found
  • 409 Conflict: Provider account with the same name already exists
  • 422 Unprocessable Entity: Invalid provider credentials or configuration

List Models

You can list and retrieve model integrations using the List Provider Integrations API. This allows you to query existing model integrations with filtering and pagination support.

API Overview

Here is the curl command example to list model integrations:

Query Parameters

string
default:"model"
Filter integrations by type. For models, use model.
string
Filter by fully qualified name (FQN) of a specific integration. Cannot be used with id.
string
Filter by integration ID. Cannot be used with fqn.
number
default:"0"
Pagination offset - number of items to skip.
number
Maximum number of items to return. If not specified, returns all items.

Response Schema

Response Fields

array
Array of model integration objects.
object
Pagination metadata.

Examples

Error Handling

The List API may return various error responses. Common scenarios include:
  • 400 Bad Request: Invalid query parameters (e.g., both fqn and id provided)
  • 401 Unauthorized: Invalid or missing API key
  • 404 Not Found: Integration with specified id or fqn not found