Secureframe API
✓ Official Vendor SpecSecurityCompliancebearer10 EndpointsREST
For Agents
Programmatically list users, list compliance frameworks. Covers 10 operations with bearer authentication.
Use for: I need to users, I want to compliance frameworks, Search for controls, Find all control
Not supported: Does not handle payments, communications, or crm — use for security only.
Secureframe API for compliance automation, risk management, and security posture monitoring. Manage compliance frameworks, audits, and security controls. The API exposes 10 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Secureframe API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Secureframe 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Secureframe API.
List Users
Get Control
Create Vendor
Query and filter Secureframe API records by parameters
Monitor Secureframe API operational status and events
Use Cases
Patterns agents use Secureframe API for, with concrete tasks.
★ Security Operations
Use the Secureframe API to perform security operations programmatically. The API provides 10 endpoints covering core functionality including list users, list compliance frameworks, list controls.
Call GET /users to list users
Automated Audits Management
Automate audits operations by combining multiple Secureframe API endpoints. Agents can list compliance frameworks and then list controls in a single workflow.
Call GET /compliance-frameworks to list compliance frameworks, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Secureframe API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'list users', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
10 endpoints — secureframe api for compliance automation, risk management, and security posture monitoring.
METHOD
PATH
DESCRIPTION
GET
/users
List Users
GET
/compliance-frameworks
List Compliance Frameworks
GET
/controls
List Controls
GET
/controls/{control_id}
Get Control
GET
/audits
List Audits
POST
/vendors
Create Vendor
GET
/vendors
List Vendors
POST
/evidence
Upload Evidence
GET
/users
List Users
GET
/compliance-frameworks
List Compliance Frameworks
GET
/controls
List Controls
GET
/controls/{control_id}
Get Control
GET
/audits
List Audits
POST
/vendors
Create Vendor
GET
/vendors
List Vendors
POST
/evidence
Upload Evidence
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Secureframe API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'list users') and Jentic returns the matching Secureframe API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Secureframe API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Snyk
Alternative security API
Choose Snyk when you need a different approach to security operations
FAQs
Specific to using Secureframe API through Jentic.
What authentication does the Secureframe API use?
The Secureframe API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I list users with the Secureframe API?
Yes. Use the GET /users endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Secureframe API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I list users through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'list users'. Jentic returns the matching Secureframe API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Secureframe API have?
The Secureframe API exposes 10 endpoints covering audits, compliance, controls operations.
GET STARTED