Catalogue API (RUD Metadata Management)

When to use this skill

• List or count embeddings tables in the catalogue
• Change visibility, update metadata, or delete catalogue entries
• Not for creating embedding vectors (use workers) or similarity queries (use RPC)

Use the Geobase project PostgREST API (geoembeddings schema) to inspect and manage embeddings_catalogue metadata on GEOBASE_PROJECT_URL — not the Studio host or /api/projects/... routes.

Required inputs

• GEOBASE_PROJECT_URL — project host (e.g. https://<project-ref>.geobase.app)
• GEOBASE_ANON_KEY — send as apikey on every request

Mutations (PATCH visibility, delete table) require one of:

• GEOBASE_SERVICE_ROLE_KEY — project service role; use server-side only as both apikey and Authorization: Bearer. Not available to agents or CLI — user must put the real key in gitignored .env.secrets (human in the loop; never paste in chat). See @geobase → Secrets (human in the loop). Or:
• A project user access token — user signed into that project (GoTrue on GEOBASE_PROJECT_URL) whose id matches owner on the catalogue row for that table.