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

# Install and keys

> Install the Founding Agent SDK and set up your publishable and API keys.

## Install

<CodeGroup>
  ```bash npm theme={null}
  npm install @moss-tools/founding-agent
  ```

  ```bash pnpm theme={null}
  pnpm add @moss-tools/founding-agent
  ```

  ```bash yarn theme={null}
  yarn add @moss-tools/founding-agent
  ```
</CodeGroup>

## Keys

<CardGroup cols={2}>
  <Card title="Publishable key" icon="globe">
    Starts with `pk_`. Safe to expose in the browser. Used by the React provider to identify your agent.
  </Card>

  <Card title="API key" icon="lock">
    Starts with `sk_`. A server secret used to mint sessions. Shown once, so store it safely and never ship it to the browser.
  </Card>
</CardGroup>

Find both keys in the portal under your agent's Deploy step at [https://portal.usemoss.dev/fa](https://portal.usemoss.dev/fa).

<Warning>
  Never ship the `sk_...` API key to the browser. Keep it in server-side environment variables only.
</Warning>

## Environment variables

Keep the API key in a server-side environment variable so it never reaches the browser. The token route reads it as `MOSS_FA_API_KEY`.

```env theme={null}
MOSS_FA_API_KEY=sk_yourcompany_...
```

The publishable key is browser-safe. Pass it to the provider directly, or read it from a `NEXT_PUBLIC_` variable if you prefer. See [React components](/docs/founding-agent/embed/react-components).

## Next steps

<CardGroup cols={1}>
  <Card title="Server token route" icon="server" href="/docs/founding-agent/embed/server-token-route">
    Create the server route that mints a short-lived session for the browser.
  </Card>
</CardGroup>
