Databasus API

Name: Databasus API
Brand: Databasus API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasebearer11 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Databasus API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Databasus 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 | sh

Step 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 instance

Jentic 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.

Capabilities

What an agent can do with Databasus API.

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

GET STARTED

Start building with Databasus API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Databasus API for, with concrete tasks.

★ 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.

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.

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.

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.

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

11 endpoints — jentic publishes the only available openapi specification for databasus api, keeping it validated and agent-ready.

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

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

Why Jentic?

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

Credential isolation

Databasus bearer tokens sit encrypted in the Jentic vault. Agents receive scoped access for each call and the raw Authorization value never enters the agent's context — important when SQL execution is exposed to an agent.

Intent-based discovery

Agents search by intent (e.g. 'provision a databasus database') and Jentic returns the matching POST /databases operation with its input schema, so the agent calls the right endpoint without browsing api.databasus.com docs.

Time to first call

Direct Databasus integration: 1-2 days for auth, lifecycle endpoints, and backup orchestration. Through Jentic: under 1 hour to call all 11 operations.

FAQs

Specific to using Databasus API through Jentic.

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 at https://app.jentic.com/sign-up.

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.

Databasus API

Connect the Databasus API to your agent

Capabilities

Start building with Databasus API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs