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

# Request logs

> Trace CLI and API requests using their request IDs.

Every CLI and API request produces a structured Cloudflare Worker event, including authentication failures, validation errors and successful requests. CLI events use `seedops-cli-request`; API-key requests use `seedops-api-request`.

Events include:

* Request ID, route template, HTTP method, status and duration.
* A hashed account reference when authentication succeeded.
* Keyword or semantic search mode.
* Returned activity and company counts, consumed records, replay status and an error code when applicable.

Events exclude authentication headers, access tokens, refresh tokens, API keys, email addresses, raw search text and returned signal content. Routes use templates rather than individual company slugs or signal IDs.

## Reporting a problem

Failed CLI commands return a JSON error on stderr containing `requestId`. Share that ID and the command type with support. API responses also include `x-request-id`.

Usage, credits and allowances remain durable in Neon and appear on the Usage and Billing pages. Worker logs are operational diagnostics, not the billing ledger. A replay can log returned records while `consumedRecords` stays zero.

## For operators

Open the production `seedops` Worker in Cloudflare and use Observability → Logs to find the request ID or event name. Existing Workers Logs collection is enabled at full request sampling; retention and platform usage follow the Cloudflare account’s plan. Live Tail can verify recent events. Access to all-account diagnostic logs remains restricted to Cloudflare operators; customers do not receive other accounts’ logs.

A single client invocation may generate more than one server event if it first refreshes a session or retries an expired access token. Use `requestId` for one HTTP request and the account reference for related authenticated traffic. Idempotent replays are explicitly marked.


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