canonical: https://jentic.com/apis/databasus.com/databasus

# Databasus API

Jentic publishes the only available OpenAPI specification for Databasus API, keeping it validated and agent-ready. Databasus is a managed cloud database service exposing provisioning, monitoring, backup management, and SQL query execution through a single REST API. The 11-endpoint surface covers database lifecycle (list, create, get, update, delete), metrics, backups (list, create, restore), SQL execution, and account info. Authentication uses bearer tokens against the https://api.databasus.com/v1 base URL.

## For AI agents

Provision and manage hosted databases, run SQL queries, retrieve metrics, and orchestrate backup and restore operations on Databasus.

## Scope

Does not handle authentication services, object storage, or message queueing - use for managed database lifecycle, backups, metrics, and SQL execution on Databasus only.

## Capabilities

- Provision new managed database instances and update their settings
- List, retrieve, and delete existing databases owned by the account
- Pull database performance metrics for monitoring and alerting
- Create on-demand backups and restore a database from a previous backup
- Execute SQL queries against a database through a structured endpoint
- Read account information including plan and quota details

## Use cases

### Programmatic Database Provisioning

Provision and tear down Databasus databases as part of an environment lifecycle, for example creating a per-tenant database when a customer signs up. POST /databases creates the instance, PATCH `/databases/{databaseId}` updates settings, and DELETE `/databases/{databaseId}` removes it. Suitable for SaaS platforms and internal tooling that need on-demand database creation.

Example prompt: Call POST /databases with engine and region parameters to provision a new database, then PATCH `/databases/{databaseId}` to apply the connection-pool size.

### Backup and Disaster Recovery Automation

Automate scheduled backups and recovery drills against Databasus instances. POST `/databases/{databaseId}/backups` creates a backup, GET lists existing backups, and POST `/databases/{databaseId}/backups/{backupId}/restore` restores from a chosen backup. Suitable for ops teams running regular DR exercises and compliance-driven backup schedules.

Example prompt: Create a backup of database 'prod-orders' via POST `/databases/{databaseId}/backups`, wait for completion, and run a restore against a staging database to verify backup integrity.

### Database Monitoring Dashboard

Power an internal monitoring dashboard with Databasus metrics rather than running a separate metrics agent. GET `/databases/{databaseId}/metrics` returns performance data for a database that can be plotted alongside application-level metrics. Useful for platform teams consolidating database health into existing observability stacks.

Example prompt: Pull metrics for each production database via GET `/databases/{databaseId}/metrics` every minute and forward them to the team's metrics pipeline.

### AI Agents Running Read-Only SQL via Jentic

AI agents that answer business questions over operational data can execute scoped SQL against Databasus through Jentic without holding the bearer token. The agent searches Jentic for the relevant intent, loads the schema, and runs the query with credentials held in Jentic's vault. POST `/databases/{databaseId}/query` is the execution surface used here. Pair with read-only database users to keep agent access bounded.

Example prompt: Use Jentic to search 'run a sql query on databasus', load POST `/databases/{databaseId}/query`, and execute a SELECT against the orders database to answer a user's revenue question.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/databases` | List databases owned by the account |
| POST | `/databases` | Provision a new database |
| GET | `/databases/{databaseId}` | Get details for a database |
| PATCH | `/databases/{databaseId}` | Update database settings |
| DELETE | `/databases/{databaseId}` | Delete a database |
| GET | `/databases/{databaseId}/metrics` | Get database performance metrics |
| POST | `/databases/{databaseId}/backups` | Create an on-demand backup |
| POST | `/databases/{databaseId}/query` | Execute a SQL query |

## Key resources

- **Databases** — Provision, list, update, and delete managed databases
- **Backups** — Create, list, and restore database backups
- **Monitoring** — Retrieve performance metrics per database
- **Query** — Execute SQL queries against a database
- **Account** — Read account information and quotas

## Why Jentic

- **Setup:** Wiring Databasus by hand means learning its bearer auth against api.databasus.com/v1 and building the lifecycle, backup, and retry plumbing for managed databases yourself. Through Jentic you install once, import the Databasus API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Databasus puts the database id in the URL path (`/databases/{databaseId}/...`), so a rule can pin your agent to one database for reading metrics, running a query, or taking a backup. You choose the operations it may call, so deleting a database is not included unless you add it.
- **Credential handling:** Your Databasus bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'provision a Databasus database' or 'run a SQL query', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the api.databasus.com docs.

## Related APIs

- **Supabase API** — Supabase exposes a managed Postgres database with auth and storage; Databasus focuses on the database lifecycle.
- **PlanetScale API** — PlanetScale provides managed MySQL with branching; Databasus provides a generalised managed database lifecycle.
- **MongoDB Atlas API** — MongoDB Atlas hosts managed MongoDB clusters; Databasus targets relational managed databases.
- **DigitalOcean API** — DigitalOcean provisions surrounding compute and networking; Databasus provisions the managed database itself.

## FAQ

### Why is there no official OpenAPI spec for Databasus API?

Databasus does not publish an OpenAPI specification through its developer site. Jentic generates and maintains this spec so that AI agents and developers can call Databasus API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Databasus API use?

The Databasus API uses bearer token authentication via the BearerAuth scheme - the token is sent in the Authorization header. Through Jentic the bearer token sits in the vault and never enters the agent's context.

### Can I run a SQL query through the Databasus API?

Yes. POST `/databases/{databaseId}/query` accepts a SQL statement and returns the result rows. Pair with a read-only database user when exposing this endpoint to agents.

### What are the rate limits for the Databasus API?

The OpenAPI spec does not declare explicit numeric limits. Apply exponential backoff on 429 responses and avoid running tight provisioning or backup loops against POST /databases or POST `/databases/{databaseId}/backups.`

### How do I provision a database through Jentic?

Run pip install jentic, then search Jentic for 'provision a databasus database', load the POST /databases schema, and execute it with the engine, region, and plan parameters. Jentic injects the bearer token at call time.

### Does the Databasus API support backup and restore?

Yes. POST `/databases/{databaseId}/backups` creates a backup, GET `/databases/{databaseId}/backups` lists existing backups, and POST `/databases/{databaseId}/backups/{backupId}/restore` restores the database from a chosen backup.

### Can I limit what my agent is allowed to do with the Databasus API?

Yes. Because you run Jentic One yourself, your own rules decide which Databasus operations and credentials the agent may use. Since Databasus puts the database id in the URL path (`/databases/{databaseId}/...`), you can pin the agent to a single database and to specific operations, such as reading metrics via GET `/databases/{databaseId}/metrics`, running a query via POST `/databases/{databaseId}/query`, or taking a backup via POST `/databases/{databaseId}/backups.` Destructive calls like DELETE `/databases/{databaseId}` are excluded unless you explicitly grant them.