Blackbird
Blackbird Labs is the membership network for restaurant lovers, founded by Eater and Resy co-founder Ben Leventhal. Its consumer app lets diners earn status, perks, and points at world-class restaurants and pay their check in FLY, Blackbird's loyalty token. Blackbird's developer platform is the Flynet API — read access to the dining network (restaurants, locations, check-ins, member identity, and memberships) plus FLY Payment Intents modeled on Stripe — backed by an OpenAPI spec, first-party TypeScript SDKs (@flynetdev/core and @flynetdev/react), two MCP servers, a published agent skill, and llms.txt. Flynet is a layer-3 network built on Coinbase's Base chain. Backed by a16z, dcvc, and multicoin-capital.
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 Blackbird the way a machine reads it — 15 machine-readable artifacts across 10 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 — Blackbird scores 47.3/100 (developing), with a separate agent-readiness read of 74/100 (agent native). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Blackbird
Each block below is one kind of artifact we hold for Blackbird. 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 10
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.
Blackbird App API
The App API from Blackbird — 1 operation(s) for app.
Blackbird Challenges API
The Challenges API from Blackbird — 1 operation(s) for challenges.
Blackbird Check-ins API
Filtered visit records.
Blackbird Locations API
Physical venues and open hours.
Blackbird Memberships API
Per-(member, restaurant) loyalty records carrying check-in counts and tiers.
Blackbird Payments API
Payment Intents for FLY-funded payments.
Blackbird Restaurants API
Brand-level restaurant discovery.
Blackbird Rewards API
The Rewards API from Blackbird — 2 operation(s) for rewards.
Blackbird Specials API
The Specials API from Blackbird — 1 operation(s) for specials.
Blackbird Users API
The authenticated member — profile, status, wallets, tags, and check-in history. Subject resolved from the token.
Scroll within the panel for all 10 ·
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.
blackbird-mcp.yml
MCP SERVERSecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Blackbird — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/blackbird · machine-readable index on apis.io