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

> ## Agent Instructions
> SeedOps CLI browser login is the default for agents. Use --limit 1–50 to retrieve only needed signals. Read /agent-setup/prompt.md for setup. Never request credentials in a prompt.

# API keys

> Create a read-only key for a server or unattended integration.

Create a key at [API keys](https://app.seedops.co/api). Give it a name and expiry. Copy the secret when it is created: SeedOps shows the full key only once. If you lose it, create a new key.

Keep API keys in a secret environment variable, such as `SEEDOPS_API_KEY`. Never put them in browser code, URLs, Git, or an agent prompt.

```bash theme={null}
curl --get 'https://app.seedops.co/api/v1/signals' \
  --header "Authorization: Bearer $SEEDOPS_API_KEY" \
  --data-urlencode 'q=hiring' \
  --data-urlencode 'limit=5'
```

Every REST API data request requires a valid key. A browser cookie or CLI session token cannot replace an API key. Keys can read published signals and company profiles; they cannot modify source data or manage keys.

## Revoke or delete

**Revoke** immediately prevents the key from authenticating. **Delete** removes it from the visible key list and also prevents future authentication. Historical usage remains available after a key is deleted.

An expired, revoked, deleted, or missing key is rejected. API usage and credits remain separate from the CLI's browser-login subscription allowance.

For agent onboarding without a manually created key, use [Connect your agent](/agent-setup/prompt).


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