Baseten management API

Name: Baseten management API API
Brand: Baseten management API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLMl InferenceapiKey19 EndpointsREST

For Agents

Manage Baseten model deployments — promote development to production, tune autoscaling, activate or deactivate deployments, and rotate inference secrets. Useful for MLOps automation agents.

Quickstart

Get started with Baseten management API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"promote a baseten deployment to production"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Baseten management API API.

List all models in a Baseten workspace and inspect their deployments

Promote a development deployment to production with POST /v1/models/{id}/deployments/development/promote

Update autoscaling settings on a deployment via PATCH on its autoscaling_settings endpoint

Activate or deactivate a deployment to control inference availability and cost

GET STARTED

Start building with Baseten management API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Baseten management API, keeping it validated and agent-ready.

Baseten is a platform for deploying and serving machine learning models at production scale, and the management API exposes the control-plane operations that sit behind its UI. The API covers model and deployment lookup, autoscaling configuration, deployment promotion between development and production, activation and deactivation, and management of secrets used by deployed models. It is the integration surface for MLOps pipelines that need to roll out new model versions, tune capacity, or rotate credentials without clicking through the dashboard.

Use Cases

Patterns agents use Baseten management API API for, with concrete tasks.

★ Promote Model from Development to Production

After validating a new model version on the development deployment, an MLOps pipeline needs to flip the production deployment to the new version. The Baseten API exposes POST /v1/models/{model_id}/deployments/development/promote to perform this atomically. Promotion typically completes within seconds and can be wired into CI gates that require eval scores above a threshold.

Call POST /v1/models/mdl-123/deployments/development/promote after CI evals pass and verify the production deployment via GET /v1/models/mdl-123/deployments/production

Cost-Aware Autoscaling Tuning

Production ML deployments often run on GPUs with steep idle costs. Operators can call PATCH /v1/models/{model_id}/deployments/production/autoscaling_settings to tighten min/max replicas, scale-down delay, and concurrency targets — or deactivate the deployment overnight via the deactivate endpoint. The flow lets agents apply policy changes without redeploying the model.

Call PATCH /v1/models/mdl-123/deployments/production/autoscaling_settings with min_replicas=0 and scale_down_delay=120 to enable scale-to-zero off-hours

Model Inventory and Audit

Platform teams running multi-team Baseten workspaces need an inventory of every model and its deployments for cost attribution and security review. GET /v1/models lists every model and GET /v1/models/{model_id}/deployments returns its deployments, so an agent can build a report of active production deployments, their replica counts, and which secrets they reference.

Call GET /v1/models, iterate each model with GET /v1/models/{model_id}/deployments, and post a summary of production deployments to the platform-ops channel

Secret Rotation for Deployed Models

Deployed models often call third-party APIs (OpenAI, Anthropic, vector DBs) that require keys. The /v1/secrets endpoints let an automation agent list current secrets and create rotated values when a key is revoked. The agent can then verify the deployment picks up the new value via the deployment-detail endpoint.

Call POST /v1/secrets with the new key value, then verify the production deployment uses it via GET /v1/models/{model_id}/deployments/production

Agent-Driven Deployment Operations via Jentic

An incident-response agent can use Baseten through Jentic to take corrective actions like deactivating a misbehaving deployment or rolling back to the development version. Jentic isolates the Baseten API key and exposes the 19 management operations as discoverable tools indexed by natural-language intent.

Search Jentic for 'deactivate a baseten deployment', load the POST /v1/models/{model_id}/deployments/{deployment_id}/deactivate schema, and execute against the offending deployment

Key Endpoints

19 endpoints — baseten is a platform for deploying and serving machine learning models at production scale, and the management api exposes the control-plane operations that sit behind its ui.

METHOD

PATH

DESCRIPTION

GET

/v1/models

List all models in the workspace

GET

/v1/models/{model_id}/deployments

List deployments for a model

POST

/v1/models/{model_id}/deployments/development/promote

Promote development deployment to production

PATCH

/v1/models/{model_id}/deployments/production/autoscaling_settings

Update production autoscaling configuration

POST

/v1/models/{model_id}/deployments/{deployment_id}/deactivate

Deactivate a deployment

GET

/v1/secrets

List secrets available to deployed models

POST

/v1/secrets

Create a new secret

GET

/v1/models

List all models in the workspace

GET

/v1/models/{model_id}/deployments

List deployments for a model

POST

/v1/models/{model_id}/deployments/development/promote

Promote development deployment to production

PATCH

/v1/models/{model_id}/deployments/production/autoscaling_settings

Update production autoscaling configuration

POST

/v1/models/{model_id}/deployments/{deployment_id}/deactivate

Deactivate a deployment

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Baseten API key is stored encrypted in the Jentic vault. Agents receive scoped access tokens, so the raw key never enters the agent's context when calling control-plane endpoints like POST /v1/models/{model_id}/deployments/development/promote.

Intent-based discovery

Agents search by intent (e.g. 'promote a baseten deployment' or 'update autoscaling') and Jentic returns matching Baseten operations with their input schemas and required parameters.

Time to first call

Direct Baseten integration: half a day to wire auth, error handling, and the promote/deactivate flow. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Illumina BaseSpace API

Genomics data platform — pair with Baseten when serving ML models trained on sequencing data

Use BaseSpace to fetch sequencing inputs; use Baseten to serve the model that processes them.

Complementary

Basesnap API

Database snapshot service — back up the application database backing a Baseten-deployed service

Use Basesnap for state database backups; use Baseten for the model-serving layer.

Alternative

Battle.net API

Unrelated domain; included as placeholder since no direct Baseten competitor exists in the corpus

Not a real alternative — listed only because the corpus does not currently include a competing model-serving API.

FAQs

Specific to using Baseten management API API through Jentic.

What authentication does the Baseten management API use?

Baseten uses an API key (ApiKeyAuth) passed as an authorization header. Through Jentic, the key is stored encrypted in the vault and the agent only receives a scoped token when calling endpoints like POST /v1/models/{model_id}/deployments/development/promote.

Can I promote a model deployment to production with the Baseten API?

Yes. Call POST /v1/models/{model_id}/deployments/development/promote to atomically promote the current development deployment to production. The previous production deployment is replaced and traffic shifts to the promoted version.

How do I update autoscaling for a production deployment through Jentic?

Search Jentic for 'update baseten autoscaling settings', which surfaces PATCH /v1/models/{model_id}/deployments/production/autoscaling_settings. Load the schema, set min_replicas, max_replicas, and scale_down_delay, and execute.

What are the rate limits for the Baseten management API?

The OpenAPI spec does not declare explicit rate limits for the management API. Treat it as a control plane — high-frequency calls to PATCH autoscaling or promote endpoints are unusual; check the Baseten dashboard for any account-level quotas.

Can I list all models in my Baseten workspace?

Yes. GET /v1/models returns every model in the workspace, and GET /v1/models/{model_id} fetches a specific model's metadata. Combine with GET /v1/models/{model_id}/deployments to enumerate every deployment under each model.

Does the Baseten API let me manage secrets used by deployed models?

Yes. GET /v1/secrets lists existing secrets and POST /v1/secrets creates a new one. Secrets are referenced by name in your deployment configuration, so rotating a value is a matter of POSTing the new secret and redeploying or letting the next deployment pick it up.