Install Jentic One Beta

Connect the Replicas API to your agent

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

Start a replica workspace from an environment with a first message and a chosen coding_agent

Send follow-up messages to a replica chat and wait for the agent to finish its turn

Run a shell command inside a replica and read its output and exit code

Expose a public preview URL for a port running inside a replica

Read and merge the GitHub pull requests a replica has opened

GET STARTED

Start building with Replicas API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Replicas API for, with concrete tasks.

★ Delegate coding tasks from your own agent

Your orchestrating agent hands a coding task to a Replicas workspace instead of doing it locally. It creates a replica with a name and message, optionally choosing coding_agent, model, and size (small, large, or ultra), waits for the agent's turn to finish, and reads the chats to see what was done.

Call POST /v1/replica with name set to 'fix-login-test' and message describing the bug, then GET /v1/replica/{id}/wait until it returns done: true

Review and ship the agent's pull request

Once a replica has opened a pull request, the agent reads its details and, if checks pass, merges it by pr_url. Replicas returns 403 when the organization's security policy blocks agent merges, so a human gate can stay in place.

Call POST /v1/replica/{id}/pull-requests/details to read the open pull requests, then POST /v1/replica/{id}/pull-requests/merge with pr_url set to the approved one

Hands-on checks inside a workspace

To verify a change, the agent runs commands in the replica with a timeout_seconds limit, opens a terminal session for longer work, and creates a preview URL for the port the app listens on so a person can click through it.

Call POST /v1/replica/{id}/exec with command set to 'npm test' and timeout_seconds set to 300, then POST /v1/replica/{id}/previews with port set to 3000

Standardise workspaces with environments and automations

Environments define what every workspace starts with: variables, files, enabled skills, tool-server connections, and start and warm hooks. Automations then launch replicas from triggers with a prompt and an environment_id, and failed executions can be retried.

Call POST /v1/environments/{environment_id}/variables to add the variable, then POST /v1/automations with name, triggers, prompt, and environment_id

Key Endpoints

135 endpoints — the replicas api creates and controls replicas: cloud workspaces where a coding agent such as claude, codex, or cursor works on your repositories.

METHOD

PATH

DESCRIPTION

POST

/v1/replica

Create replica

POST

/v1/replica/{id}/messages

Send message

GET

/v1/replica/{id}/wait

Wait for replica

POST

/v1/replica/{id}/exec

Run command

POST

/v1/replica/{id}/previews

Create preview

POST

/v1/replica/{id}/pull-requests/merge

Merge pull request

POST

/v1/environments

Create environment

POST

/v1/automations/{id}/trigger

Trigger automation

POST

/v1/replica

Create replica

POST

/v1/replica/{id}/messages

Send message

GET

/v1/replica/{id}/wait

Wait for replica

POST

/v1/replica/{id}/exec

Run command

POST

/v1/replica/{id}/previews

Create preview

POST

/v1/replica/{id}/pull-requests/merge

Merge pull request

POST

/v1/environments

Create environment

POST

/v1/automations/{id}/trigger

Trigger automation

Why Jentic?

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

Setup

Wiring Replicas by hand means handling its bearer API key, polling the wait operation until a preparing replica is ready, and threading replica, chat, and environment ids through a large nested surface. Through Jentic you install once, import Replicas from the API Directory, store the key once, and your agent calls it.

Permission scoping

Replicas puts the replica id in the URL path (/v1/replica/{id}/...), so a rule can pin your agent to one workspace, and environment ids sit in the path the same way. You choose the operations it may call, so high-impact ones like shell exec, pull request merge, or replica deletion are not included unless you add them.

Credential isolation

Your Replicas 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 cloud coding agent workspace' or 'merge the replica's pull request', and Jentic returns the matching Replicas operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Replicas API through Jentic.

What authentication does the Replicas API use?

Per its OpenAPI spec, the Replicas API uses a bearer token: an organization or personal API key created under Settings, API Keys, sent in the Authorization header. The two workspace identity discovery documents under /.well-known need no API key. Through Jentic, your key is stored encrypted by your own Jentic One instance and injected at execution time.

How many replicas can run at once?

The spec states that an organization can have 100 API and automation replicas active or preparing at once. A new replica returns status preparing straight away, and GET /v1/replica/{id}/wait blocks until it has started and its agents finish their turns.

Which coding agents can a Replicas workspace use?

The create replica operation takes a coding_agent value such as claude, codex, cursor, or opencode, with claude as the default, plus an optional model and a size of small, large, or ultra.

What are the rate limits for the Replicas API?

The OpenAPI spec does not specify request rate limits beyond the concurrent replica cap. Check https://docs.replicas.dev for current limits.

How do I start a Replicas workspace through Jentic?

Search Jentic for 'start a cloud coding agent workspace'. It returns POST /v1/replica, which requires a name and a first message; your agent fills those in and Jentic sends the call with your stored key. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Replicas MCP server?

You don't need an MCP server to give your agent Replicas. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it, finding the right operation by intent instead of loading a tool list for the whole surface into its context.

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

Yes. For instance, allow POST /v1/replica/42/messages, GET /v1/replica/42/wait, and GET /v1/replica/42/history only, so the agent can talk to that one workspace and read its progress but cannot run shell commands, merge pull requests, or change environments or credentials. Every call it makes is logged.

Replicas API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer135 EndpointsREST

For Agents

Start cloud coding-agent workspaces on Replicas, message them, run commands, open previews, merge their pull requests, and manage the environments and automations they run with. Bearer API key auth.

Use for: Start a Replicas workspace to fix the failing test in our repo, Send the replica a follow-up message asking for unit tests, Wait for the replica to finish and show me its chats, Run 'npm test' inside the replica

Not supported: Does not handle source code hosting, CI test execution, or production application deployment. Use for creating and driving Replicas coding-agent workspaces and their environments and automations only.

The Replicas API creates and controls replicas: cloud workspaces where a coding agent such as claude, codex, or cursor works on your repositories. You start a replica from an environment with a first message, then send follow-up messages, manage chats and their queues, run shell commands, open terminal sessions, expose preview URLs for a port, and read or merge the GitHub pull requests the agent opens. Environments carry the variables, files, skills, tool-server connections, and start and warm hooks a workspace boots with, while automations launch replicas from triggers and learnings are loaded into every new workspace.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

87%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

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.

73%

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

58%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

73%

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: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Replicas API to your agent

Capabilities

Start building with Replicas API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Replicas API

Jentic AI Readiness Score

Replicas 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