Install Jentic One Beta

Connect the Cohesivity Agent Control API to your agent

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

Create a 72-hour ephemeral tenant to bootstrap a project

Provision one or many tenant resources

Tear down a single tenant resource by name

Read a tenant's resources, runtime, billing, and limits

Create a one-click human approval URL for a sensitive action

GET STARTED

Start building with Cohesivity Agent Control API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cohesivity Agent Control API for, with concrete tasks.

★ Agent Bootstraps an Ephemeral Tenant

An AI agent connected to the Cohesivity Agent Control API can stand up a short-lived workspace to run a project. It creates a 72-hour ephemeral tenant with the genesis endpoint, then provisions the resources the project needs, so the agent gets an isolated environment that expires on its own instead of leaving infrastructure behind. The status endpoint lets the agent confirm what was provisioned.

Create a 72-hour ephemeral tenant, provision the resources it needs, and read the tenant status to confirm they are ready

Resource Provisioning and Teardown

The Cohesivity Agent Control API provisions tenant resources one at a time or in a batch and tears a single resource down by name. An agent managing a project can add a resource when a step needs it and remove it when the step is done, keeping a tenant's footprint matched to the work in progress rather than provisioning everything up front.

Provision the resource named cache for the tenant, then tear it down by name once the job completes

Human Approval Before a Sensitive Action

Some actions should pause for a person. The Cohesivity Agent Control API creates a one-click human approval URL, so an agent can generate the link, surface it to the owner, and poll the wait descriptor until the action is approved or denied. This keeps a human in the loop for sensitive steps without the agent blocking on a side channel.

Create a human approval URL for a sensitive action, present it to the owner, and poll the wait descriptor until it resolves

Tenant Status and Usage Observability

Operators need to know what each tenant is running and spending. The Cohesivity Agent Control API reads a single tenant's resources, runtime, billing, and limits, and reads account-wide observability across every tenant. An agent can poll these to report usage, flag a tenant near its limits, and keep an inventory of what is provisioned without a dashboard.

Read account-wide observability and return every tenant that is approaching its provisioned limits

Key Endpoints

17 endpoints — the cohesivity agent control api bootstraps tenants and manages their resources for agent-run projects.

METHOD

PATH

DESCRIPTION

POST

/api/genesis

Create a 72-hour ephemeral tenant

POST

/api/resources

Provision multiple tenant resources

POST

/api/resources/{resourceName}

Provision one tenant resource

DELETE

/api/resources/{resourceName}

Tear down one tenant resource

GET

/api/status

Read tenant resources, runtime, billing, and limits

POST

/api/claim/url

Create a one-click human approval URL

GET

/api/wait

Poll a Cohesivity wait descriptor

GET

/api/observability

Read account-wide tenant and usage observability

POST

/api/genesis

Create a 72-hour ephemeral tenant

POST

/api/resources

Provision multiple tenant resources

POST

/api/resources/{resourceName}

Provision one tenant resource

DELETE

/api/resources/{resourceName}

Tear down one tenant resource

GET

/api/status

Read tenant resources, runtime, billing, and limits

POST

/api/claim/url

Create a one-click human approval URL

GET

/api/wait

Poll a Cohesivity wait descriptor

GET

/api/observability

Read account-wide tenant and usage observability

Why Jentic?

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

Setup

Wiring the Cohesivity Agent Control API by hand means handling a management API key in the Authorization header, a separate wait token, and the optional OAuth 2.1 PKCE flow, and knowing which operations are open. Through Jentic you install once, import Cohesivity from the API Directory, store the management key once, and your agent calls it.

Permission scoping

Cohesivity puts the resource name in the URL path (/api/resources/{resourceName}) and the management key is scoped to one tenant, so a rule can pin your agent to that tenant and the operations you pick: it can read status and provision resources without the teardown operation. You choose the operations it may call, so DELETE /api/resources/{resourceName} is not included unless you add it.

Credential isolation

Your Cohesivity management 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 'provision a tenant resource' or 'read tenant status', and Jentic returns the matching Cohesivity operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cohesivity Agent Control API through Jentic.

What authentication does the Cohesivity Agent Control API use?

The Cohesivity Agent Control API uses several schemes per its OpenAPI spec. Most management operations take a management API key sent in the Authorization header as the literal value Bearer coh_man_ from the tenant .cohesivity file. Creating an ephemeral tenant, the health check, and the OAuth endpoints are open, the wait endpoint takes a wait token, and account access can use OAuth 2.1 with PKCE. Through Jentic the management key is stored once by your own self-hosted instance and injected at call time, so it never sits in your agent's prompt or logs.

Is there a Cohesivity MCP server?

Yes - Cohesivity runs a public MCP server for its documentation and management. You can also connect the Cohesivity Agent Control API directly through Jentic: your agent gets the full 17-endpoint surface, including the tenant provisioning and status operations, without loading another server's tool definitions into its context, your management key is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Cohesivity Agent Control API?

Yes. Write a rule that allows only the status read and resource-provisioning operations for one tenant, so the agent can bootstrap and inspect resources but cannot tear anything down or issue approval URLs. Every call it makes is logged, so you can audit exactly what the agent touched.

Can I provision and tear down tenant resources with the Cohesivity Agent Control API?

Yes. Provision many resources with POST /api/resources or one with POST /api/resources/{resourceName}, and tear a single resource down with DELETE /api/resources/{resourceName}. Read what a tenant is running with GET /api/status, which returns its resources, runtime, billing, and limits in one call.

What are the rate limits for the Cohesivity Agent Control API?

The OpenAPI spec does not specify rate limits for the Cohesivity Agent Control API. The status endpoint reports a tenant's current limits, so an agent can read those and pace its provisioning calls. Check the documentation at https://cohesivity.ai for current account limits.

How do I provision a tenant resource with the Cohesivity Agent Control API through Jentic?

Search Jentic for 'provision a tenant resource' and it returns the POST /api/resources/{resourceName} operation with its input schema. Pass the resource name and its configuration and the agent provisions it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Cohesivity Agent Control API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeapiKey, oauth217 EndpointsREST

For Agents

Bootstrap ephemeral tenants, provision and tear down tenant resources, read a tenant's status and limits, issue human approval URLs, and poll for long-running actions. Reads account-wide usage observability across tenants.

Use for: Create an ephemeral tenant to try out a project, Provision the resources a new tenant needs, Tear down a resource I no longer need, Check a tenant's current resources, runtime, and limits

Not supported: Does not run your agent's business logic, host application code, or store end-user data. Use for Cohesivity tenant bootstrap, resource provisioning, and status only.

The Cohesivity Agent Control API bootstraps tenants and manages their resources for agent-run projects. It creates 72-hour ephemeral tenants, provisions and tears down tenant resources by name, and reads a tenant's resources, runtime, billing, and limits in one status call. It also issues one-click human approval URLs for sensitive actions, polls a wait descriptor for long-running work, and reads account-wide usage observability.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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.

68%

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: D+Signals: 4

46%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

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

58%

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: A-Signals: 1

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cohesivity Agent Control API to your agent

Capabilities

Start building with Cohesivity Agent Control API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cohesivity Agent Control API

Jentic AI Readiness Score

Cohesivity Agent Control 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