Semaphore CI

Name: Semaphore CI API
Brand: Semaphore CI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey34 EndpointsREST

For Agents

Programmatically run a new workflow, list workflows. Covers 34 operations with apiKey authentication.

Install Jentic One Beta

Connect the Semaphore CI to your agent

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

Run a new workflow

List workflows

Describe a workflow

Rerun a workflow

GET STARTED

Start building with Semaphore CI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Semaphore CI API for, with concrete tasks.

★ CRM Operations

Use the Semaphore CI to perform crm operations programmatically. The API provides 34 endpoints covering core functionality including run a new workflow, list workflows, describe a workflow.

Call POST /plumber-workflows to run a new workflow

Automated Agents Management

Automate agents operations by combining multiple Semaphore CI endpoints. Agents can list workflows and then describe a workflow in a single workflow.

Call GET /plumber-workflows to list workflows, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Semaphore CI 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 'run a new workflow', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

34 endpoints — semaphore ci/cd api for managing workflows, pipelines, jobs, promotions, deployment targets, self-hosted agents, and artifact retention policies.

METHOD

PATH

DESCRIPTION

POST

/plumber-workflows

Run a new workflow

GET

/plumber-workflows

List workflows

GET

/plumber-workflows/{workflow_id}

Describe a workflow

POST

/plumber-workflows/{workflow_id}/reschedule

Rerun a workflow

POST

/plumber-workflows/{workflow_id}/terminate

Stop a workflow

GET

/pipelines

List pipelines

GET

/pipelines/{pipeline_id}

Describe a pipeline

PATCH

/pipelines/{pipeline_id}

Stop a pipeline

POST

/plumber-workflows

Run a new workflow

GET

/plumber-workflows

List workflows

GET

/plumber-workflows/{workflow_id}

Describe a workflow

POST

/plumber-workflows/{workflow_id}/reschedule

Rerun a workflow

POST

/plumber-workflows/{workflow_id}/terminate

Stop a workflow

Why Jentic?

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

Setup

Wiring Semaphore CI by hand means learning its token auth in the Authorization header, resolving the per-organization host at {organization}.semaphoreci.com, and handling pipeline polling yourself. Through Jentic you install once, import Semaphore CI from the API Directory, store the token once, and your agent calls it.

Permission scoping

Semaphore CI puts the workflow and pipeline ids in the URL path (/plumber-workflows/{workflow_id}, /pipelines/{pipeline_id}), so a rule can pin your agent to reading and rescheduling a specific workflow. You choose the operations it may call, so destructive ones like workflow termination are not included unless you add them.

Credential isolation

Your Semaphore CI 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 'run a new workflow' or 'check pipeline status', and Jentic returns the matching Semaphore CI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Semaphore CI API through Jentic.

What authentication does the Semaphore CI use?

The Semaphore CI 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 run a new workflow with the Semaphore CI?

Yes. Use the POST /plumber-workflows endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Semaphore CI?

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 run a new workflow through Jentic?

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

How many endpoints does the Semaphore CI have?

The Semaphore CI exposes 34 endpoints covering agents, artifacts_retention_policies, deployment_targets operations.

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

Yes. Because Jentic One is self-hosted, you decide which Semaphore CI operations your agent may call, so you can grant it read and reschedule access to workflows and pipelines while leaving out destructive operations like workflow termination or pipeline stop. Semaphore CI carries the workflow and pipeline ids in the URL path, such as /plumber-workflows/{workflow_id} and /pipelines/{pipeline_id}, so your own rules can pin the agent to a specific workflow or pipeline rather than the whole account. The credentials the agent uses are the ones you store and scope, and it can only reach the endpoints you have allowed.

Semaphore CI

Connect the Semaphore CI to your agent

Capabilities

Start building with Semaphore CI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs