Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Security / Drata API - Beta
Drata API - Beta logo

Drata API - Beta

53
AI ReadinessFoundational (C)53/100
See full scorecard
Community OpenAPI document · agent-readySecurityCompliancebearer110 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage Drata workspaces, controls, vendors, risk registers, and personnel so an agent can keep continuous compliance state synchronised with external systems.

Use for: I need to add a vendor to the Drata register, List all controls in a Drata workspace, Update the owner on a Drata control, Retrieve the personnel records tracked by Drata

Not supported: Does not run vulnerability scans, generate the audit report PDF, or replace your HRIS as a system of record - use for compliance state management within Drata only.

Drata is a continuous compliance automation platform that monitors security controls across SOC 2, ISO 27001, HIPAA, and other frameworks. The V2 public API exposes 110 operations covering workspaces, controls, control notes and owners, vendors and vendor types, risk registers, personnel, policies, devices, assets, users, roles, and custom connections. Authentication is via a bearer token, suitable for headless ingestion of evidence and synchronisation of compliance state across systems. The spec is currently published as a public beta.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Drata API - Beta to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Drata API - Beta, 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%2Fdrata.com%2Fdrata" | sh
2

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%2Fdrata.com%2Fdrata" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Drata API - Beta API.

Manage Drata workspaces and inspect their compliance scope

List, create, modify, and remove controls within a workspace

Add control notes and assign control owners across the workspace surface

Maintain a vendor register with vendor types, risk profiles, and lifecycle state

Track risk register entries and supporting documentation

Synchronise personnel, policies, devices, and assets that feed Drata's evidence engine

Configure custom connections so non-native systems become evidence sources

Use Cases

Patterns agents use Drata API - Beta API for, with concrete tasks.

★ Vendor Risk Register Sync

Mirror the company's source-of-truth vendor list into Drata's vendor register so each vendor is reflected against compliance frameworks. The agent calls the workspaces vendor endpoints to upsert vendors and vendor types, keeping risk classifications aligned with procurement state. This avoids drift between Drata and the vendor management spreadsheet.

For each vendor in procurement, upsert a Drata vendor record under the relevant workspace and set its vendor type and risk classification.

Control Ownership Reviews

Run quarterly control ownership reviews by listing controls per workspace, attaching review notes, and updating control owners where ownership has rotated. The agent uses the workspace controls and control owners endpoints to record the review outcome alongside any compensating-control commentary, keeping audit trails inside Drata rather than in scattered spreadsheets.

List controls in workspace 'wsp_42', and for each control with an outdated owner, modify the owners and add a review note dated this quarter.

Personnel and Device Hygiene

Keep Drata's personnel and device evidence current by syncing HRIS leavers and MDM device retirements through the personnel and devices endpoints. The agent removes off-boarded personnel and retires decommissioned devices so compliance evidence reflects the current population, preventing stale findings from blocking SOC 2 readiness.

Pull HRIS leavers, remove their Drata personnel records, and mark associated devices retired through the devices endpoints.

Risk Register Maintenance

Maintain the Drata risk register from incident management or GRC source data so risks are added, updated, and retired in lockstep. The agent uses the risk-registers endpoints to mirror the latest risk state, attach notes from triage reviews, and close out remediated items, giving auditors a current view at any time.

Read the latest risk triage outcomes and update each Drata risk register entry with the new status and remediation note.

AI Agent Compliance Operator

Through Jentic, an AI agent can take 'add this vendor to Drata as high risk' and resolve it to the appropriate Drata vendor creation operation without browsing docs. Jentic injects the bearer token from the vault and validates the input payload against the operation schema. End-to-end setup is under an hour from sign-up versus several days of Drata API plumbing.

Use Jentic search for 'add a Drata vendor', load the matching workspace vendor operation, and execute it with the vendor name, type, and risk classification.

Key Endpoints

110 endpoints — drata is a continuous compliance automation platform that monitors security controls across soc 2, iso 27001, hipaa, and other frameworks.

METHOD

PATH

DESCRIPTION

GET

/workspaces/{workspaceId}/controls

List controls in a workspace

POST

/workspaces/{workspaceId}/controls

Create a control

PUT

/workspaces/{workspaceId}/controls/{controlId}/owners

Modify control owners

POST

/workspaces/{workspaceId}/controls/{controlId}/notes

Create a control note

GET

/assets

List assets

POST

/custom-connections

Create a custom connection

POST

/background-checks

Create a manual background check

GET

/workspaces/{workspaceId}/controls

List controls in a workspace

POST

/workspaces/{workspaceId}/controls

Create a control

PUT

/workspaces/{workspaceId}/controls/{controlId}/owners

Modify control owners

POST

/workspaces/{workspaceId}/controls/{controlId}/notes

Create a control note

GET

/assets

List assets

POST

/custom-connections

Create a custom connection

POST

/background-checks

Create a manual background check

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.

D

Drata API – Beta 🧪

- Foundational (C)
53/100
48
Foundational Compliance
76
Developer Experience & Jentic Compatibility
34
AI-Readiness & Agent Experience
82
Agent Usability
60
Security
71
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
48

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4
91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

76

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4
32%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

34

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
74%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

82

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1
82%

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).

71

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Drata API by hand means handling its bearer auth, picking the right regional host across its US, EU, and APAC endpoints, and threading the workspace id through every path yourself. Through Jentic you install once, import Drata from the API Directory, store the token once, and your agent calls it.

Permission scoping

Drata puts the workspace id in the URL path (/workspaces/{workspaceId}/controls/...), so a rule can pin your agent to one workspace and the controls under it. You choose the operations it may call, so you can allow reading controls and adding notes while leaving out creating controls or custom connections unless you add them.

Credential isolation

Your Drata bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Drata controls' or 'add a control note', and Jentic returns the matching V2 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.

Alternative

Secureframe API

→

Secureframe is a peer compliance automation platform with similar control and evidence coverage; Drata leans into deeper vendor and risk management.

Choose Secureframe when the customer is already on Secureframe. Choose Drata when SOC 2 + extended risk register coverage is the priority.

Complementary

Snyk API

Snyk identifies application and dependency vulnerabilities; Drata records them as evidence for compliance frameworks.

Use Snyk for vulnerability detection. Use Drata to capture remediation evidence inside the compliance program.

Complementary

Tenable Attack Surface Management API

→

Tenable surfaces external exposure; Drata records the corresponding control and evidence state.

Use Tenable to enumerate exposure. Use Drata to track the related controls and risk register entries.

FAQs

Specific to using Drata API - Beta API through Jentic.

What authentication does the Drata API use?

Drata uses a bearer token in the Authorization header. Through Jentic, that token is stored encrypted in the vault and injected at execution time, so it never appears in the agent's prompt or response.

Can I manage controls programmatically with the Drata API?

Yes. The /workspaces/{workspaceId}/controls endpoints support listing, creating, retrieving, and modifying controls within a workspace. Companion endpoints handle control notes and control owners for review workflows.

How do I add a vendor to Drata through Jentic?

Run pip install jentic, search for 'add a Drata vendor', load the matching vendor creation operation, and execute it with the vendor name, vendor type, and risk classification. Jentic returns the input schema so the agent assembles a valid request without reading docs.

Can I sync personnel and devices into Drata?

Yes. The personnel and devices endpoints allow you to mirror HRIS and MDM data into Drata so its evidence engine sees the current population. This keeps SOC 2 and ISO readiness aligned with the live workforce.

Is the Drata API stable?

The V2 surface is published as a public beta. Track the source-url in the spec and validate changes before relying on the schema in production. Treat schema changes as breaking until the surface graduates from beta.

What are the rate limits for the Drata API?

The published spec does not declare explicit per-endpoint limits. Build retry-with-backoff into the client and treat 429 responses as the signal to slow down. For high-volume sync jobs, contact Drata to confirm thresholds.

Can I limit what my agent is allowed to do with the Drata API?

Yes. Because Jentic One is self-hosted and enforces your own rules, you decide which Drata operations the agent may call: you can allow it to list controls and add control notes while leaving out creating controls or custom connections. Since Drata puts the workspace id in the URL path, such as /workspaces/{workspaceId}/controls, you can also pin the agent to a single workspace and the controls under it. The token your instance holds is only ever attached to the operations you have permitted.

GET STARTED

Start building with Drata API - Beta API

Explore with Jentic One
View OpenAPI Document