Guides
Publishing a run
Executions are private. Publishing one is opt-in, per run, and redacts by selecting rather than removing.
Every execution is private to the key that ran it. That is not a setting — it is the default, because an execution records the address somebody asked about.
POST
/api/v1/feed/{execution_id}/publishAPI keyOpt one run into the public feed
Only the key that ran an execution may publish it, so nobody can expose somebody else's analysis.
What a stranger sees
The public shape is built by selecting fields, never by deleting them. That direction matters: a field added upstream later cannot leak by accident, because it is not on the list.
- The kind of run, its status, and how long it took.
- Step labels and durations, in human phases rather than internal stage names.
- Counts — findings and sources.
- Never the address, the request text, the key, or any vendor name.
| Route | Auth | Does |
|---|---|---|
GET /api/v1/feed | None | Published runs, newest first |
GET /api/v1/feed/stream | None | The same feed as server-sent events |