> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flynet.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> From sandbox access to your first integration.

# Start building today

The Flynet API gives you read access to Blackbird's dining graph and
write access to FLY Payment Intents. Before you write code, walk
through the steps below.

<Steps>
  <Step title="Get sandbox access">
    Request staging credentials via [Request access](/resources/request-access). Approval typically takes about a week.
  </Step>

  <Step title="Read the house rules">
    Skim [Concepts](/concepts/authentication): auth, pagination, errors, and data model basics take ten minutes and save you bug reports later.
  </Step>

  <Step title="Run the quickstart">
    [Quickstart](/quickstart) makes three authenticated calls (wallets,
    check-ins, restaurants) and confirms both credential schemes work.
  </Step>

  <Step title="Pick a recipe">
    Browse [Recipes](/recipes) for working code on common product slices: discovery, profile UI, activity feeds, and payments.
  </Step>

  <Step title="Wire up authentication">
    For production, integrate OAuth. The [OAuth concept page](/concepts/oauth)
    walks the full PKCE flow in about 10 minutes. For server-to-server
    calls without a member context, use your API key; see [API keys](/concepts/api-keys).
    Or drop in the [TypeScript client](/concepts/typescript-client) and skip the plumbing.
  </Step>

  <Step title="Bring your AI agent">
    Building with Claude Code or Cursor? [Build with AI](/build-with-ai/overview)
    wires your agent into the live docs, the API, and the SDK's rules — or follow
    the [full walkthrough](/build-with-ai/walkthrough) from empty directory to a
    Vercel deploy.
  </Step>
</Steps>

<Warning>
  **Keep credentials server-side.** Your API key and `client_secret`
  are server-to-server secrets; they must only ever be used from your
  backend, never shipped to a browser, mobile client, or any code your
  users can see. Route Discovery and token-exchange calls through your
  own backend; the only thing that belongs client-side is the
  short-lived OAuth access token, held in memory. See
  [API keys](/concepts/api-keys) and [OAuth](/concepts/oauth).
</Warning>

## What you can build

<CardGroup cols={3}>
  <Card title="Restaurant network growth" icon="chart-line" />

  <Card title="Consumer discovery" icon="map" />

  <Card title="Data visualizations" icon="chart-bar" />

  <Card title="Data marketplaces" icon="store" />

  <Card title="Consumer marketplace tooling" icon="cart-shopping" />

  <Card title="Third-party tools" icon="puzzle-piece" />
</CardGroup>

<CardGroup cols={1}>
  <Card title="Get API keys →" icon="key" href="https://blackbirdlabsinc.typeform.com/to/KDFWyPsm?typeform-source=flynet.org" color="purple">
    Request sandbox access and join the developer community.
  </Card>
</CardGroup>

## Resources

* [API reference](/api-reference/introduction): interactive playground for the launch endpoints
* [Recipes](/recipes): copy-paste code for common product slices
* [FAQ](/resources/faq): common gotchas
* [Support](/resources/support): get help when you're blocked