# Integrations & API

Protege offers enterprise integration options for teams that want to connect document review and compliance workflows to their own systems, automations, or agent frameworks.

## What Is Available

* **External Review API**: Submit text and file-based document reviews, poll asynchronous jobs, and retrieve structured review findings.
* **Reference Data Access**: Discover tenant-scoped brands, policies, policy groups, and document evaluation types required to drive integrations.
* **Monitoring Workflows**: Manage scanner jobs and retrieve report data for ongoing web and content monitoring use cases.
* **Implementation Support**: Enterprise customers can receive sandbox access, sample requests, and enablement support during setup.

## Where Agent Skills Fit

An agent skill can be a useful accelerator, but it is usually **not** the primary enterprise artifact.

Agent skills work best when a client already has an agent platform and wants a lightweight wrapper that gives their agents fast access to Protege review workflows. In that setup, the skill acts as a convenience layer over the Protege API.

For most enterprise evaluations, the stronger primary deliverable is:

1. clear API documentation
2. a tested sandbox workflow
3. sample requests or a starter client
4. a concise business-case narrative showing why Protege outperforms a DIY reviewer

Then, if the client is actively standardizing on an agent platform, add an agent skill as an optional starter artifact rather than the core integration surface.

## Recommended Enterprise Package

For customer onboarding or benchmark exercises, we recommend sharing:

* **Business case overview** explaining why Protege is broader than a point document reviewer
* **API and sandbox guide** for technical validation
* **Example review workflow** showing file upload, async polling, and findings retrieval
* **Optional agent skill** for teams that want to expose Protege to their internal agents quickly

## Access and Enablement

If you need an API key, help selecting a `documentEvaluationTypeId`, or sample requests for your environment, contact the Protege team through your shared enterprise support channel or email <founders@tryprotege.com>.

The detailed endpoint reference for document reviews remains available in the Document Review section:

{% content-ref url="/pages/wH4eclB0efC3ka5ulg6i" %}
[API Reference](/review/getting-started/api-reference.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook.tryprotege.com/review/enterprise-features/integrations-and-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.