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

# Quickstart

> Mint a key and make your first call in under five minutes.

<Steps>
  <Step title="Mint a key">
    In the Originalis app, go to
    [Integrations → API Keys](https://app.originalis.ai/app/integrations/api-keys) and create
    a key. Choose **Read-only** for pure integrations or **Read & write**
    if you'll invoke analysis actions.

    The secret (`ak_...`) is shown once — store it in your secret
    manager. Keys can be given an expiry and revoked at any time.
  </Step>

  <Step title="Make a read call">
    ```bash theme={null}
    curl -H "Authorization: Bearer ak_..." \
      "https://api.originalis.ai/api/v1/network/who-knows?domain=acme.com"
    ```

    Responses are plain JSON. List and detail reads state their `scope`
    (whose data you're seeing) and carry `as_of`:

    ```json theme={null}
    {
      "target": { "domain": "acme.com", "person": null },
      "scope": "org_shared",
      "paths": [
        {
          "contact_id": "9f2c1b7a-4e11-4c2e-9b3a-1d5f6a7b8c9d",
          "name": "Jane Doe",
          "title": "CTO",
          "email": "jane@acme.com",
          "warmth": 0.72,
          "strength_score": 81.0,
          "relationship": "strong",
          "path_owner": "Mark Smith"
        }
      ],
      "unavailable_reason": null,
      "as_of": "2026-09-02T14:00:00Z"
    }
    ```
  </Step>

  <Step title="Run your first action">
    With a write-scoped key, submit a company for full analysis:

    ```bash theme={null}
    curl -X POST -H "X-API-Key: ak_..." -H "Content-Type: application/json" \
      -d '{"website_url": "https://acmerobotics.com"}' \
      "https://api.originalis.ai/api/v1/deals/analyze"
    ```

    You get a `202` with a `status_url` — see
    [Actions](/guides/actions) for the full polling/streaming story.
  </Step>
</Steps>

<Note>
  The full endpoint catalog with request/response schemas and runnable
  examples lives in the **API Reference** tab — it is generated from the
  live service, so it always matches what's deployed.
</Note>