Install Jentic One Beta

Connect the Arpio API to your agent

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

List and manage protected accounts

Configure sync pairs for cross-region replication

Inspect application resources with backup and restore status

Run and review failover tests

Tune recovery point retention settings

GET STARTED

Start building with Arpio API

Explore with Jentic One

View OpenAPI Document

Validate recovery readiness

Confirm that a protected environment can actually recover. The agent reviews recent failover test results so it can flag any environment whose last drill did not pass.

Call GET /api/accounts/{account_id}/failoverTestResults and surface any failed drill

Audit backup coverage

Check which resources in an application are backed up and which can be restored. The agent lists the application's resources with their backup and restore status to spot gaps.

Call GET /api/accounts/{account_id}/applications/{app_id}/resources/backup to review coverage

Key Endpoints

176 endpoints — the arpio api drives cloud disaster recovery for aws environments.

METHOD

PATH

DESCRIPTION

GET

/api/accounts

List accounts the authenticated subject can access

GET

/api/accounts/{account_id}

Get an account

PUT

/api/accounts/{account_id}

Update an account

DELETE

/api/accounts/{account_id}

Delete an account

GET

/api/accounts/{account_id}/syncPairs

List sync pairs

GET

/api/accounts/{account_id}/failoverTestResults

List failover test results

GET

/api/accounts/{account_id}/applications/{app_id}/resources/backup

List an application's resources with their backup status

GET

/api/accounts/{account_id}/retention

Get an account's recovery point retention settings

GET

/api/accounts

List accounts the authenticated subject can access

GET

/api/accounts/{account_id}

Get an account

PUT

/api/accounts/{account_id}

Update an account

DELETE

/api/accounts/{account_id}

Delete an account

GET

/api/accounts/{account_id}/syncPairs

List sync pairs

GET

/api/accounts/{account_id}/failoverTestResults

List failover test results

GET

/api/accounts/{account_id}/applications/{app_id}/resources/backup

List an application's resources with their backup status

GET

/api/accounts/{account_id}/retention

Why Jentic?

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

Setup

Wiring the Arpio API by hand means obtaining an API key or session cookie, pointing at the api.arpio.io host, and shaping account and application requests yourself. Through Jentic you install once, import Arpio from the Jentic API Directory, store the key once, and your agent calls it.

Permission scoping

Arpio puts the account and application ids in the URL path (/api/accounts/{account_id}), so a rule can pin your agent to one account and nothing else. You choose which operations it may call, so state-changing ones like deleting an account or updating a sync pair are not included unless you add them.

Credential isolation

Your Arpio API key or ArpioSession cookie 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 'list protected accounts' or 'check failover test results', and Jentic returns the matching Arpio operation with its input schema so the agent calls the right endpoint without browsing the reference.

FAQs

Specific to using Arpio API through Jentic.

What authentication does the Arpio API use?

The Arpio API accepts an API key in the X-Api-Key header or an ArpioSession session cookie. Through Jentic the credential is stored encrypted in your Jentic One instance and injected at execution time, so the raw secret never enters the agent context. A few endpoints, such as the OpenAPI document, are public and need no credential.

What can an agent do with the Arpio API?

It can manage protected accounts, configure sync pairs for cross-region replication, inspect application resources with their backup and restore status, run and review failover tests, and tune recovery point retention. Responses are structured so an agent can act on them directly.

Can I run failover tests through the Arpio API?

Yes. The API records failover test results per account, so an agent can review recent drills and flag any environment whose last test did not pass.

What are the rate limits for the Arpio API?

Rate limits are not specified in the OpenAPI spec. Check the Arpio documentation for current limits. Through Jentic, retries are handled in the execution layer.

How many endpoints does the Arpio API have?

The Arpio API exposes 176 endpoints covering accounts, applications, sync pairs, failover tests, and retention.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Arpio operations your agent may call. Because Arpio puts the account id in the URL path, such as /api/accounts/{account_id}, a rule can pin the agent to a single account and nothing else. You also choose which operations it may call, so destructive ones like DELETE /api/accounts/{account_id} to delete an account are excluded unless you add them.

Arpio API

AI ReadinessFoundational (D)44/100

See full scorecard

Community OpenAPI document · agent-readyStorageBackup RecoveryapiKey176 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage AWS disaster recovery with Arpio: protected accounts, sync pairs, backup and restore status, failover tests, and retention. Secured with an API key or session cookie.

Use for: Set up Arpio disaster recovery, List protected AWS accounts, Check the latest failover test results, Review backup status for an application

Not supported: Does not handle application performance monitoring or cost management - use it for AWS disaster recovery and backup only.

The Arpio API drives cloud disaster recovery for AWS environments. An agent can manage protected accounts, configure sync pairs that replicate workloads into a recovery region, inspect application resources with their backup and restore status, run and review failover tests, and tune recovery point retention. It covers the protect, test, and recover lifecycle across accounts and the applications inside them.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

85%

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

12%

Example Density

How richly the API is illustrated with examples.

84%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

54%

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.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: CSignals: 1

54%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Arpio API to your agent

Capabilities

Start building with Arpio API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Arpio API

Jentic AI Readiness Score

Arpio 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