Supabase

Connect Supabase to add your organizations, projects, databases, and organization members to your Asset Map.

​

What it maps

This gives agents context about where a project runs and who has access to manage it.

​

Access required

Use a Supabase personal access token for the Management API. The integration reads organization, project, and member metadata. If your account offers scoped tokens, grant Read access to Organizations, Projects (account-wide), and Organization Members, covering the organizations you want to map. A token’s permissions are also limited by the account that creates it. See Supabase personal access tokens. Classic personal access tokens inherit your account’s access. Antigen uses them for read operations, but the token may also permit changes in Supabase.

​

Connect Supabase

​

1. Create a personal access token

Open Supabase access tokens. Generate a token named Antigen and copy its value. Use a personal access token beginning with sbp_. Project publishable keys, secret keys, and legacy anon or service_role keys authenticate to a project’s APIs and cannot replace this management token.

​

2. Complete the connection

Open Settings → Integrations → Supabase in Antigen. Paste the token and select Connect. Antigen discovers the organizations and projects available to the token and adds them to your Asset Map.

​

Troubleshooting

​

An organization or project is missing

Check that the account that created the token has access to it. For a scoped token, also check the selected organizations, projects, and read permissions.

​

The connection stops syncing

Confirm that the token is still valid and that its owner still has the required access. If you revoke the token, reconnect with a replacement.