Skip to main content

​
Build on Flynet

Flynet is the developer surface for Blackbird: the APIs, payment rails, and $FLY rewards that power the dining network, opened up for you to build on.

​
Why build on Flynet

A network that's already busy

Real members dining at real restaurants, with relationships across some of the best rooms in the country. You’re not seeding a directory from zero; you’re building on a network that already shows up.

Rails that already carry weight

Payments and $FLY rewards run in production today, moving real value across live wallets. Build on infrastructure that’s already doing the work, not a sandbox waiting for its first call.

Data you can trust

Authenticated profiles, verified check-ins, real spend. Ground truth about how people actually dine, not a model’s best guess.

​
What to build

Restaurant network growth

Consumer discovery

Data visualizations

Data marketplaces

Consumer marketplace tooling

Third-party tools

Payments

We’d love to hear what else fits the network. Apply to build on Flynet.

​
What you can build today

The first Flynet API surfaces (Discovery, member context, and Payments) are live in staging. Discovery gives you read access to restaurants and locations. Member context gives you the authenticated member’s profile, status, wallets, tags, and check-ins via /users/me/*. Payments lets approved partners accept FLY-funded transactions on behalf of merchants.
  • Restaurants: brand-level metadata, cuisine, and image assets
  • Locations: physical venues with address, geo, weekly hours, and reservation fields
  • Member context: the authenticated member’s profile, status, wallets, tags, and check-ins (/users/me/*)
  • Memberships: the member’s restaurant membership records
  • Check-ins: visit records with embedded venue context (filters optional)
  • Payments: accept FLY-funded payments from Blackbird members on behalf of your merchants
More APIs are on the way, including rewards, webhooks, and Mini Apps inside the Blackbird app surface itself.

​
How requests flow

Every request goes through /flynet/v1/*. Discovery routes use X-API-Key; member-acting and payment routes use OAuth bearer tokens. See Authentication for the house rules.

​
Become a Flynet developer

Let’s build the future of the restaurant economy together.

Get started

Sandbox access, quickstart, and the four-step onboarding.

Apply to Build on Flynet

Tell us what you’re building. We’ll help you get there.

API Reference

Interactive playground for every launch endpoint.

Block Explorer

View live network activity.