Supabase Management API

Name: Supabase Management API
Brand: Supabase Management API
Availability: InStock

✓ Official Vendor SpecProductivityCalendar Schedulingbearer14 EndpointsREST

For Agents

Programmatically create project, list projects. Covers 14 operations with bearer authentication.

Install Jentic One Beta

Connect the Supabase Management API to your agent

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

Create project

List projects

Get project

Delete project

GET STARTED

Start building with Supabase Management API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Supabase Management API for, with concrete tasks.

★ Productivity Operations

Use the Supabase Management API to perform productivity operations programmatically. The API provides 14 endpoints covering core functionality including create project, list projects, get project.

Call POST /projects to create project

Automated API Keys Management

Automate api keys operations by combining multiple Supabase Management API endpoints. Agents can list projects and then get project in a single workflow.

Call GET /projects to list projects, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Supabase Management API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Search Jentic for 'create project', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — supabase project management api.

METHOD

PATH

DESCRIPTION

POST

/projects

Create project

GET

/projects

List projects

GET

/projects/{ref}

Get project

DELETE

/projects/{ref}

Delete project

POST

/projects/{ref}/functions

Create edge function

GET

/projects/{ref}/functions

List edge functions

GET

/projects/{ref}/functions/{slug}

Get function

PATCH

/projects/{ref}/functions/{slug}

Update function

POST

/projects

Create project

GET

/projects

List projects

GET

/projects/{ref}

Get project

DELETE

/projects/{ref}

Delete project

POST

/projects/{ref}/functions

Create edge function

GET

/projects/{ref}/functions

Why Jentic?

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

Credential isolation

Your Supabase Management API 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a project' or 'list edge functions', and Jentic returns the matching Supabase Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Supabase Management API through Jentic.

What authentication does the Supabase Management API use?

The Supabase Management API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create project with the Supabase Management API?

Yes. Use the POST /projects endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Supabase Management API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create project through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create project'. Jentic returns the matching Supabase Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Supabase Management API have?

The Supabase Management API exposes 14 endpoints covering api keys, functions, organizations operations.

Supabase Management API

Connect the Supabase Management API to your agent

Capabilities

Start building with Supabase Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs