Blackkitetech Black Kite API
Official vendor OpenAPI document · agent-readySecurityComplianceoauth237 EndpointsREST
For Agents
Manage monitored companies in Black Kite, pull cyber risk scores and trends, and generate vendor risk reports. Useful for agents that automate third-party risk monitoring.
Use for: Add a new vendor for Black Kite monitoring, Get the cyber risk summary for a monitored company, Retrieve the monthly technical risk trend for a vendor, Generate a Black Kite report for a third party
Not supported: Does not handle internal vulnerability scanning, endpoint protection, or SIEM ingestion - use for third-party cyber, compliance, and financial risk monitoring only.
The Black Kite API is the programmatic surface of Black Kite's cyber risk intelligence platform, used to assess third-party and supply chain risk from technical, compliance, and financial perspectives. It exposes operations to manage the catalogue of monitored companies and their attack-surface assets (domains, subdomains, IPs, IP blocks, ASNs, cloud associations), pull risk score summaries and monthly trends, and generate or download company risk reports. The published rate limit is 60 requests per minute.
Install Jentic One Beta
Connect the Black Kite API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Black Kite 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%2Fblackkitetech.com%2Fblackkite" | 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%2Fblackkitetech.com%2Fblackkite" | 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 Black Kite API.
Add, list, and remove companies in the Black Kite monitoring catalogue
Pull a company's technical, compliance, and financial risk score summary
Track monthly technical and financial risk trends per monitored company
Generate, poll, and download Black Kite company risk reports on demand
Inspect attack-surface assets per company - domains, subdomains, IPs, ASNs, cloud associations
Search the company catalogue with structured filters before drilling into details
Use Cases
Patterns agents use Black Kite API for, with concrete tasks.
★ Third-Party Vendor Onboarding Risk Check
When procurement onboards a new supplier, the integration calls POST /api/v2/companies to add the vendor to the Black Kite watchlist, then GET /api/v2/companies/{id}/summary to pull the initial risk scores. Procurement and security review the technical, compliance, and financial dimensions before the contract is signed. Repeat the call monthly to detect drift.
Call POST /api/v2/companies with the new vendor name and primary domain, wait for the initial scan, then call GET /api/v2/companies/{id}/summary and report the technical and compliance scores.
Supply Chain Risk Monitoring Dashboard
Build a monitoring dashboard that pulls GET /api/v2/companies/{id}/trend/technical and /trend/financial for every monitored vendor on a monthly cadence. The dashboard highlights vendors whose technical or financial risk worsened month over month, which feeds the security and procurement risk reviews. Black Kite's 60 rpm limit is comfortable for portfolios in the low hundreds.
Iterate the company list from GET /api/v2/companies, call /trend/technical and /trend/financial for each, and emit a list of vendors with month-over-month deterioration above 5 points.
Automated Risk Report Generation
Compliance teams trigger a Black Kite report on a vendor, wait for it to be ready, and store the PDF or download link in their GRC system. The flow is POST /api/v2/companies/{id}/report-generate, poll GET /api/v2/companies/{id}/report-status, then GET /api/v2/companies/{id}/report-download or /report/{type}. This replaces the manual click-through in the Black Kite UI.
Call POST /api/v2/companies/{id}/report-generate, poll /report-status until done, then GET /report-download and store the link in the GRC system of record.
Attack Surface Inventory Sync
Sync the Black Kite-attributed assets for a vendor - domains, subdomains, IPs, IP blocks, ASNs, and cloud associations - into the in-house CMDB or ASM tool. Use the per-company asset endpoints (e.g. /api/v2/companies/{id}/domains, /subdomains, /ips, /ipblocks, /asn) to enumerate and reconcile differences. PATCH endpoints let the team mark false positives.
For a given vendor id, call GET /api/v2/companies/{id}/domains and /subdomains, diff against the CMDB, and PATCH the status of any asset the team has marked invalid.
Agent-Driven Vendor Risk Lookup via Jentic
An AI agent supporting the security team gets a question like 'what's the current cyber risk score for Acme Inc?' and uses Jentic to find the Black Kite summary operation. Jentic returns the schema, the agent calls /api/v2/companies/{id}/summary, and answers with the technical, compliance, and financial scores. The Black Kite OAuth credentials never enter the agent's prompt.
Use Jentic search for 'get the cyber risk summary for a monitored company', load the schema, then execute GET /api/v2/companies/{id}/summary and return the headline scores.
Key Endpoints
37 endpoints — the black kite api is the programmatic surface of black kite's cyber risk intelligence platform, used to assess third-party and supply chain risk from technical, compliance, and financial perspectives.
METHOD
PATH
DESCRIPTION
GET
/api/v2/companies
List monitored companies
POST
/api/v2/companies
Add a company for monitoring
GET
/api/v2/companies/{id}/summary
Get company risk score summary
GET
/api/v2/companies/{id}/trend/technical
Monthly technical risk trend
POST
/api/v2/companies/{id}/report-generate
Generate a company report
GET
/api/v2/companies/{id}/report-download
Download a generated report
GET
/api/v2/companies/{id}/domains
List domains attributed to a company
GET
/api/v2/companies
List monitored companies
POST
/api/v2/companies
Add a company for monitoring
GET
/api/v2/companies/{id}/summary
Get company risk score summary
GET
/api/v2/companies/{id}/trend/technical
Monthly technical risk trend
POST
/api/v2/companies/{id}/report-generate
Generate a company report
GET
/api/v2/companies/{id}/report-download
Download a generated report
GET
/api/v2/companies/{id}/domains
List domains attributed to a company
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Black Kite API by hand means running its OAuth 2.0 client-credentials flow, minting and rotating short-lived bearer tokens against the app.blackkitetech.com host, and handling retries across risk-monitoring calls yourself. Through Jentic you install once, import Black Kite from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Black Kite puts the company id in the URL path (/api/v2/companies/{id}/summary), so a rule can pin your agent to one company: it can read that company's summary, technical trend, and domains and nothing else. You choose the operations it may call, so report generation with POST /api/v2/companies/{id}/report-generate is not included unless you add it.
Credential isolation
Your Black Kite OAuth client id and secret are stored once, encrypted, by your own Jentic One instance, which mints and rotates the bearer tokens and injects them at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a company cyber risk summary' or 'list monitored companies', and Jentic returns the matching operation with its input and response 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 Black Kite API through Jentic.
What authentication does the Black Kite API use?
OAuth 2.0 with the client_credentials flow. Tokens are issued from https://app.blackkitetech.com/oauth/token. Through Jentic the OAuth client id and secret are stored in the encrypted vault, Jentic mints and rotates the bearer token, and the agent receives a scoped Jentic token instead of the raw client credentials.
Can I add a vendor for monitoring with the Black Kite API?
Yes. POST /api/v2/companies adds a company to your monitored catalogue. Once added, GET /api/v2/companies/{id}/summary returns the technical, compliance, and financial risk scores after the initial scan completes.
What are the rate limits for the Black Kite API?
60 requests per minute, as documented in the API description. For portfolio sweeps over more than a few dozen companies, throttle the loop or use the bulk-style search endpoint POST /api/v2/companies/search to reduce call counts.
How do I generate and download a Black Kite report through Jentic?
Install with pip install jentic, then use Jentic search with 'generate a Black Kite report for a third party'. Jentic resolves the three-step flow: POST /api/v2/companies/{id}/report-generate, poll /report-status, then GET /report-download. The OAuth token is managed inside Jentic.
Can I see the attack-surface assets attributed to a vendor?
Yes. Per-company endpoints like GET /api/v2/companies/{id}/domains, /subdomains, /ips, /ipblocks, /asn, and /clouds expose the assets Black Kite has attributed. PATCH variants let you correct false positives.
Is the Black Kite API free?
No. Black Kite is a paid platform - API access is included with active subscriptions. There is no public free tier; OAuth client credentials are issued to customer accounts only.
Can I limit what my agent is allowed to do with the Black Kite API?
Yes. Because Jentic One is self-hosted and enforces your own rules, you decide exactly which Black Kite operations and credentials your agent may use. Since the company id sits in the URL path (for example GET /api/v2/companies/{id}/summary), you can pin the agent to a single company and to read-only calls like its risk summary, technical trend, and domains. Write actions such as POST /api/v2/companies/{id}/report-generate stay out of reach unless you explicitly add them.
GET STARTED