Basesnap API
★ Only Publicly Available OpenAPI DocumentStorageBackup RecoveryapiKey3 EndpointsREST
For Agents
Create database snapshots, list existing snapshots, and trigger restores from a chosen snapshot ID. Useful for agents running pre-deploy backups or recovery flows.
Use for: I need to take a snapshot of my production database before a migration, List all snapshots created in the last week, Restore the database from snapshot abc-123, Check whether yesterday's nightly snapshot was created successfully
Not supported: Does not handle application-level data export, schema migrations, or per-row backups — use for full database snapshot and restore operations only.
Jentic publishes the only available OpenAPI specification for Basesnap API, keeping it validated and agent-ready. Basesnap is a database snapshot and backup service that lets teams capture point-in-time copies of their databases and roll back to any prior snapshot on demand. The API exposes three core operations covering snapshot listing, snapshot creation, and snapshot restoration, all secured by an API key passed in the Authorization header. It is suitable for ops teams that want programmatic disaster-recovery automation rather than relying on manual database tooling.
Install Jentic One Beta
Connect the Basesnap API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Basesnap 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.
1
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 | sh2
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 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.
Capabilities
What an agent can do with Basesnap API.
Capture a point-in-time database snapshot before risky migrations or deploys
List all available snapshots with their creation timestamps and identifiers
Restore a database to a chosen snapshot using its snapshot ID
Automate pre-release backup checkpoints from CI/CD pipelines
Trigger disaster-recovery rollbacks from incident-response runbooks
Use Cases
Patterns agents use Basesnap API for, with concrete tasks.
★ Pre-Deploy Database Checkpoint
Capture a database snapshot immediately before a release or schema migration so the team can roll back in seconds if something breaks. The Basesnap API exposes a single POST /snapshots call that returns a snapshot identifier, which the deployment pipeline can store and reference. Snapshot creation runs asynchronously and is suitable for production-sized databases.
Call POST /snapshots to create a snapshot named pre-deploy-2026-06-10 and store the returned snapshot ID for rollback
Incident Recovery Rollback
When a deploy or data corruption incident occurs, an on-call engineer or runbook agent needs to identify the most recent good snapshot and restore the database. Basesnap's GET /snapshots returns the snapshot list and POST /snapshots/{id}/restore triggers the restore. End-to-end rollback typically completes within minutes for moderate database sizes.
List snapshots via GET /snapshots, pick the latest snapshot before the incident timestamp, then call POST /snapshots/{id}/restore
Scheduled Backup Audit
Compliance and SRE teams need to verify that scheduled snapshots are actually being created and retained. The GET /snapshots endpoint returns the full snapshot list with timestamps, so an agent can audit retention policies and alert if expected snapshots are missing.
Call GET /snapshots and verify a snapshot exists for each of the last 7 daily backup windows
Agent-Driven Recovery via Jentic
AI agents handling on-call escalation can use Basesnap through Jentic to perform a full identify-and-restore loop without operator intervention. Jentic isolates the Basesnap API key in its vault and exposes the three snapshot operations as discoverable tools, so the agent can search for restore intent, load the schema, and execute.
Search Jentic for 'restore a database snapshot', load the POST /snapshots/{id}/restore schema, and execute with the chosen snapshot ID
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for basesnap api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/snapshots
List all database snapshots
POST
/snapshots
Create a new database snapshot
POST
/snapshots/{id}/restore
Restore the database from a snapshot
GET
/snapshots
List all database snapshots
POST
/snapshots
Create a new database snapshot
POST
/snapshots/{id}/restore
Restore the database from a snapshot
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Basesnap API key (Authorization header) is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw key never enters the agent's context, even when calling POST /snapshots/{id}/restore.
Intent-based discovery
Agents search by intent (e.g. 'create a database snapshot' or 'restore a database') and Jentic returns matching Basesnap operations with their input schemas, so the agent calls the right endpoint without browsing docs.
Time to first call
Direct Basesnap integration: half a day for auth setup, error handling, and rollback logic. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Basesnap API through Jentic.
Why is there no official OpenAPI spec for Basesnap API?
Basesnap does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Basesnap 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 Basesnap API use?
Basesnap uses an API key passed in the Authorization header. Through Jentic, the key is stored encrypted in the vault and never enters the agent's context — the agent receives a scoped token to call POST /snapshots and the other two endpoints.
Can I create a database snapshot with the Basesnap API?
Yes. Call POST /snapshots to create a new snapshot. The response returns a snapshot identifier you can later pass to POST /snapshots/{id}/restore to roll the database back to that point in time.
How do I restore a database from a snapshot through Jentic?
Search Jentic for 'restore a database snapshot', which surfaces the POST /snapshots/{id}/restore operation. Load the schema, supply the target snapshot ID, and execute. The full search-load-execute loop runs from a single Jentic SDK session.
What are the rate limits for the Basesnap API?
The OpenAPI spec does not declare explicit rate limits. Treat snapshot creation as a heavyweight operation and avoid running concurrent POST /snapshots calls against the same database — check Basesnap's account dashboard for current quotas.
Is the Basesnap API free?
Basesnap is a commercial service and pricing is set per account. The API itself does not expose billing endpoints, so check your Basesnap account for current plan limits before automating high-frequency snapshot creation.
GET STARTED