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

# Authentication

> Connect a local agent, authenticate a headless script, or create a limited personal key.

## Agent login

Run the supported CLI with Node.js 22 or newer. It opens a dedicated sign-in page, validates its loopback callback, and stores a separate agent session. You do not need to extract a token from your browser.

```bash theme={null}
npx -y -p @crowdlisten/harness@2.4.3 crowdlisten-harness login --no-setup
```

Restart your agent after setup, then call `recall({ mode: "connection" })`. The harness refreshes its saved session and coordinates concurrent clients. Keep its credential file private; `logout` clears the local connection. This browser-assisted login requires a local browser and is not a device-code grant.

## Accounts and outside reviewers

A website session and an agent connection can be signed into different accounts. Check the identity and authorized workspace from the client doing the work. Signing into any CrowdListen account does not grant access to another account's private result.

For an outside reviewer, use an [owner-approved share or export](https://crowdlisten.com/docs/guides/results.md#review-with-another-person-or-agent). Never transfer the owner's login, password, session tokens, saved credential file, or API keys to solve a review handoff. The reviewer can return feedback, but a share does not authorize task changes or paid work.

## ChatGPT and Grok hiring connections

The [ChatGPT](https://crowdlisten.com/docs/setup/chatgpt.md) and [Grok](https://crowdlisten.com/docs/setup/grok.md) connections use OAuth with the `experts:hire` scope. The public endpoint is enabled for testing; account connection and end-to-end host acceptance remain under verification. Follow the availability notice in each setup guide.

When available, sign in through CrowdListen and approve the named app. The host receives its own limited connection credentials, not your CrowdListen password or raw account session. Workspace access and task approvals still apply: account connection does not authorize a paid work order.

Manage disconnection through the host's app settings and verify access is revoked from a new conversation. The read-only personal connections list below does not manage hiring OAuth connections. Disconnecting does not cancel existing work.

## Hosted personal agents (read-only)

Instinct, Muse and other supported HTTPS clients use a browser-approved account connection. Follow the [account-connection skill](https://crowdlisten.com/skills/connect-account/SKILL.md), approve the named agent in CrowdListen, then verify its account and authorized workspaces.

The host stores the connection securely and refreshes it automatically. It can read saved results across your current authorized workspaces; you do not create a separate connection for each result. Revoke it from **Connectors → Personal agent connections**.

This account connection remains read-only. Expert execution, spending and result decisions require a connection that supports those operations and their existing approvals. Use the full local MCP client while the hiring connections are in preview. No customer password or manually copied session token is part of agent setup. A website session and an agent connection are separate; both must resolve to an account with access to the requested workspace.

The legacy remote MCP endpoint does not implement generic OAuth enrollment. The hosted account connection above is its own explicit authorization flow, with narrower permissions.

## Personal key permissions

Sign in once to establish the account that owns the key. Create or revoke keys in [Agent access](https://crowdlisten.com/agent), or call `/api/user/keys` with a user session. Requiring that session prevents one leaked script key from minting more keys. Personal keys are limited credentials, not replacements for every product API.

Credential

Accepted operations

Boundary

`ingest` permission

Account-scoped agent setup, context recall/save, and `/agent/v1/ingest/*`

Use it to list accessible entities, check a selected entity, save or recall agent context, and ingest evidence. Processing and research can incur usage; workspace access and limits still apply.

`export` permission

`GET /agent/v1/export/*`

Raw export must be enabled for the account by CrowdListen.

`*` key

Both of the above

Does not grant user-session APIs, admin access, or additional workspaces.

User session

Product APIs and key management

Account role, workspace membership, feature access, and billing rules still apply.

The key-creation dialog creates one key with both ingest and export permissions. Existing restricted keys keep their original permissions. Raw export is currently restricted to accounts explicitly enabled by CrowdListen (the legacy database field is `whitelisted`) and administrators. Creating an export key does not enable this feature. [Contact CrowdListen](https://crowdlisten.com/contact) to request access. A 401 means authentication failed; a 403 means the credential is recognized but access is denied.

## Account recovery

Use [Reset password](https://crowdlisten.com/forgot-password) for an existing email account. If sign-in reports an unconfirmed email, use its resend control. On the signup confirmation screen, choose “Use a different email” to correct an address and submit signup again. Confirmation links opened on another device can be followed by a normal password sign-in.

[Browse every published API operation](https://crowdlisten.com/docs/api-catalogue.md). The catalogue includes connector callbacks and administrative operations; listing an endpoint does not grant permission to call it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.