Install Jentic One Beta

Connect the Capy API to your agent

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

Create automations and enable, disable, flush, or cancel their batches

Open a thread and send messages that drive a Capy agent

Stream a thread, task, or subagent to follow an agent's work in real time

Launch Captains and inspect their crew and daily digest

Start a code review and shape it with review rules and ignore paths

GET STARTED

Start building with Capy API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Capy API for, with concrete tasks.

★ Autonomous Background Agents

Through Jentic, an AI agent creates automations, opens threads, and sends messages to Capy's own background agents, then streams each thread to watch the work land. Every call authenticates with a Capy API key as a bearer token, and a rule can pin the agent to one automation or thread so it drives only the work you intend. The agent finds the operation it needs by intent and calls it directly.

Create an automation, open a thread against it, send the first instruction, and stream the thread until the task reports complete.

Conversational Agent Threads

A product embeds Capy threads so users converse with an AI agent, send follow-up messages, and interrupt or regenerate a reply. Capy keeps each thread's message history, lets a human take over a thread, and supports pinning, archiving, and filing threads into folders. This runs a chat-style agent surface without building the orchestration from scratch.

Open a thread, send a question, stream the reply, and hand the thread off to a human if the agent cannot resolve it.

AI Code Review Automation

Capy starts an AI code review and shapes which findings surface using review rules, filter rules, and ignore paths. A review runs in rounds you can poll by request id, and findings can be commented on and assigned. Teams wire this into their change workflow so an agent reviews code against the rules they set.

Start a review, poll its round by request id until it finishes, and list the findings it produced.

Key Endpoints

78 endpoints — the capy api drives capy's background ai agents: it creates and runs automations, opens threads and sends them messages, and launches captains whose crews and subagents carry out the work.

METHOD

PATH

DESCRIPTION

GET

/api/v1/automations

List automations

POST

/api/v1/automations

Create an automation

GET

/api/v1/threads

List threads

POST

/api/v1/threads

Create a thread

POST

/api/v1/threads/{threadId}/message

Send a message to a thread

GET

/api/v1/threads/{threadId}/messages

List messages in a thread

POST

/api/v1/reviews

Start a code review

GET

/api/v1/captains

List Captains

GET

/api/v1/automations

List automations

POST

/api/v1/automations

Create an automation

GET

/api/v1/threads

List threads

POST

/api/v1/threads

Create a thread

POST

/api/v1/threads/{threadId}/message

Send a message to a thread

GET

/api/v1/threads/{threadId}/messages

List messages in a thread

POST

/api/v1/reviews

Start a code review

GET

/api/v1/captains

List Captains

Why Jentic?

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

Setup

Wiring the Capy API by hand means creating a Capy API key, sending it as a bearer token on every call, and tracking ids across automations, threads, tasks, and subagents. Through Jentic you install once, import Capy from the API Directory, store the key once, and your agent calls it.

Permission scoping

Capy puts the automation id and thread id in the URL path, so a rule can pin your agent to one automation or thread and the operations you pick. You choose what it may call, so deleting automations or changing review rules is not included unless you add it.

Credential isolation

Your Capy 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 'start a code review' or 'open a thread', and Jentic returns the matching Capy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Capy API through Jentic.

What authentication does the Capy API use?

The Capy API authenticates with a Capy API key sent as a bearer token in the Authorization header, per its OpenAPI spec. You create the key in Capy under Settings, then every request to automations, threads, and reviews carries it. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only when a call runs.

Can I run and stream Capy agents through the API?

Yes. You create and run automations, open threads and send them messages, and launch Captains whose subagents do the work. You can stream a thread, task, or subagent to follow progress, and interrupt or hand off a thread when needed.

What are the rate limits for the Capy API?

The OpenAPI spec does not specify rate limits for the Capy API. Check Capy's own documentation at https://docs.capy.ai for current limits before running an agent against it.

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

Yes. Write a rule that allows only the thread and message operations for one automation, so the agent can run and follow that work but cannot delete automations, change review rules, or read the organization's users. Every call it makes is logged, and the agent never sees the key itself.

Is there a Capy MCP server?

You don't need an MCP server to give your agent the Capy API. Jentic connects it directly from the API Directory: import it, store your Capy API key once, and your agent calls the automation, thread, and review operations. You skip loading another server's tool definitions into the agent's context.

How do I run a Capy agent through Jentic?

Add the Capy API from the Jentic API Directory and store your Capy API key once. Your agent then searches by intent such as 'open a thread and send a message' and Jentic returns the matching operation with its input schema, so it can create an automation and stream the thread. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Capy API

AI ReadinessFoundational (D-)42/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer78 EndpointsREST

For Agents

Create and run automations, drive AI agents in threads, start code reviews, and stream their progress across a Capy organization. Every call uses a Capy API key as a bearer token.

Use for: Create an automation that runs a Capy agent on a schedule, Open a new thread and send the agent a task, Stream a thread to watch the agent work in real time, List the Captains in my organization

Not supported: Does not host, train, or fine-tune language models, and does not store files or send email. Use for running Capy automations, agent threads, and code reviews only.

The Capy API drives Capy's background AI agents: it creates and runs automations, opens threads and sends them messages, and launches Captains whose crews and subagents carry out the work. It streams a thread, task, or subagent so you can follow the agent as it runs, starts AI code reviews and shapes them with review rules and ignore paths, and reports usage and organization users. Projects hold the environment variables agents run against, and threads can be archived, pinned, filed into folders, and handed off between the agent and a human.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

51%

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

21%

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.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

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

44%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Capy API to your agent

Capabilities

Start building with Capy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Capy API

Jentic AI Readiness Score

Capy 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