Install Jentic One Beta

Connect the ActionDock API to your agent

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

Submit a bounded action and hold it as an awaiting-approval job until the workspace owner approves the exact request

List the actions a workspace exposes and the approved API connections available without their credentials

Track each job's status and read owner-reported reconciliation evidence for a write whose outcome is unknown

Follow job and callback events from action submission through delivery and retry

GET STARTED

Start building with ActionDock API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use ActionDock API for, with concrete tasks.

★ Owner-Approved Agent Writes

Put a human in the loop before an AI agent performs a consequential write. The agent submits a bounded action to ActionDock, which holds it as an awaiting-approval job until the workspace owner approves the exact request, then runs it with server-held credentials. This bounds what an autonomous agent can trigger without ever handing it the downstream API keys.

Submit a bounded action, then poll the returned job until the owner approves or rejects it

Job and Reconciliation Tracking

Follow a submitted action from proposal to delivery. The agent lists recent jobs, reads a single job's status and events, and when a write's outcome is unknown it reads the owner-reported reconciliation evidence instead of guessing. Teams use this to audit exactly which agent action produced which external effect.

List recent jobs, fetch one job by id, and read its reconciliation evidence for an execution-unknown write

AI Agent Integration via Jentic

An AI agent discovers and calls ActionDock through Jentic without handling the workspace key directly. The agent searches by intent, receives the matching operation and its input schema, and submits a bounded action, while Jentic injects the stored credential at execution time. This lets the agent propose approved writes without reading the reference docs or holding secrets.

Search Jentic for 'submit an action for approval', load the operation schema, and submit the action with Jentic-injected credentials

Key Endpoints

29 endpoints — the actiondock api puts owner approval and deterministic policy between an ai agent's tool call and a real external write.

METHOD

PATH

DESCRIPTION

GET

/v1/actions

List available actions

POST

/v1/actions/{action}

Submit one bounded action for approval

GET

/v1/jobs

List recent jobs and workflow metadata

GET

/v1/jobs/{jobId}

Get a single job

GET

/v1/jobs/{jobId}/reconciliations

Read owner-reported evidence for an unknown write

GET

/v1/connections

List approved API connections without credentials

GET

/v1/actions

List available actions

POST

/v1/actions/{action}

Submit one bounded action for approval

GET

/v1/jobs

List recent jobs and workflow metadata

GET

/v1/jobs/{jobId}

Get a single job

GET

/v1/jobs/{jobId}/reconciliations

Read owner-reported evidence for an unknown write

GET

/v1/connections

List approved API connections without credentials

Why Jentic?

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

Setup

Wiring ActionDock by hand means creating a workspace API key, sending it as a Bearer token on actiondock.app, and separately handling the owner-approval callbacks and job polling yourself. Through Jentic you install once, import ActionDock from the API Directory, store the key once, and your agent calls it.

Permission scoping

ActionDock already gates every external write behind owner approval, and through Jentic you choose which of its own operations your agent may call. You can allow it to submit actions and read job status while leaving artifact deletion and the owner-only dashboard operations out of the set.

Credential isolation

Your ActionDock workspace 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 'submit an action for approval' or 'check a job status', and Jentic returns the matching ActionDock operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using ActionDock API through Jentic.

What authentication does the ActionDock API use?

The ActionDock API authenticates agent operations with a workspace API key sent as a Bearer token in the Authorization header, per its OpenAPI spec. The owner-only dashboard endpoints use a separate signed-in session cookie rather than an API key, and a few endpoints such as the health check and agent manifest are public. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent.

Is there an ActionDock MCP server?

You do not need a separate MCP server to give your agent ActionDock. Jentic connects it directly from the API Directory: import ActionDock, store your workspace key once, and your agent calls its approval and job operations on demand. Operations are discovered as needed, so your agent's context is not filled with tool definitions it will not use.

Can I require owner approval before my agent performs a write with the ActionDock API?

Yes. Your agent submits the write as a bounded action, ActionDock holds it as an awaiting-approval job, and the workspace owner approves the exact request before ActionDock executes it with server-held credentials. The agent can list available actions and poll job status, but it cannot complete a write the owner has not approved.

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

Yes. Because you run Jentic One yourself, your rules decide which ActionDock operations the agent may call. You can allow it to submit actions and read job status and events while withholding artifact deletion and the owner-only dashboard operations, and every call it makes is logged.

What are the rate limits for the ActionDock API?

The OpenAPI spec does not specify rate limits for the ActionDock API. Check the ActionDock documentation at https://actiondock.app for current limits. Through Jentic, calls run from your own instance, so you can add your own pacing around them.

How do I submit an action for approval with the ActionDock API through Jentic?

Search Jentic for 'submit an action for approval' to get the matching ActionDock operation and its input schema, then your agent submits the bounded action and polls the returned job for the owner's decision. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Actiondock App ActionDock API

AI ReadinessFoundational (D)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthorizationbearer, apiKey29 EndpointsREST

For Agents

Submit bounded API writes for owner approval, track each job to delivery, and read reconciliation evidence, across 29 operations secured with a workspace API key.

Use for: I need to submit an API write for my owner to approve, Check whether a submitted action has been approved, List the actions available in my workspace, Get the status of a job I submitted

Not supported: Does not execute payments, send messages, or provision infrastructure itself. Use for approving and governing an AI agent's external API writes only.

The ActionDock API puts owner approval and deterministic policy between an AI agent's tool call and a real external write. An agent submits a bounded action, which waits as an awaiting-approval job until the workspace owner approves the exact request, and ActionDock then executes it with server-held credentials the agent never sees. It exposes operations to list the available actions, track jobs and their events, read reconciliation evidence for writes whose outcome is unknown, and inspect workspace connections, billing, and usage. The credentials for each downstream API stay on ActionDock's servers, so the agent proposes writes but never holds the keys that perform them.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

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).

30%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

44%

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

37%

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.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

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: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ActionDock API to your agent

Capabilities

Start building with ActionDock API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Actiondock App ActionDock API

Jentic AI Readiness Score

ActionDock API

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