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

# API Overview

> Explore EveryBite's suite of APIs for food intelligence and guest personalization

# EveryBite APIs

EveryBite provides a comprehensive suite of APIs to power personalized dining experiences.

## Available APIs

<CardGroup cols={2}>
  <Card title="SmartMenu API" icon="utensils" href="/api/smartmenu/overview">
    Real-time menu personalization based on dietary preferences, allergens, and health goals
  </Card>

  <Card title="GuestIQ" icon="user-check" href="/api/guestiq/overview">
    Guest identification, segmentation, and behavioral signals for personalized experiences
  </Card>
</CardGroup>

## Getting Started

1. **Get API credentials** - [Contact us](mailto:api-partnerships@everybite.com) to get your API key
2. **Choose your API** - Select the APIs that match your use case
3. **Authenticate** - Include your API key in the Authorization header
4. **Start building** - Follow the [Quickstart Guide](/docs/quickstart)

## Authentication

All EveryBite APIs use API key authentication. Include your key in every request as the raw `Authorization` header value:

```bash theme={null}
Authorization: pk_YOUR_API_KEY
```

If you are using the docs auth or headers tab, paste only the `pk_...` value.

<Info>
  **Postman users:** Do not use the **Authorization tab** with type "Bearer Token" — Postman will prepend `Bearer ` to the value, which will cause authentication to fail.

  Instead, go to the **Headers tab** and add the key manually:

  | Key             | Value             |
  | --------------- | ----------------- |
  | `Authorization` | `pk_YOUR_API_KEY` |

  If your chain API key is restricted to specific origins, also add an `Origin` header with one of the approved values, otherwise the request will be rejected:

  | Key      | Value                              |
  | -------- | ---------------------------------- |
  | `Origin` | `https://your-approved-origin.com` |
</Info>

See the [Authentication Guide](/docs/authentication) for details on:

* API key types (Restaurant, Chain, Brand)
* Session-based context
* Rate limits and error handling

## Rate Limits

| Key Type   | Requests/minute | Requests/day |
| ---------- | --------------- | ------------ |
| Restaurant | 60              | 10,000       |
| Chain      | 300             | 100,000      |
| Brand      | 1,000           | Unlimited    |

## Need Help?

* Check our [Guides](/docs/guides/best-practices) for implementation patterns
* Contact [api-partnerships@everybite.com](mailto:api-partnerships@everybite.com) for support