Loader.io API

Name: Loader.io API
Brand: Loader.io API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey13 EndpointsREST

For Agents

Register applications, verify test domains, run cloud-based load tests, and retrieve performance results from the Loader.io API.

Install Jentic One Beta

Connect the Loader.io API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loader.io 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

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 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 Loader.io API.

Create load tests with target URLs, concurrency, and duration configuration

Trigger and stop test runs from CI or agent workflows

GET STARTED

Start building with Loader.io API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Loader.io API for, with concrete tasks.

★ Pre-Release Load Test in CI

Engineering teams gate releases on a load test against staging. Loader.io is called from CI to verify the application, kick off a configured test, wait for the run to finish, and pull the result. Failures fail the pipeline. The flow is small enough to wire into any CI provider with a few API calls.

Call PUT /tests/{test_id}/run to start a saved load test, poll GET /tests/{test_id}/results until the run completes, and fail the build if response time exceeds the threshold.

Domain Verification and Firewall Setup

Before any test can run, loader.io requires you to prove ownership of the target domain and ideally allowlist the loader.io egress IPs at your firewall. The API exposes both: a verification endpoint per app and a global servers endpoint that returns the IP list. This means platform teams can fully script onboarding instead of doing it through the dashboard.

Call POST /apps to register the domain, POST /apps/{app_id}/verify to verify ownership, then GET /servers to retrieve the loader.io IPs for the firewall.

AI Agent-Driven Performance Triage

An AI agent investigating a slow endpoint can use Jentic to discover Loader.io operations, configure a test against the suspect URL, run it, and pull the results back into a triage summary. Credentials remain in the Jentic vault, so the agent can run tests without ever holding the API key.

Use Jentic to call POST /tests with a config targeting the slow URL, PUT /tests/{test_id}/run to start it, and GET /tests/{test_id}/results to summarise latency and error rate.

Key Endpoints

13 endpoints — jentic publishes the only available openapi specification for loader.

METHOD

PATH

DESCRIPTION

POST

/apps

POST

/apps/{app_id}/verify

Verify domain ownership

POST

/tests

Create a load test configuration

PUT

/tests/{test_id}/run

Trigger a test run

PUT

/tests/{test_id}/stop

Stop a running test

GET

/tests/{test_id}/results

Retrieve results for a test

GET

/servers

Loader.io egress IPs

POST

/apps

POST

/apps/{app_id}/verify

Verify domain ownership

POST

/tests

Create a load test configuration

PUT

/tests/{test_id}/run

Trigger a test run

PUT

/tests/{test_id}/stop

Stop a running test

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Loader.io API keys are stored encrypted in the Jentic vault. The loaderio-auth header is injected at execution time so the raw key never enters the agent's context, logs, or LLM traces.

Intent-based discovery

Agents search Jentic for intents like 'run a load test' and Jentic returns the relevant Loader.io operations with input schemas, so an agent can configure and trigger a test without consulting docs.loader.io.

Time to first call

Direct Loader.io integration: half a day to a day for app registration, domain verification, and result polling logic. Through Jentic: under 1 hour to search, load schema, and execute.

FAQs

Specific to using Loader.io API through Jentic.

Why is there no official OpenAPI spec for Loader.io API?

Loader.io does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Loader.io API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Loader.io API use?

The API requires an API key sent in the loaderio-auth request header. Through Jentic, the key sits in the vault and is injected at call time, so the agent never holds the raw value.

Can I run a load test without verifying my domain?

No. Loader.io requires domain verification before traffic is sent. Use POST /apps/{app_id}/verify after registering the application; only then will tests created against that app run.

What are the rate limits for the Loader.io API?

Rate limits are not stated in the spec. Loader.io enforces per-plan limits on concurrent users and total test minutes; these are tied to your subscription rather than the HTTP API.

How do I run a load test from an agent through Jentic?

Search Jentic for 'run a load test against my application'. Jentic returns the PUT /tests/{test_id}/run operation. Load the schema, pass your test_id, and execute. Poll GET /tests/{test_id}/results to retrieve the run.

How do I get the loader.io IPs for a firewall allowlist?

Call GET /servers. The response is the current list of loader.io egress IPs that you can add to your firewall or WAF rules so test traffic is not blocked.

Loader.io API

Connect the Loader.io API to your agent

Capabilities

Start building with Loader.io API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs