Stoplight

Name: Stoplight API
Brand: Stoplight
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey5 EndpointsREST

Install Jentic One Beta

Connect the Stoplight to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stoplight, 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%2Fstoplight.io%2Fstoplight" | 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%2Fstoplight.io%2Fstoplight" | 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 Stoplight API.

Publish Anonymous

Export

Import

Unpublish

GET STARTED

Start building with Stoplight API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Stoplight API for, with concrete tasks.

★ Developer Tools Operations

Use the Stoplight to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including publish anonymous, export, import.

Call POST /versions/publish/anon to publish anonymous

Automated Versions Management

Automate versions operations by combining multiple Stoplight endpoints. Agents can export and then import in a single workflow.

Call GET /versions/{versionId}/export/{format} to export, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Stoplight 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 'publish anonymous', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — stoplight.

METHOD

PATH

DESCRIPTION

POST

/versions/publish/anon

Publish Anonymous

GET

/versions/{versionId}/export/{format}

Export

PUT

/versions/{versionId}/import

Import

POST

/versions/{versionId}/publish

Publish

PUT

/versions/{versionId}/unpublish

Unpublish

POST

/versions/publish/anon

Publish Anonymous

GET

/versions/{versionId}/export/{format}

Export

PUT

/versions/{versionId}/import

Import

POST

/versions/{versionId}/publish

Publish

PUT

/versions/{versionId}/unpublish

Unpublish

Why Jentic?

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

Setup

Wiring Stoplight by hand means sending its API key in the Authorization header on every call to api.stoplight.io/v1 and coordinating the export, import, and publish steps for each version yourself. Through Jentic you install once, import Stoplight from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Stoplight puts the version id in the URL path (/versions/{versionId}/...), so a rule can pin your agent to one version: it can export or import that version and nothing else. You choose the operations it may call, so publish and unpublish are not included unless you add them.

Credential isolation

Your Stoplight API key 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 'export an API version' or 'publish a documentation version', and Jentic returns the matching Stoplight 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

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Stoplight API through Jentic.

What authentication does the Stoplight use?

The Stoplight uses an API key passed in the `Authorization` 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 publish anonymous with the Stoplight?

Yes. Use the POST /versions/publish/anon endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Stoplight?

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 publish anonymous through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'publish anonymous'. Jentic returns the matching Stoplight operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Stoplight have?

The Stoplight exposes 5 endpoints covering versions operations.