canonical: https://jentic.com/apis/supabase.com/supabase

# Supabase Management API

Supabase project management API. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or crm - use for productivity only.

## Capabilities

- Create project
- List projects
- Get project
- Delete project
- Monitor Supabase Management API operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **API Keys** — Operations related to API Keys
- **Functions** — Operations related to Functions
- **Organizations** — Operations related to Organizations
- **Projects** — Operations related to Projects
- **Secrets** — Operations related to Secrets

## Why Jentic

- **Setup:** Wiring the Supabase Management API by hand means handling its bearer token auth against api.supabase.com and managing retries yourself. Through Jentic you install once, import the Supabase Management API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Supabase Management API puts the project ref in the URL path (/projects/{ref}/...), so a rule can pin your agent to one project: it can read and manage functions for that project and nothing else. You choose the operations it may call, so destructive ones like deleting a project are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

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

### Can I limit what my agent is allowed to do with the Supabase Management API?

Yes. Because you run Jentic One yourself, your own rules decide which Supabase Management API operations and credentials the agent may use. Since the API puts the project ref in the URL path, such as /projects/{ref}/functions, you can pin the agent to a single project so it only reads and manages functions for that project and nothing else. You also pick the exact operations it may call, so a destructive one like DELETE /projects/{ref} stays out of reach unless you deliberately grant it.