Install Jentic One Beta

Connect the YepCode REST API to your agent

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

Resume scheduled process

Pause scheduled process

Kill execution

Create variable

Get variables

GET STARTED

Start building with YepCode REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use YepCode REST API for, with concrete tasks.

★ Developer Tools Operations

Use the YepCode REST API to perform developer tools operations programmatically. The API provides 54 endpoints covering core functionality including resume scheduled process, pause scheduled process, kill execution.

Call PUT /schedules/{id}/resume to resume scheduled process

Automated Auth Management

Automate auth operations by combining multiple YepCode REST API endpoints. Agents can pause scheduled process and then kill execution in a single workflow.

Call PUT /schedules/{id}/pause to pause scheduled process, then verify the result

AI Agent Integration via Jentic

AI agents discover and call YepCode REST API 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 oauth2 tokens manually.

Search Jentic for 'resume scheduled process', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

54 endpoints — yepcode rest api - openapi specification.

METHOD

PATH

DESCRIPTION

PUT

/schedules/{id}/resume

Resume scheduled process

PUT

/schedules/{id}/pause

Pause scheduled process

PUT

/executions/{id}/kill

Kill execution

POST

/variables

Create variable

GET

/variables

Get variables

POST

/storage/objects

Upload an object

GET

/storage/objects

Get objects

POST

/processes

Create a process

PUT

/schedules/{id}/resume

Resume scheduled process

PUT

/schedules/{id}/pause

Pause scheduled process

PUT

/executions/{id}/kill

Kill execution

POST

/variables

Create variable

GET

/variables

Get variables

POST

/storage/objects

Upload an object

GET

/storage/objects

Get objects

POST

/processes

Create a process

Why Jentic?

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

Setup

Wiring YepCode by hand means running its OAuth2 client-credentials flow against the YepCode realm, substituting your team id into the cloud.yepcode.io host, and handling token refresh and retries yourself. Through Jentic you install once, import YepCode from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

YepCode puts the schedule and execution ids in the URL path (/schedules/{id}, /executions/{id}), so a rule can pin your agent to one schedule or execution: it can pause or resume that schedule and nothing else. You choose the operations it may call, so disruptive ones like killing an execution are not included unless you add them.

Credential isolation

Your YepCode credentials 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 'resume a scheduled process' or 'create a variable', and Jentic returns the matching YepCode 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 YepCode REST API through Jentic.

What authentication does the YepCode REST API use?

The YepCode REST API uses OAuth 2.0 for authorization. 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 resume scheduled process with the YepCode REST API?

Yes. Use the PUT /schedules/{id}/resume endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the YepCode REST API?

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 resume scheduled process through Jentic?

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

How many endpoints does the YepCode REST API have?

The YepCode REST API exposes 54 endpoints covering auth, executions, modules operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which YepCode operations and credentials the agent may use. Because YepCode carries the schedule and execution ids in the URL path (/schedules/{id}, /executions/{id}), you can pin the agent to a single schedule or execution, letting it pause or resume that one and nothing else. You also choose the exact operations it may call, so disruptive ones like killing an execution are excluded unless you explicitly allow them.

YepCode REST API

Name: YepCode REST API
Brand: YepCode REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controloauth254 EndpointsREST

For Agents

Programmatically resume scheduled process, pause scheduled process. Covers 54 operations with oauth2 authentication.

Use for: I need to resume scheduled process, I want to pause scheduled process, Search for kill execution, Find all variable

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

YepCode REST API - OpenAPI Specification. The API exposes 54 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document