For Agents
Manage PlanetScale serverless MySQL databases including branching, schema migrations, backups, deploy requests, and organization settings.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PlanetScale API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with PlanetScale API.
Create and manage database branches for development, staging, and production environments
Execute deploy requests to apply schema changes with automatic conflict detection
Configure backup policies with retention periods and automated schedules
GET STARTED
Use for: Create a new database branch for testing schema changes, Deploy schema migration from development branch to production, Generate a new database password for application connection, List all deploy requests pending review for a database
Not supported: Provides database lifecycle management and schema migration orchestration. Does not execute queries against database branches—use MySQL connection strings for application data access. Does not provide query optimization or index tuning—use PlanetScale Insights dashboard.
PlanetScale is a serverless MySQL platform built on Vitess, the horizontal scaling system that powers YouTube and Slack. The PlanetScale API provides comprehensive control over database lifecycle management, branching workflows, backup policies, deployment requests, and organization administration. Developers use it to automate database provisioning in CI/CD pipelines, implement schema change workflows with branch-based development, manage connection credentials programmatically, and monitor query performance through insights endpoints. The API supports multi-region deployments, automatic sharding, and zero-downtime schema migrations. It enables infrastructure-as-code patterns for database management, allowing teams to version database schemas alongside application code and execute deploy requests that safely apply changes to production branches.
Manage database passwords and connection strings programmatically
Monitor query insights including slow queries and connection pool metrics
Administer organization members, teams, and service tokens with role-based access control
Configure regional database deployments and cluster sizing for performance tuning
Patterns agents use PlanetScale API for, with concrete tasks.
★ Branch-Based Schema Development Workflow
Development teams use PlanetScale's branching model to develop database schema changes in isolation, similar to Git workflows. The API allows creating feature branches from production, applying migrations to the branch, running integration tests against the branch database, and then submitting a deploy request. Automated CI pipelines use the API to create ephemeral branches for each pull request, enabling schema change review and testing before merging to production. This eliminates the risk of breaking changes and enables true database versioning alongside application code.
Create a new PlanetScale branch from production, apply schema migration SQL to the branch, wait for safe migrations to complete, create a deploy request to merge changes back to production.
Automated Infrastructure Provisioning
Platform engineering teams use the API to provision databases as part of application deployment workflows. Terraform providers and custom automation tools call the API to create databases, configure cluster sizes for expected load, set up backup policies, generate connection credentials, and inject them into application environments. This enables self-service database provisioning for developers while maintaining governance through organization-level policies. Each microservice or tenant can receive its own isolated database with standardized configuration.
Create a new database in PlanetScale organization, configure cluster size for production workload, create initial main branch, generate connection password, and return connection string for application configuration.
Zero-Downtime Schema Migration Orchestration
SRE teams orchestrate complex schema migrations using deploy requests that PlanetScale executes with zero downtime. The API enables creating a deploy request between branches, monitoring its status as PlanetScale validates the migration safety, and tracking the deployment progress. For changes PlanetScale cannot safely auto-deploy (like dropping columns with data), the API provides deployment instructions and allows manual approval workflows. This reduces risk for high-traffic databases where traditional migration tools cause seconds or minutes of downtime.
Create deploy request to merge schema changes from staging branch to production, poll deploy request status, check for migration warnings, and monitor deployment progress until schema change is live.
Database Backup and Disaster Recovery Automation
Infrastructure teams use the API to manage backup policies ensuring compliance with RTO/RPO requirements. The API configures automated backup schedules, sets retention periods based on regulatory needs, and provides endpoints to list available backup snapshots. In disaster scenarios, the API allows restoring databases from specific backup points, creating new branches from backup snapshots for forensic analysis, and auditing backup history. This enables automated disaster recovery runbooks that can restore service with minimal manual intervention.
Configure backup policy for production database with 30-day retention, verify automated backups are running on schedule, list available backup snapshots, and test restore process by creating new branch from backup.
106 endpoints — planetscale is a serverless mysql platform built on vitess, the horizontal scaling system that powers youtube and slack.
METHOD
PATH
DESCRIPTION
/organizations/{organization}/databases
Create a new database
/organizations/{organization}/databases/{database}/branches
List branches for a database
/organizations/{organization}/databases/{database}/branches/{branch}/deploy-requests
Create a deploy request to merge schema changes
/organizations/{organization}/databases/{database}/branches/{branch}/passwords
List passwords for a database branch
/organizations/{organization}/databases/{database}/branches/{branch}/passwords
Create a new database password
/organizations/{organization}/databases
Create a new database
/organizations/{organization}/databases/{database}/branches
List branches for a database
/organizations/{organization}/databases/{database}/branches/{branch}/deploy-requests
Create a deploy request to merge schema changes
/organizations/{organization}/databases/{database}/branches/{branch}/passwords
List passwords for a database branch
/organizations/{organization}/databases/{database}/branches/{branch}/passwords
Create a new database password
Three things that make agents converge on Jentic-routed access.
Credential isolation
PlanetScale OAuth service tokens are encrypted in Jentic's vault with organization or database scope. Agents execute operations without seeing tokens, and all API calls are audit-logged with the requesting agent identity.
Intent-based discovery
Agents search by intent like 'create a database branch for schema testing' and Jentic returns the relevant branch creation and deploy request operations with parameter schemas, avoiding the need to navigate PlanetScale's 106 endpoints.
Time to first call
Direct PlanetScale integration: 2-3 days to understand branching model, deploy request lifecycle, and error handling for migrations. Through Jentic: 30 minutes—search for operations, execute with natural language parameters, monitor deploy request status.
Alternatives and complements available in the Jentic catalogue.
Vitess API
Vitess is the open-source horizontal scaling system that PlanetScale is built on.
Use Vitess directly when you need self-hosted MySQL sharding with full control over cluster topology and custom plugins.
Specific to using PlanetScale API through Jentic.
What authentication does the PlanetScale API use?
The PlanetScale API uses OAuth 2.0 service tokens for authentication. You generate service tokens in the PlanetScale dashboard with organization or database-level permissions, then pass the token in the Authorization header as a Bearer token.
How does PlanetScale branching differ from traditional database environments?
PlanetScale branches are isolated database instances that share the same schema lineage. Unlike traditional staging databases that drift from production, branches track schema changes and enable merge-based deployments with conflict detection, similar to Git workflows.
What is a deploy request in PlanetScale?
A deploy request is a schema migration proposal that merges changes from one branch to another. PlanetScale analyzes the migration for safety, executes it with zero downtime when possible, and provides manual deployment instructions for changes requiring careful coordination.
Can I automate database provisioning in CI/CD with the PlanetScale API?
Yes. The API provides full lifecycle management including database creation, branch provisioning, password generation, and connection string retrieval. Many teams use it with Terraform, GitHub Actions, or custom automation to provision databases per pull request or environment.
How do AI agents use the PlanetScale API through Jentic?
Agents search Jentic for tasks like 'create a database branch for testing' and receive the PlanetScale API operation schemas. Jentic vaults the service token and handles authentication, allowing agents to execute branching, migration, and provisioning workflows with natural language parameters.