Skip to main content
orgs list and orgs get operate on the organizations your credential can see. orgs assets list accepts --org <slug> so staff and multi-org callers can target any organization they have access to; org-scoped API keys can omit the flag and use their own organization. orgs asset-groups list still operates on the organization tied to your API key.

orgs list

List organizations with their subscription status and per-service active flag. All filters compose with AND. Services are reporting, reviewing, protection, takedowns, detection, and darkWebMonitoring. automated is reported for takedowns only — that is the one service where manual-versus-automated changes real platform behavior.

orgs get

Get a single organization by slug. Returns the same shape as one row of orgs list.
The caller must have access: an organization-scoped API key must match the slug, and a user session or key needs an active membership unless the user is staff.

orgs assets list

List the assets in an organization’s allowlist. Pass --org <slug> to choose one, or omit it to use the organization tied to your API key. An organization-scoped API key that passes --org for a different organization is rejected with a 403, and an unknown slug returns a 404 — the same way reports list --org already behaves.

orgs asset-groups list

List your organization’s asset groups with per-group asset counts.

brands list

brands is a separate top-level command that lists the brands available to you.
The --type value is case-insensitive. Brand IDs from this listing are what --brand and --brand-id accept elsewhere — in reports list, detections list, takedowns list, metrics, and proposals review.