Supabase

Connect your own Supabase organization to agntdata via the Supabase Management API.

This is not the agntdata-provisioned workspace database. agntdata can provision a Supabase project for your workspace and expose it at /v1/db/* — that’s a separate, managed surface. This connection talks to your own Supabase organization using a Personal Access Token you generate in the Supabase dashboard. Use it to manage projects that live outside agntdata.

Overview

The Supabase connection proxies requests to the Supabase Management API at https://api.supabase.com. Use it to enumerate projects, run SQL against a project’s primary database, list and inspect edge functions, read secret names, and list database branches.

• Base URL: https://api.agntdata.dev/v1/connections/supabase/*
• Supabase auth: agntdata injects Authorization: Bearer <your_supabase_pat>
• Credential: Supabase Personal Access Token (sbp_...), account-wide scope.

Setup

1. Generate a Supabase Personal Access Token

   In Supabase go to Account → Access tokens and create a PAT (sbp_...).

2. Paste it into agntdata

   In the agntdata dashboard open Integrations, pick Supabase, and paste the PAT.

3. Call the Management API

   Make requests to https://api.agntdata.dev/v1/connections/supabase/* with your agntdata API key. agntdata injects your PAT on every proxied request.

Supabase PATs are account-wide — they can read and modify any project in any organization your Supabase account belongs to. Treat the PAT like a root credential and rotate it from Account → Access tokens if you suspect it has leaked.

Examples

List projects you can see

curl -X GET "https://api.agntdata.dev/v1/connections/supabase/v1/projects" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Retrieve one project

curl -X GET "https://api.agntdata.dev/v1/connections/supabase/v1/projects/abcd1234" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Run a SQL query against a project

curl -X POST "https://api.agntdata.dev/v1/connections/supabase/v1/projects/abcd1234/database/query" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"select count(*) from public.events"}'

List edge functions

curl -X GET "https://api.agntdata.dev/v1/connections/supabase/v1/projects/abcd1234/functions" \
  -H "Authorization: Bearer $AGNTDATA_API_KEY"

Supported operations

• Projects — list, retrieve
• Database — run SQL via the Management API
• Edge Functions — list, retrieve metadata
• Secrets — list names (values are never returned)
• Branches — list

When to use the workspace database instead

If you want a Supabase project managed by agntdata (provisioning, service-role key handling, row-level audit, SDK/MCP parity with the agent runtime), use the agntdata workspace database at /v1/db/* — no PAT required. See the /v1/db/* documentation for that surface.