Supabase Management API
✓ Official Vendor SpecProductivityCalendar Schedulingbearer14 EndpointsREST
For Agents
Programmatically create project, list projects. Covers 14 operations with bearer authentication.
Use for: I need to project, I want to projects, Search for project, Find all project
Not supported: Does not handle payments, communications, or crm — use for productivity only.
Supabase project management API. The API exposes 14 endpoints secured 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.
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 Supabase Management API.
Create project
List projects
Get project
Delete project
Monitor Supabase Management API operational status and events
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
List edge functions
GET
/projects/{ref}/functions/{slug}
Get function
PATCH
/projects/{ref}/functions/{slug}
Update function
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Supabase Management API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create project') and Jentic returns the matching Supabase Management API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Supabase Management API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED