> ## Documentation Index > Fetch the complete documentation index at: https://docs.zebratruth.ai/llms.txt > Use this file to discover all available pages before exploring further. # List available agents > Discover all available compliance agents. Agents are added regularly — always use this endpoint to discover dynamically rather than hardcoding agent IDs. ## OpenAPI ````yaml /openapi/zebratruth-v1.yaml get /agents openapi: 3.1.0 info: title: ZebraTruth Compliance API version: 1.0.0 description: > AI-powered compliance checking for advertising content. Check text and images against jurisdiction laws, platform policies, and rights clearance requirements. Results include embeddable annotations mapped to content locations (text spans, video timestamps, image regions). contact: name: ZebraTruth Support email: support@zebratruth.ai url: https://developers.zebratruth.ai license: name: MIT url: https://opensource.org/licenses/MIT servers: - url: https://api.zebratruth.ai/v1 description: Production security: - bearerAuth: [] tags: - name: Video Compliance description: > **Primary endpoint.** Async compliance analysis for video ads. 3-step flow: get an upload URL, upload the video bytes, submit for analysis. Poll or receive an HMAC-signed webhook with the report. Returns timestamped findings citing stable evidence IDs (`audio_NNN`, `frame_NNN`, `ocr_NNN`, `signal_NNN`). 3-180 second videos. mp4 / webm / quicktime. Built for ad agencies and creators. - name: Authentication description: Validate API keys and check account status - name: Compliance description: >- Run compliance checks on text + image content (sync). For video, use the Video Compliance endpoints above. - name: Agents description: Discover and invoke individual compliance agents - name: Jobs description: Poll async job status and view execution traces - name: Reports description: Retrieve and replay compliance reports - name: Observability description: Request logs and webhook delivery status - name: Billing description: Subscriptions, plan changes, and credit balance - name: Documents description: Extract text from PDF and Word documents before or as part of a check - name: Check History description: List and retrieve past compliance checks for the workspace - name: Provenance description: Inspect and sign Content Credentials (C2PA) on images and video - name: Corpus description: >- Review queue for proposed changes to the governed legal corpus (dashboard session) - name: Webhooks description: Saved webhook endpoints (dashboard session) and delivery logs paths: /agents: get: tags: - Agents summary: List available agents description: > Discover all available compliance agents. Agents are added regularly — always use this endpoint to discover dynamically rather than hardcoding agent IDs. operationId: listAgents responses: '200': description: List of available agents content: application/json: schema: type: array items: $ref: '#/components/schemas/AgentDefinition' '401': $ref: '#/components/responses/Unauthorized' components: schemas: AgentDefinition: type: object properties: id: $ref: '#/components/schemas/ComplianceAgentId' name: type: string example: Advertising Law description: type: string example: Checks FTC, UCPD, and advertising regulations phase: type: integer enum: - 1 - 2 - 3 description: Pipeline phase (for full mode ordering) inputType: type: string enum: - text - image - both version: type: string example: 1.1.0 annotationSupport: type: array items: $ref: '#/components/schemas/AnnotationType' description: Annotation types this agent can emit. ComplianceAgentId: type: string enum: - ai-laws - jurisdiction-detection - advertising-law - platform-policy - metadata-labeling - rights-clearance - rights-clearance-text - rights-clearance-image - compliance-score - fs-compliance-financial-promotion - fs-compliance-advisory-suitability - fs-compliance-credit-servicing - fs-compliance-markets-trading - fs-compliance-financial-crime - fs-compliance-ai-governance - financial-services-compliance - pharma-healthcare-compliance description: > Agent identifier. Use `GET /agents` to discover all available agents dynamically. The list is filtered to the industries your workspace has selected. **Financial services.** The six `fs-compliance-*` agents correspond one-to-one to the review scopes (`financial_promotion` → `fs-compliance-financial-promotion`, and so on). In a full check they are selected with `reviewScopes`. Via `POST /agents/{agentId}` only `fs-compliance-financial-promotion` can be invoked directly today; the other five return 400 `review_scope_not_enabled` on direct invocation and must run through `POST /compliance/check`. `financial-services-compliance` is a read-only alias of `fs-compliance-financial-promotion` accepted for older clients. **Pharma and healthcare.** `pharma-healthcare-compliance` runs for workspaces on the `pharma_healthcare` industry and honours `regulatedActor`. `ai-laws` is the canonical id; `jurisdiction-detection` is accepted as an input alias for backward compatibility with historical clients. New integrations should use `ai-laws`. **Note on rights-clearance variants.** `GET /agents` exposes two registered agents for rights clearance: `rights-clearance-text` and `rights-clearance-image` — invoke them via `POST /agents/{agentId}` using those qualified IDs. On **check response objects**, however, text rights-clearance findings carry the bare `agentId: "rights-clearance"`. Treat bare `rights-clearance` and `rights-clearance-text` as the same logical pipeline — the bare form is the value that appears on `checks[]` entries from that agent. AnnotationType: type: string enum: - text-span - timeline - image-region - global responses: Unauthorized: description: | Invalid, missing, or expired API key. Standard error envelope — read `message` for the human-readable reason. content: application/json: schema: type: object description: Standard error envelope. required: - statusCode - message properties: error: type: boolean example: true url: type: string format: uri example: https://api.zebratruth.ai/v1/whoami statusCode: type: integer example: 401 statusMessage: type: string example: Invalid API key message: type: string description: Canonical human-readable reason — pattern-match on this field. example: Invalid API key securitySchemes: bearerAuth: type: http scheme: bearer description: | API key starting with `zt_live_` (production) or `zt_test_` (sandbox). Get your key at https://developers.zebratruth.ai ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.