Install Jentic One Beta

Connect the Activepieces API to your agent

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

Build automation flows and update their steps

Trigger, list, and cancel flow runs to control executions

Organise flows into folders and projects

Store and query rows in Activepieces tables

Manage app connections that hold third-party credentials for flows

GET STARTED

Start building with Activepieces API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Activepieces API for, with concrete tasks.

★ AI agent flow control

An AI agent operating an Activepieces instance can start, inspect, and stop automation runs on demand. Through Jentic the agent searches by intent and the API token never enters its prompt context, turning Activepieces into a programmable automation backend rather than a dashboard the operator clicks through.

Use Jentic to search 'list Activepieces flow runs', call GET /v1/flow-runs to find recent runs, and POST /v1/flow-runs/cancel to stop a run that is stuck.

Programmatic flow management

Teams that version their automations in code can create and fetch flows without opening the builder. The agent creates a flow, then reads it back to confirm the configuration was saved, keeping flow definitions in sync with an external source of truth.

Create a flow via POST /v1/flows, then fetch it with GET /v1/flows/{id} to confirm it was saved.

Tables as an automation backend

Activepieces tables store structured rows that flows read and write. An agent can append rows and list existing data to drive downstream automation, using the built-in table store instead of standing up a separate database for lightweight state.

Add a row via POST /v1/records/{id} into a table, then list current rows with GET /v1/records.

Connection and release management

Before a flow can reach a third-party service it needs an app connection, and moving a configured project forward needs a release. An agent can provision the connection and publish the release in one sequence, automating environment promotion for Activepieces projects.

Create an app connection via POST /v1/app-connections, then publish a release with POST /v1/project-releases.

Key Endpoints

66 endpoints — the activepieces api manages automation flows, executions, and the data that supports them on an activepieces instance.

METHOD

PATH

DESCRIPTION

POST

/v1/flows

Create an automation flow

GET

/v1/flows

List flows

GET

/v1/flows/{id}

Get a flow by id

GET

/v1/flow-runs

List flow runs

POST

/v1/flow-runs/cancel

Cancel a flow run

GET

/v1/records

List table records

POST

/v1/app-connections

Create an app connection

POST

/v1/project-releases

Publish a project release

POST

/v1/flows

Create an automation flow

GET

/v1/flows

List flows

GET

/v1/flows/{id}

Get a flow by id

GET

/v1/flow-runs

List flow runs

POST

/v1/flow-runs/cancel

Cancel a flow run

GET

/v1/records

List table records

POST

/v1/app-connections

Create an app connection

POST

/v1/project-releases

Publish a project release

Why Jentic?

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

Setup

Wiring Activepieces by hand means handling its bearer token auth against cloud.activepieces.com/api and encoding flow, run, and table calls yourself. Through Jentic you install once, import Activepieces from the API Directory, store the token once, and your agent calls it.

Permission scoping

Activepieces puts the flow, project, and table ids in the URL path (/v1/flows/{id}, /v1/projects/{id}), so a rule can pin your agent to one project or flow. You choose the operations it may call, so destructive ones like deleting a flow or removing a user are not included unless you add them.

Credential isolation

Your Activepieces API 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 'trigger a flow' or 'add a table row', and Jentic returns the matching Activepieces operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Activepieces API through Jentic.

Is there an Activepieces MCP server?

You don't need an MCP server to give your agent Activepieces. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls its flow, run, and table operations. That keeps your agent's context free of an extra server's tool definitions.

What authentication does the Activepieces API use?

The Activepieces API authenticates with a bearer token sent in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never reaches the agent's context.

Can I trigger and cancel flow runs with the Activepieces API?

Yes. GET /v1/flow-runs lists runs and GET /v1/flow-runs/{id} returns a single run, while POST /v1/flow-runs/cancel stops a run in progress. Creating and editing the flows themselves is handled by POST /v1/flows and GET /v1/flows/{id}.

Can I store data in Activepieces tables through the API?

Yes. GET /v1/tables lists your tables, POST /v1/records/{id} adds a row, and GET /v1/records reads rows back, so a flow or agent can use tables as a lightweight state store.

What are the rate limits for the Activepieces API?

The OpenAPI spec does not specify rate limits. Check the Activepieces documentation at https://www.activepieces.com/docs for current limits.

How do I run an Activepieces flow through Jentic?

Search Jentic for 'list Activepieces flow runs', load the input schema, and execute against GET /v1/flow-runs or POST /v1/flow-runs/cancel. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the flow-run read and cancel operations under one project id, so the agent can start and stop runs for that project and touch nothing else, and every call it makes is logged. Deleting flows or removing users stays out unless you add those operations.

Activepieces API

AI ReadinessNon-Ready (F)4/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsProject Managementbearer66 EndpointsREST

For Agents

Create and edit automation flows, trigger and cancel flow runs, manage folders, projects, tables, and app connections, and publish project releases on an Activepieces instance.

Use for: Create a new automation flow in my project, List all flows in a folder, Trigger a flow run and check its status, Cancel a running flow execution

Not supported: Does not run your automation logic outside Activepieces, provide analytics dashboards, or replace the connected third-party apps. Use for managing Activepieces flows, runs, tables, and connections only.

The Activepieces API manages automation flows, executions, and the data that supports them on an Activepieces instance. It creates and edits flows, triggers and cancels flow runs, organises work into folders and projects, and stores rows in built-in tables. App connections hold the credentials that flows use to reach third-party services, and project releases move a configured project between environments.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 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).

100%

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: FSignals: 4

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

92%

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

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Activepieces API to your agent

Capabilities

Start building with Activepieces API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Activepieces API

Jentic AI Readiness Score

Activepieces Documentation

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