Supabase
Supabase is an open-source Firebase alternative that provides a suite of backend services built on top of PostgreSQL. It offers a managed PostgreSQL database with auto-generated REST and GraphQL APIs via PostgREST, real-time data subscriptions via WebSockets, user authentication with JWT (GoTrue), file storage with S3-compatible object storage, edge compute via globally distributed TypeScript functions on the Deno runtime, and a management API for programmatic control of projects and organizations. Supabase is available as a fully managed cloud service (app.supabase.com) and as a self-hosted open-source deployment.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Supabase the way a machine reads it — 85 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Supabase scores 42.5/100 (developing), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Supabase's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/supabase/"
title="Supabase on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/supabase.svg"
alt="Supabase Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/supabase/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/supabase/"
title="Supabase on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/supabase/card.svg"
alt="Supabase Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Supabase
Each block below is one kind of artifact we hold for Supabase. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Supabase Realtime API
The Supabase Realtime API provides WebSocket-based subscriptions for real-time data changes from PostgreSQL databases. It supports three channel types: database change events (I...
Supabase Admin API
Administrative endpoints for managing users. Requires service_role key.
Supabase Authentication API
User signup, signin, and token management endpoints.
Supabase Buckets API
Manage storage buckets that organize files and folders. Buckets can be public or private and have configurable file size limits and allowed MIME types.
Supabase Configuration API
Server configuration and settings endpoints.
Supabase Database API
Manage database configurations, migrations, and extensions.
Supabase Domains API
Configure custom domains and vanity subdomains for projects.
Supabase Functions API
Deploy and manage Edge Functions for serverless compute at the edge.
Supabase Invocation API
Invoke deployed Edge Functions via HTTP requests. Each function is accessible at its own URL path based on its slug.
Supabase MFA API
Multi-factor authentication enrollment and verification endpoints.
Supabase Network API
Manage network restrictions, bans, and SSL enforcement.
Supabase OAuth API
OAuth social login provider endpoints.
Supabase Objects API
Upload, download, move, copy, and delete files within storage buckets.
Supabase Organizations API
Manage organizations including membership, billing, and settings.
Supabase Projects API
Manage Supabase projects including creation, configuration, pausing, restoring, and deletion.
Supabase Rendering API
Serve and transform stored files including image resizing and format conversion.
Supabase RPC API
Invoke PostgreSQL functions via remote procedure calls.
Supabase Secrets API
Manage project secrets used by Edge Functions and other services.
Supabase SSO API
SAML-based single sign-on endpoints.
Supabase Tables API
CRUD operations on database tables. Paths are auto-generated based on your database schema.
Supabase User Management API
Endpoints for managing the currently authenticated user profile.
Scroll within the panel for all 21 ·
Open Collections 26
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONSupabase Auth Admin API
OPEN COLLECTIONSupabase Auth API
OPEN COLLECTIONSupabase Auth Admin Authentication API
OPEN COLLECTIONSupabase Auth Admin Buckets API
OPEN COLLECTIONSupabase Auth Admin Configuration API
OPEN COLLECTIONSupabase Auth Admin Database API
OPEN COLLECTIONSupabase Database REST API
OPEN COLLECTIONSupabase Auth Admin Domains API
OPEN COLLECTIONSupabase Edge Functions API
OPEN COLLECTIONSupabase Auth Admin Functions API
OPEN COLLECTIONSupabase Auth Admin Invocation API
OPEN COLLECTIONSupabase Management API
OPEN COLLECTIONSupabase Auth Admin MFA API
OPEN COLLECTIONSupabase Auth Admin Network API
OPEN COLLECTIONSupabase Auth Admin OAuth API
OPEN COLLECTIONSupabase Auth Admin Objects API
OPEN COLLECTIONSupabase Auth Admin Organizations API
OPEN COLLECTIONSupabase Auth Admin Projects API
OPEN COLLECTIONSupabase Auth Admin Rendering API
OPEN COLLECTIONSupabase Auth Admin RPC API
OPEN COLLECTIONSupabase Auth Admin Secrets API
OPEN COLLECTIONSupabase Auth Admin SSO API
OPEN COLLECTIONSupabase Storage API
OPEN COLLECTIONSupabase Auth Admin Tables API
OPEN COLLECTIONSupabase Auth Admin User Management API
OPEN COLLECTIONScroll within the panel for all 26 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERAgent Skills 2
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
supabase-postgres-best-practices
AGENT SKILLsupabase
AGENT SKILLGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Supabase GraphQL API
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Supabase Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Supabase Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Supabase Realtime API
The Supabase Realtime API enables real-time communication over WebSocket connections using the Phoenix Channel protocol (v2). It supports three main features: Postgres Changes f...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Supabase Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 1
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Supabase Project
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Supabase Project Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Supabase Select Rows Example
EXAMPLESupabase Sign Up Example
EXAMPLESecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Supabase — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/supabase · machine-readable index on apis.io
This is an independent, third-party profile of Supabase, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.