Install Jentic One Beta

Connect the Loadster API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loadster 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.

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%2Floadster.com%2Floadster" | sh

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%2Floadster.com%2Floadster" | 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 Loadster API.

Launch a load test from a scenario's trigger code with startTestRunByShortcut and an optional label, then poll its status by test code

Read a finished load test's report and the advice Loadster generates for it with getTestReportData and getTestAdvice

Stop a running cloud load test gracefully with stopCloudTest or immediately with killCloudTest

Import a JMeter, k6, or Locust script into a Loadster script with importScript

GET STARTED

Start building with Loadster API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Loadster API for, with concrete tasks.

★ Agent-run load tests through Jentic

A coding agent finishing a performance change asks Jentic for the Loadster operation that launches a test, calls startTestRunByShortcut with the scenario's trigger code, then polls getTestStatusByShortcut and reads getTestReportDataByShortcut once the run finishes. The personal access token used for project and monitor operations stays in your self-hosted Jentic One instance.

Search Jentic for 'launch a Loadster load test', call startTestRunByShortcut with the scenario shortcut and label 'release-42', then poll getTestStatusByShortcut until it finishes and summarize the report

Load test review and advice

After a test, an agent calls getTestReportData for the project and test ids to read response times, errors, and hit counts, then getTestAdvice for Loadster's own guidance on the finished test. Notes can be written back to the report with updateTestReportData.

Call getTestReportData for projectId 'p1' and testId 't9', then call getTestAdvice for the matching cloud test id and list the top issues

Migrating scripts from other tools

Teams moving to Loadster call importScript on a target script with source set to the original JMeter, k6, or Locust script, optionally replacing existing steps and setting a baseUrl. duplicateScript copies a working script into another project for reuse.

Call importScript for projectId 'p1' and scriptId 's3' with the k6 script as source and replace true

Synthetic monitoring and incidents

Create a monitor with createMonitor pointing at a repository project and script, set its frequency and acceptable response-time ranges, and attach notification policies. getIncidents and getMonitorPeriods show when it failed, and maintenance windows stop alerts during planned deploys.

Call getIncidents with includeResolved false, then call getMonitorPeriods for each affected monitor id over the last day

Key Endpoints

85 endpoints — the loadster api works with the same projects, scripts, scenarios, datasets, monitors, and load test results as the loadster dashboard.

METHOD

PATH

DESCRIPTION

POST

/s/{shortcut}

Launch a load test from a trigger code

GET

/t/{shortcut}/status

Get a load test's status by test code

GET

/projects/{projectId}/tests/{testId}/report

Get a load test report

GET

/cloud/tests/{id}/advice

Get advice on a finished load test

POST

/projects/{projectId}/scripts/{scriptId}/actions/import

Import a JMeter, k6, or Locust script

POST

/player/script/actions/start

Play a script once

POST

/monitoring/monitors

Create a monitor

GET

/monitoring/incidents

List incidents

POST

/s/{shortcut}

Launch a load test from a trigger code

GET

/t/{shortcut}/status

Get a load test's status by test code

GET

/projects/{projectId}/tests/{testId}/report

Get a load test report

GET

/cloud/tests/{id}/advice

Get advice on a finished load test

POST

/projects/{projectId}/scripts/{scriptId}/actions/import

Import a JMeter, k6, or Locust script

POST

/player/script/actions/start

Play a script once

POST

/monitoring/monitors

Create a monitor

GET

/monitoring/incidents

List incidents

Why Jentic?

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

Setup

Wiring Loadster by hand means knowing which calls take the personal access token and which trigger-code endpoints need none, then polling test status and fetching reports yourself. Through Jentic you install once, import Loadster from the API Directory, store the token once, and your agent calls it.

Permission scoping

Loadster puts projectId in the URL path for scripts, scenarios, datasets, tests, and runs, so a rule can pin your agent to one project: it can work under /projects/{projectId}/ for that project and nothing else. You choose the operations it may call, so destructive ones like deleteProject or killCloudTest are not included unless you add them.

Credential isolation

Your Loadster personal access 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 'launch a load test' or 'list monitoring incidents', and Jentic returns the matching Loadster operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Loadster API through Jentic.

What authentication does the Loadster API use?

Per its OpenAPI spec, the Loadster API uses an HTTP bearer scheme carrying a personal access token from the Loadster dashboard, sent as `Authorization: Bearer`. The trigger-code endpoints under /s/ and /t/ need no token, because the code in the path authorizes the request. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

Can I start a load test from CI with the Loadster API?

Yes. POST /s/{shortcut} launches a load test from a scenario's trigger code, with an optional label query parameter. Then poll GET /t/{shortcut}/status with the returned test code and read GET /t/{shortcut}/report or download GET /t/{shortcut}/report.json when it finishes.

What are the rate limits for the Loadster API?

The OpenAPI spec does not specify rate limits. Check the Loadster documentation for current limits, and poll test status at a modest interval rather than in a tight loop.

How do I read a load test report with the Loadster API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add the Loadster API from the Jentic API Directory, and have your agent search for 'get a load test report'. Jentic returns getTestReportData (GET /projects/{projectId}/tests/{testId}/report) with its schema, and the agent passes the project and test ids. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Loadster MCP server?

Yes - Loadster offers an MCP server for AI assistants. You can also connect the Loadster API directly through Jentic: your agent gets the full 85-endpoint surface from the spec without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

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

Yes. Write a rule that allows GET under /projects/p1/ plus the trigger and status calls for your checkout scenario. The agent can then launch that test and read its reports in one project, while deleteProject, deleteMonitorById, and killCloudTest are outside the allowed set, and every call it makes is logged.

Can the Loadster API import scripts from JMeter, k6, or Locust?

Yes. POST /projects/{projectId}/scripts/{scriptId}/actions/import takes a required source query parameter with the original script, plus optional replace and baseUrl parameters, and converts it into the target Loadster script.

Loadster API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting Qahttp bearer (personal access token); trigger-code endpoints need no token85 EndpointsREST

For Agents

Launch Loadster load tests from a trigger code, check status and read test reports and advice, edit projects, scripts, scenarios, and datasets, and manage synthetic monitors, incidents, and maintenance windows.

Use for: Kick off the checkout load test from CI, Check whether the load test that started ten minutes ago has finished, Get the report and advice for the last load test, I want to import our k6 script into Loadster

Not supported: Does not host or deploy your application, collect production APM traces, or manage on-call schedules. Use for load testing, script authoring, and synthetic monitoring in Loadster only.

The Loadster API works with the same projects, scripts, scenarios, datasets, monitors, and load test results as the Loadster dashboard. It lets you build and import test scripts (including JMeter, k6, or Locust scripts), play a script once on an engine, launch a load test from a scenario's trigger code, follow its status, and read the finished test report and advice. The monitoring side manages synthetic monitors, their cycles and status periods, incidents, notification policies, and maintenance windows, and you can register self-hosted engines alongside Loadster's cloud regions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

95%

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

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

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.

AI-Readiness & Agent Experience

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

Grade: D-Signals: 4

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

88%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C+Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Loadster API to your agent

Capabilities

Start building with Loadster API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Loadster API

Jentic AI Readiness Score

Loadster API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness