Install Jentic One Beta

Connect the Layerbase Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Layerbase Cloud 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Flayerbase.com%2Flayerbase" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Flayerbase.com%2Flayerbase" | 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 Layerbase Cloud API.

Provision a database on an engine from the public registry, with optional backupPolicy, storageBlocks, and keepAlive

Spin up a transient database with ttlHours that is destroyed outright at expiry, suited to CI test runs

Run a SQL query over HTTP against a database by id and read back columns, rows, and rowCount

List the engines and versions available to provision before creating a database

GET STARTED

Start building with Layerbase Cloud API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Layerbase Cloud API for, with concrete tasks.

★ Agent-run database queries through Jentic

An AI agent that answers questions about application data can call the Layerbase query operation with a SQL string and read the columns and rows straight from the JSON response, without installing a database driver. Through Jentic the agent finds the operation by intent, the bearer key is injected at execution time, and a rule can hold the agent to querying one database id.

Call POST /v1/databases/{id}/query with the reporting database id and query 'SELECT status, count(*) FROM orders GROUP BY status', then summarise the returned rows

Ephemeral databases for CI pipelines

Integration tests need a clean database per run and nothing left behind afterwards. Layerbase provisions a database from an engine name in one call, and setting ttlHours between 1 and 72 makes it transient: an expiry is stamped and the database is destroyed with no final backup, so stale test databases do not pile up.

Call POST /v1/databases with engine 'postgresql', name 'ci-run-1842', and ttlHours 2, then poll GET /v1/databases/{id} until it is ready

Least-privilege keys for each service

Rather than sharing one account-wide key, teams can create a key per service with scopeType set to 'database' and scopeId naming the database it may touch, plus a ttlSeconds expiry so it ages out. Keys are rotated or revoked by id when a deploy changes or a service is retired.

Call POST /v1/api-keys with name 'billing-worker', scopeType 'database', scopeId set to the billing database id, and ttlSeconds 86400

Serverless and edge data access

Serverless functions and edge runtimes often cannot hold open database sockets. The Layerbase query operation accepts a query over HTTPS and wakes a hibernated database automatically, returning a 503 with retry_after while it starts, so a function can retry and then read results as JSON.

Call POST /v1/databases/{id}/query with query 'SELECT 1', and if the response is 503 wait for retry_after before calling again

Key Endpoints

11 endpoints — the layerbase cloud api provisions managed databases and runs queries against them over plain https, with no driver or open socket required.

METHOD

PATH

DESCRIPTION

POST

/v1/databases

Provision a database

GET

/v1/databases

List your databases

POST

/v1/databases/{id}/query

Run a query over HTTP

GET

/v1/engines

List available engines

POST

/v1/api-keys

Create an API key

POST

/v1/api-keys/{id}/rotate

Rotate an API key

DELETE

/v1/api-keys/{id}

Revoke an API key

POST

/v1/databases

Provision a database

GET

/v1/databases

List your databases

POST

/v1/databases/{id}/query

Run a query over HTTP

GET

/v1/engines

List available engines

POST

/v1/api-keys

Create an API key

POST

/v1/api-keys/{id}/rotate

Rotate an API key

DELETE

/v1/api-keys/{id}

Revoke an API key

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Layerbase by hand means managing a bearer key, overriding the server URL with the host from each database's Connect panel, and handling 503 retry_after responses while hibernated databases wake. Through Jentic you install once, import Layerbase from the API Directory, store the key once, and your agent calls it.

Permission scoping

Layerbase puts the database id in the URL path (/v1/databases/{id}/query), so a rule can pin your agent to one database and the operations you pick. You choose the operations it may call, so sensitive ones like key revocation or key rotation are not included unless you add them.

Credential isolation

Your Layerbase API key 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.

Intent-based discovery

Agents search Jentic by intent such as 'run a SQL query' or 'provision a temporary database', and Jentic returns the matching Layerbase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Layerbase Cloud API through Jentic.

Is there a Layerbase MCP server?

You don't need an MCP server to give your agent the Layerbase Cloud API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so your agent's context carries no tool definitions it will not use.

What authentication does the Layerbase Cloud API use?

Per its OpenAPI spec, Layerbase uses HTTP bearer authentication with a personal API key sent as `Authorization: Bearer sk_<your-key>`. An account-scoped key can reach every authenticated endpoint, while a database-scoped key may only call its own database. The health check and engine registry are open. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

Can I run SQL against a Layerbase database without a driver?

Yes. POST /v1/databases/{id}/query takes a JSON body such as { "query": "SELECT 1" } for SQL engines and returns columns, rows, and rowCount. A hibernated database wakes automatically, answering 503 with retry_after while it starts, and a locked database returns 423.

What are the rate limits for the Layerbase Cloud API?

The OpenAPI spec does not specify rate limits. Check https://layerbase.com/docs/api for current limits and plan quotas.

How do I create a temporary database through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Layerbase Cloud API from the directory, and store your API key. Your agent then searches for 'provision a database' and Jentic returns POST /v1/databases, which needs only engine and accepts ttlHours to make the database transient. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which database engines can Layerbase provision?

Call GET /v1/engines, which needs no key, to read the current registry. The spec gives postgresql, mysql, redis, valkey, mariadb, mongodb, and clickhouse as examples of the engine value POST /v1/databases accepts, with version defaulting to the engine default from that registry.

Can I limit what my agent is allowed to do with the Layerbase Cloud API?

Yes. Write a rule that allows only POST /v1/databases/{id}/query and GET /v1/databases/{id} for your reporting database id: the agent can read that database and run queries against it, while provisioning, other databases, and the API key operations stay out of reach, and every call it makes is logged.

Layerbase Cloud API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageDatabasebearer11 EndpointsREST

For Agents

Provision Postgres, MySQL, Redis, MongoDB, ClickHouse, and other databases, run queries over HTTP without a driver, and create, rotate, or revoke database-scoped API keys.

Use for: I need to spin up a temporary Postgres database for a CI run, Run SELECT count(*) on the orders table in my Layerbase database, List all databases on my Layerbase account, Check which engines and versions Layerbase can provision

Not supported: Does not handle file or object storage, user authentication, schema migrations, or analytics dashboards. Use for provisioning databases, querying them over HTTP, and managing their API keys only.

The Layerbase Cloud API provisions managed databases and runs queries against them over plain HTTPS, with no driver or open socket required. A single create call takes an engine such as postgresql, mysql, redis, valkey, mariadb, mongodb, or clickhouse, plus optional backupPolicy, storageBlocks, and ttlHours for transient databases that are destroyed at expiry. The same surface lists and inspects your databases, reports key identity and usage, and creates, rotates, and revokes the personal API keys that authenticate each call, including keys scoped to a single database.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

68%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

33%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

83%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Layerbase Cloud API to your agent

Capabilities

Start building with Layerbase Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Layerbase Cloud API

Jentic AI Readiness Score

Layerbase Cloud API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness