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

# Quickstart

> From a key to your first relation in three requests.

<Steps>
  <Step title="Get a key">
    Keys are issued by the Routeur team during the private preview. A key looks like `rk_live_<id>_<secret>` and is shown once, so store it somewhere secret and only use it server-side.
  </Step>

  <Step title="Check the service">
    `/v1/status` names the latest graph run and the crawls it was built from.

    ```bash theme={null}
    curl https://api.routeur.app/v1/status \
      -H "X-API-Key: $ROUTEUR_API_KEY"
    ```
  </Step>

  <Step title="Browse events">
    Events group a venue's markets the way people browse them. Filter by category, search their titles, or keep only events listed on both venues.

    ```bash theme={null}
    curl "https://api.routeur.app/v1/events?category=Politics&cross_venue=true&limit=5" \
      -H "X-API-Key: $ROUTEUR_API_KEY"
    ```

    Every event carries its leading outcomes with the best price on each venue.
  </Step>

  <Step title="Read a market's relations">
    Take a venue and market id from an outcome (`venue` and `market_id`) and ask what that market is proven to relate to. `cross_venue=true` keeps only markets on the other venue.

    ```bash theme={null}
    curl "https://api.routeur.app/v1/markets/$VENUE/$MARKET_ID/relations?cross_venue=true" \
      -H "X-API-Key: $ROUTEUR_API_KEY"
    ```
  </Step>
</Steps>

## Next

<CardGroup cols={2}>
  <Card title="Leads" icon="scale-balanced" href="/concepts/leads">
    Turn a relation into a purchase that pays in every outcome.
  </Card>

  <Card title="Rate limits" icon="gauge" href="/rate-limits">
    What your tier allows and the headers that report it.
  </Card>
</CardGroup>