> ## 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.

# Usage and errors

> Separate CLI-session and API-key analytics, monthly CLI allowances and prepaid API records.

Free accounts have unlimited Web browsing and can run 10 Web searches or filter applications per calendar month (UTC). Pagination and count-only follow-ups reuse the same search; a new search or filter application uses one. They receive **500 CLI records and 100 API records** once per account; these separate allowances never reset. Browser-login CLI access and API-key access have independent usage ledgers and analytics. Paid plans include unlimited Web access and a separate monthly CLI allowance: 10,000 records for $49, 50,000 for $199, or 100,000 for $349. API access is separate prepaid usage at **$0.005 per returned record\*\*, with a custom dollar amount starting at **\$10 for 2,000 records**. Existing account-access restrictions and security rate protection still apply.

Web, CLI, and API analytics appear on [Usage](https://app.seedops.co/usage). Connected devices remain on [AI agents](https://app.seedops.co/agents).

Opening the default Web page consumes no data. Paid Web browsing, pages, searches and filters are unlimited. CLI and API data consumption count actual returned records. A page of 50 activities adds 50 records. An activity detail adds one activity record; a company profile adds one company record. Empty results, count-only totals, filter catalogues, and failed requests add no records. Successful data requests are counted separately for analytics, without a request quota for now. Usage and identity checks are free.

Use `seedops usage` for browser-login usage and `seedops usage --api` for API-key usage. The `billing` object contains the current record allowance or prepaid balance. Top-level request counters are operational analytics, not data credits.

## Reliable retries

Send an `Idempotency-Key` of 8–128 letters, digits, underscores or hyphens, or use `--idempotency-key` in the CLI. Repeat it only for the same request and credential. Successful cached replays within 24 hours do not count another request or duplicate records. Failed requests release their reservation.

| Status | Meaning |
| - | - |
| 400 | Invalid input or filters |
| 401 | Missing, expired or revoked credentials |
| 402 | Subscription allowance or API balance required |
| 403 | Restricted or disabled account |
| 409 | Request conflict, in-progress retry, or browser approval pending |
| 429 | Temporary security rate protection |
| 503 | Temporary service failure |

Respect `Retry-After`. CLI errors are JSON on stderr with a nonzero exit code.


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