Tenable MSSP Portal
Browse all Tenable APIs64
AI ReadinessAI-Aware (B)64/100
Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey34 EndpointsREST
For Agents
Programmatically create evaluation account v1, create evaluation account v2. Covers 34 operations with apiKey authentication.
Use for: I need to evaluation account v1, I want to evaluation account v2, Search for quote, Find all child accounts
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
The Tenable Managed Security Service Provider (MSSP) Portal API provides a secure and accessible way for MSSP administrators to manage and maintain multiple customer instances of Tenable products. Endpoints in the Tenable MSSP Portal API enables customers to view and manage your MSSP customer accounts. For more information about the Tenable MSSP Portal, see the [Tenable MSSP Portal User Guide](htt. The API exposes 34 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the MSSP Portal to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MSSP Portal, 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%2Ftenable.com%2Fmssp-portal" | 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%2Ftenable.com%2Fmssp-portal" | 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 MSSP Portal API.
Create evaluation account v1
List child accounts
Get child account details
Query and filter MSSP Portal records by parameters
Monitor MSSP Portal operational status and events
Use Cases
Patterns agents use MSSP Portal API for, with concrete tasks.
★ E-Commerce Operations
Use the MSSP Portal to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including create evaluation account v1, create evaluation account v2, create quote.
Call POST /mssp/accounts/eval to create evaluation account v1
Automated Accounts Management
Automate accounts operations by combining multiple MSSP Portal endpoints. Agents can create evaluation account v2 and then create quote in a single workflow.
Call POST /mssp/accounts/v2/eval to create evaluation account v2, then verify the result
AI Agent Integration via Jentic
AI agents discover and call MSSP Portal 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 apiKey tokens manually.
Search Jentic for 'create evaluation account v1', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
34 endpoints — the tenable managed security service provider (mssp) portal api provides a secure and accessible way for mssp administrators to manage and maintain multiple customer instances of tenable products.
METHOD
PATH
DESCRIPTION
POST
/mssp/accounts/eval
Create evaluation account v1
POST
/mssp/accounts/v2/eval
Create evaluation account v2
POST
/mssp/accounts/quote
Create quote
GET
/mssp/accounts
List child accounts
GET
/mssp/accounts/{account_uuid}
Get child account details
GET
/mssp/accounts/{account_uuid}/domains
List domains
POST
/mssp/accountGroup
Create account group
GET
/mssp/accountGroup
List account groups
POST
/mssp/accounts/eval
Create evaluation account v1
POST
/mssp/accounts/v2/eval
Create evaluation account v2
POST
/mssp/accounts/quote
Create quote
GET
/mssp/accounts
List child accounts
GET
/mssp/accounts/{account_uuid}
Get child account details
GET
/mssp/accounts/{account_uuid}/domains
List domains
POST
/mssp/accountGroup
Create account group
GET
/mssp/accountGroup
List account groups
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.
M
MSSP Portal
- AI-Aware (B)64/100
74
Foundational Compliance77
Developer Experience & Jentic Compatibility45
AI-Readiness & Agent Experience94
Agent Usability50
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
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).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
77
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
37%
Example Density
How richly the API is illustrated with examples.
97%
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.
45
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
60%
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.
20%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
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 Tenable MSSP Portal by hand means learning its X-ApiKeys header auth (accessKey plus secretKey) against the cloud.tenable.com host and handling account and account-group calls yourself. Through Jentic you install once, import MSSP Portal from the API Directory, store the key pair once, and your agent calls it.
Permission scoping
MSSP Portal puts the account id in the URL path (/mssp/accounts/{account_uuid}), so a rule can pin your agent to one managed account: it can read that account and its domains and nothing else. You choose the operations it may call, so creating evaluation accounts or quotes is not included unless you add it.
Credential isolation
Your MSSP Portal access key and secret key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list managed accounts' or 'get an account's domains', and Jentic returns the matching MSSP Portal 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
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using MSSP Portal API through Jentic.
What authentication does the MSSP Portal use?
The MSSP Portal uses an API key passed in the `X-ApiKeys` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create evaluation account v1 with the MSSP Portal?
Yes. Use the POST /mssp/accounts/eval endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the MSSP Portal?
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 create evaluation account v1 through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create evaluation account v1'. Jentic returns the matching MSSP Portal operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the MSSP Portal have?
The MSSP Portal exposes 34 endpoints covering accounts, account groups, child containers operations.
Can I limit what my agent is allowed to do with the MSSP Portal API?
Yes. Because you run Jentic One yourself, your own rules decide which MSSP Portal operations and credentials the agent may use. Since the account id sits in the URL path (/mssp/accounts/{account_uuid}), you can pin the agent to a single managed account so it only reads that account and its domains through GET /mssp/accounts/{account_uuid} and the list-domains call. You choose the operations it may reach, so creating evaluation accounts or quotes stays off limits unless you explicitly allow it.
GET STARTED