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

# Quickstart

> Pick the path that matches what you are building.

Four ways in. They all end with a working agent — the difference is how you
reach it.

<CardGroup cols={2}>
  <Card title="In the browser" icon="window" href="/quickstart/browser">
    A talking agent on a web page. The fastest way to hear it work.
  </Card>

  <Card title="Answering the phone" icon="phone" href="/quickstart/inbound-phone">
    Point a number at an agent and have it answer.
  </Card>

  <Card title="Outbound calls" icon="phone-arrow-up-right" href="/quickstart/outbound">
    Have an agent call someone.
  </Card>

  <Card title="Your own telephony" icon="tower-cell" href="/quickstart/byot">
    Bridge Twilio, Telnyx, or Plivo yourself.
  </Card>
</CardGroup>

<Note>
  All four need an API key from
  [**API Keys**](https://dashboard.omnia-voice.com/dashboard/api-keys). Keep it
  in your environment as `OMNIA_API_KEY` and never ship it to a browser.
</Note>

## Not sure?

Start with **[the browser](/quickstart/browser)**. It needs no phone number and
no carrier, and hearing the agent answer is the quickest way to know whether the
prompt is right. Everything you configure there carries over unchanged to a
phone line.

## What every path shares

<Steps>
  <Step title="An agent">
    Personality, voice, language, and call behaviour. Created once, reached
    everywhere. See [Agents](/concepts/agents).
  </Step>

  <Step title="A call">
    Created server-side with your API key, returning a short-lived
    `websocketUrl`. See [Calls](/concepts/calls).
  </Step>

  <Step title="Tools and knowledge, when you need them">
    [Tools](/tools/overview) to act, [corpora](/concepts/corpora) to answer from
    your documents.
  </Step>
</Steps>