Clearpolicy App ClearPolicy API
70
AI ReadinessAI-Aware (A-)70/100
Official vendor OpenAPI document · agent-readySecurityCompliancebearer9 EndpointsREST
For Agents
Send policy attestation requests, manage people and groups, and list the documents in an organization. Reads the current user and token role so an agent knows which operations it may call.
Use for: Send an attestation request for a policy document to our staff, List all people in my organization, Add a new employee to our people directory, Add a person to a specific group
Not supported: Does not handle payroll, time off, or e-signature capture. Use for policy attestation requests and people and group management only.
The ClearPolicy API manages an organization's people, groups, and policy documents and sends attestation requests asking people to acknowledge a document. It lists and adds people, moves them in and out of groups, and lists the documents available to attest. Tokens are organization-scoped, and the current-user endpoint reports the token's role so an integration knows which operations it may call.
Install Jentic One Beta
Connect the ClearPolicy API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClearPolicy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclearpolicy.app%2Fclearpolicy" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fclearpolicy.app%2Fclearpolicy" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with ClearPolicy API.
Send attestation requests asking people to acknowledge a document
List people in your organization and add a new person
Add people to a group or remove a person from one
List the documents available for attestation
List groups and look up an individual person
Read the current user and the token's role
Use Cases
Patterns agents use ClearPolicy API for, with concrete tasks.
★ Agent-Driven Policy Attestation Rollout
An AI agent connected to the ClearPolicy API can roll out a policy for sign-off. It lists the documents available to attest, lists the people who need to acknowledge the policy, and sends an attestation request so each person is asked to confirm they have read it. This turns a manual send-and-chase into an automated rollout the agent can repeat whenever a policy changes.
List the available documents, then send an attestation request for the chosen policy document to the organization's people
People Directory Onboarding
When a new hire joins, their record and group memberships must exist before policies can be assigned. The ClearPolicy API lets an agent add the person with the create-person endpoint and add them to the right groups, so onboarding automation keeps the people directory current without a manual admin step. The agent can read back the person record to confirm the add.
Add a new person with their name and email, then add that person to the group named Engineering
Offboarding Group Removal
When someone leaves or changes teams, they should drop out of the groups that assign them policies. The ClearPolicy API exposes a remove-person operation on a group, so an offboarding agent can remove a departing person from each group they belonged to, keeping attestation assignments accurate. Group membership is addressed by group and person id, so the removal is precise.
Remove the person with the given id from the group with the given id
Document and Group Inventory
Compliance teams need to know which policies exist and which groups they map to. The ClearPolicy API lists documents and groups so an agent can build an inventory of the organization's policies and the groups responsible for each, then flag any group that has no document assigned. It reads from organization-scoped endpoints so the view is the whole organization.
List all documents and all groups and return a table pairing each group with the policies it is responsible for
Key Endpoints
9 endpoints — the clearpolicy api manages an organization's people, groups, and policy documents and sends attestation requests asking people to acknowledge a document.
METHOD
PATH
DESCRIPTION
POST
/attestation-requests
Send an attestation request
GET
/people
List people
POST
/people
Add a person
GET
/people/{id}
Get a person
GET
/documents
List documents
GET
/groups
List groups
POST
/groups/{group}/people
Add people to a group
DELETE
/groups/{group}/people/{person}
Remove a person from a group
POST
/attestation-requests
Send an attestation request
GET
/people
List people
POST
/people
Add a person
GET
/people/{id}
Get a person
GET
/documents
List documents
GET
/groups
List groups
POST
/groups/{group}/people
Add people to a group
DELETE
/groups/{group}/people/{person}
Remove a person from a group
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
ClearPolicy API
- AI-Aware (A-)70/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility53
AI-Readiness & Agent Experience94
Agent Usability60
Security88
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
2%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
53
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
62%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
88
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
88%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ClearPolicy API by hand means creating a bearer token with the api:use scope, tracking which role your token holds so writes do not 403, and honoring the per-token rate limit. Through Jentic you install once, import ClearPolicy from the API Directory, store the token once, and your agent calls it.
Permission scoping
ClearPolicy puts the group and person id in the URL path (/groups/{group}/people/{person}), so a rule can pin your agent to the people and group operations you pick. You can let it list people, groups, and documents without granting the add-person, remove-person, or send-attestation operations.
Credential isolation
Your ClearPolicy token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'send a policy attestation request' or 'list people in the organization', and Jentic returns the matching ClearPolicy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ClearPolicy API through Jentic.
What authentication does the ClearPolicy API use?
The ClearPolicy API authenticates with a bearer token per its OpenAPI spec: a token created in ClearPolicy settings with the api:use scope, sent as an Authorization: Bearer header. Tokens are organization-scoped, and a Group Manager token can call the current-user endpoint while owner and administrator tokens reach the rest. Through Jentic the token is stored once by your own self-hosted instance and injected at call time, so it never sits in your agent's prompt or logs.
Is there a ClearPolicy MCP server?
You do not need an MCP server to give your agent the ClearPolicy API. Jentic connects it directly from the API Directory: import it, store your API token once, and your agent calls the people, groups, documents, and attestation operations on demand. Operations are discovered when needed, so no extra server's tool definitions are loaded into the agent's context.
Can I limit what my agent is allowed to do with the ClearPolicy API?
Yes. Write a rule that allows only the list-people, list-groups, and list-documents operations, so the agent can read your directory and policies but cannot add or remove people or send an attestation request. Every call it makes is logged, so you can audit exactly what the agent touched.
Can I send policy attestation requests with the ClearPolicy API?
Yes. Send an attestation request with POST /attestation-requests, which asks the chosen people to acknowledge a document. You can list the documents available to attest at /documents and list the people who should receive the request at /people, so an agent can assemble and send a rollout in a few calls.
What are the rate limits for the ClearPolicy API?
The OpenAPI spec states each API token is limited to 60 requests per minute. A 429 response carries a Retry-After header to wait on, and the X-RateLimit headers report your remaining allowance so an agent can pace its calls.
How do I send a policy attestation with the ClearPolicy API through Jentic?
Search Jentic for 'send a policy attestation request' and it returns the POST /attestation-requests operation with its input schema. Pass the document and the people who must acknowledge it and the agent sends the request. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED