Crunchy Bridge API

Name: Crunchy Bridge API API
Brand: Crunchy Bridge API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasebearer26 EndpointsREST

For Agents

Manage managed PostgreSQL clusters, networks, access tokens, and per-cluster Postgres roles on Crunchy Bridge.

Quickstart

Get started with Crunchy Bridge API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a postgres role on a managed cluster"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Crunchy Bridge API API.

Create, update, delete, and fork managed PostgreSQL clusters

Suspend, resume, restart, and back up clusters via dedicated action endpoints

Toggle high availability per cluster with enable-ha and disable-ha

Issue and revoke short-lived access tokens that scope agent or CI access

GET STARTED

Start building with Crunchy Bridge API API

Explore with Jentic

View OpenAPI Document

Use for: Provision a new PostgreSQL cluster on Crunchy Bridge, Suspend my dev cluster after hours to reduce billing, Fork the production cluster for a load test, Create a Postgres role with read-only permissions on cluster cl_xyz

Not supported: Does not handle SQL execution, query monitoring, or schema migrations — use for cluster, network, role, and access-token administration only.

Jentic publishes the only available OpenAPI document for Crunchy Bridge API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Crunchy Bridge API, keeping it validated and agent-ready. This Crunchy Data surface covers cluster lifecycle (create, update, delete, fork), runtime actions (suspend, resume, restart, backup, HA toggles), account management, access token issuance, network configuration, and Postgres role management across 26 endpoints. Authentication uses a bearer token — either a long-lived cbkey_ API key or a short-lived access token.

Use Cases

Patterns agents use Crunchy Bridge API API for, with concrete tasks.

★ Postgres Role Management at Scale

Automate creation and rotation of per-cluster Postgres roles by calling the role endpoints from a script or agent. Useful when issuing scoped credentials for downstream services or when offboarding employees who held read-write access.

POST /clusters/{cluster_id}/roles with the role name and password policy, then PUT /clusters/{cluster_id}/roles/{role_name} to grant the necessary privileges.

Cluster Lifecycle Automation

Drive the full cluster lifecycle — create, fork for testing, suspend overnight, resume on demand, and finally delete — from CI or an ops agent without anyone touching the dashboard. Crunchy Bridge exposes every action as a dedicated PUT verb.

POST /clusters to create the cluster, run integration tests, PUT /clusters/{cluster_id}/actions/suspend afterwards, and DELETE /clusters/{cluster_id} when the run finishes.

Short-Lived Access Tokens for Agents

Issue narrowly scoped, time-limited access tokens for AI agents or external services so the long-lived cbkey_ key never leaves the secure vault. Revoke the token immediately when the workflow completes.

POST /access-tokens to mint a scoped token, hand it to the downstream service, then DELETE /access-tokens/{access_token_id} once the run finishes.

Network Configuration Updates

Inspect and update Crunchy Bridge network resources to control which CIDR blocks, peering connections, or private endpoints can reach a cluster. Patching the network record propagates rule changes without re-creating the cluster.

GET /networks to list networks, then PATCH /networks/{network_id} with the updated CIDR allowlist.

Agent-Driven Database Ops

Allow an AI agent to handle the routine PostgreSQL chores — provisioning, role creation, suspend/resume, token rotation — through Jentic so the cbkey_ token stays in the vault and only short-lived scoped tokens enter the runtime context.

Search Jentic for 'create a postgres role', load the create-role operation, and execute it for the target cluster.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/clusters

Create a managed PostgreSQL cluster

POST

/clusters/{cluster_id}/forks

Fork a cluster

PUT

/clusters/{cluster_id}/actions/suspend

Suspend a cluster

PUT

/clusters/{cluster_id}/actions/start-backup

Trigger a backup

POST

/access-tokens

Mint a short-lived access token

POST

/clusters/{cluster_id}/roles

Create a Postgres role

PATCH

/networks/{network_id}

Update a network configuration

POST

/clusters

Create a managed PostgreSQL cluster

POST

/clusters/{cluster_id}/forks

Fork a cluster

PUT

/clusters/{cluster_id}/actions/suspend

Suspend a cluster

PUT

/clusters/{cluster_id}/actions/start-backup

Trigger a backup

POST

/access-tokens

Mint a short-lived access token

Why though Jentic?

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

Credential isolation

Long-lived cbkey_ tokens are stored encrypted in the Jentic vault. For agent runs Jentic can mint short-lived access tokens via POST /access-tokens so the long-lived key never enters runtime context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a postgres role') and Jentic returns the matching role or cluster operation along with its parameter schema.

Time to first call

Direct integration: 1-2 days to wire bearer auth, role and access-token lifecycle, and network management. Through Jentic: minutes per operation.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Crunchy Bridge API

Sister Crunchy Bridge surface — narrower endpoint set covering similar lifecycle operations.

Pick the crunchybridge.com entry when the agent does not need access tokens, networks, or per-cluster Postgres role endpoints.

Complementary

Crusoe Cloud API

Cloud compute API; useful for workloads that talk to Crunchy Bridge clusters.

Pair when the agent provisions both compute (Crusoe) and managed Postgres (Crunchy Data) for an end-to-end stack.

Complementary

Crustdata API

External data enrichment to populate downstream Postgres tables.

Use Crustdata to fetch external company or people data, then write into a Crunchy Bridge cluster managed via this API.

FAQs

Specific to using Crunchy Bridge API API through Jentic.

Why is there no official OpenAPI spec for Crunchy Bridge API?

Crunchy Data does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crunchy Bridge 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 Crunchy Bridge API use?

The API uses bearer-token authentication. The token can either be a long-lived cbkey_ API key or a short-lived access token issued via POST /access-tokens. Through Jentic the token is held in the encrypted vault.

Can I create Postgres roles inside a cluster with this API?

Yes. POST /clusters/{cluster_id}/roles creates a new Postgres role on the target cluster. Subsequent PUT /clusters/{cluster_id}/roles/{role_name} calls update privileges, and DELETE removes the role when the access is no longer needed.

How do I issue a short-lived access token through the Crunchy Bridge API?

Call POST /access-tokens to mint a scoped token, hand it to the downstream service, and call DELETE /access-tokens/{access_token_id} to revoke it when the workflow completes.

What are the rate limits for the Crunchy Bridge API?

The OpenAPI specification does not document specific rate limits. Inspect HTTP 429 responses on bursty traffic and contact Crunchy Data support for production quotas.

How do I provision a cluster through Jentic?

Run pip install jentic, search 'provision a postgres cluster', load the create-cluster operation, and execute it with your plan and region. Jentic resolves auth automatically.