Install Jentic One Beta

Connect the Capgo Public API to your agent

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

Attach a bundle to a channel to roll out a live update

Create and configure release channels for an app

Link devices to a specific channel or bundle override

Read time-series statistics and bundle usage for an app

GET STARTED

Start building with Capgo Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Capgo Public API for, with concrete tasks.

★ AI Agent Release Rollout

An AI agent connected through Jentic can ship a Capacitor live update end to end: it registers the new bundle from a hosted zip URL, attaches it to the production channel, and confirms the channel now points to that bundle. Capgo handles distribution to linked devices so the agent drives the rollout without touching an app store review.

Register a new bundle from a hosted zip URL and checksum, attach it to the production channel, and confirm the channel points to the new bundle

Staged Live Updates by Channel

Roll out updates gradually by creating separate channels such as beta and production and attaching bundles to each. Capgo lets you move a bundle between channels so testers receive a build before the wider audience does.

Create a beta channel, attach the latest bundle to it, and verify the channel configuration

Device-Targeted Overrides

Pin a specific device to a chosen bundle or channel to reproduce an issue or validate a fix before a wider release. Capgo links devices to overrides and can remove the override so the device falls back to its channel default.

Link a given device to a specific bundle override, then remove the override so the device returns to the channel default

Release Analytics

Measure update adoption by reading per-app time-series statistics and bundle usage distribution. Capgo exposes app-level and organization-level statistics that feed dashboards tracking how many devices run each bundle.

Fetch the time-series statistics and bundle usage distribution for one app over the current period

Key Endpoints

30 endpoints — the capgo api automates capacitor live updates by registering app bundles, attaching them to release channels, and rolling them out to devices without waiting on an app store review.

METHOD

PATH

DESCRIPTION

GET

/app/

List apps visible to the API key

POST

/app/

Create a new app

POST

/bundle/

PUT

/bundle/

Attach a bundle to a channel

POST

/channel/

Create or update a channel configuration

GET

/device/

List devices for an app

GET

/statistics/app/{appId}/

Get time-series statistics for an app

GET

/app/

List apps visible to the API key

POST

/app/

Create a new app

POST

/bundle/

PUT

/bundle/

Attach a bundle to a channel

POST

/channel/

Create or update a channel configuration

GET

/device/

List devices for an app

GET

/statistics/app/{appId}/

Get time-series statistics for an app

Why Jentic?

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

Setup

Wiring Capgo by hand means sending your API key in the x-api-key header (the legacy authorization header still works) and tracking the app, channel, bundle, and device paths yourself. Through Jentic you install once, import Capgo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Capgo puts the app identifier in the URL path (/app/{appId}), so a rule can pin your agent to one app: it can read statistics and roll out bundles for that app and nothing else. You choose which operations it may call, so deleting an app or rotating an API key is not included unless you add it.

Credential isolation

Your Capgo 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 'roll out an app update' or 'list devices for an app', and Jentic returns the matching Capgo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Capgo Public API through Jentic.

What authentication does the Capgo API use?

The Capgo API authenticates with an API key sent in the `x-api-key` header, and it also accepts the key in a legacy `authorization` header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it stays out of the agent's prompt and logs.

Can I roll out live updates with the Capgo API?

Yes. You register a bundle from a hosted zip URL and checksum, then attach it to a channel so linked devices pick up the update. You can also set device-specific overrides and read per-app statistics and bundle usage to track adoption.

What are the rate limits for the Capgo API?

The Capgo spec states that standard accounts are limited to 100 requests per minute and enterprise accounts to 1000 requests per minute. Stay within those ceilings when scripting bulk bundle or device operations.

Is there a Capgo MCP server?

You do not need an MCP server to give your agent the Capgo API. Jentic connects it directly from the API Directory: import Capgo, store your key once, and your agent registers bundles and manages channels through the operations the API already exposes. Operations are discovered on demand, so no extra tool definitions are loaded into the agent's context.

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

Yes. Because the app identifier travels in the URL path, you can write a rule that pins the agent to one app and allows only the operations it needs, such as attaching a bundle and reading statistics. Deleting apps or rotating API keys stays unavailable unless you add it, and every call the agent makes is logged.

How do I roll out an update through Jentic with the Capgo API?

Search Jentic for 'attach a bundle to a channel', which returns the Capgo operation with its input schema, then supply the app, channel, and bundle and the agent runs it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Capgo App Capgo Public API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsCi CdapiKey30 EndpointsREST

For Agents

Register app bundles, attach them to release channels, target devices, and read per-app update statistics through the Capgo live-update API.

Use for: Register a new app bundle from a hosted zip URL, Attach a bundle to the production channel, List the apps visible to my API key, Create a new release channel for my app

Not supported: Does not handle app store submission, native source builds, or crash reporting. Use for Capacitor over-the-air live updates and bundle distribution only.

The Capgo API automates Capacitor live updates by registering app bundles, attaching them to release channels, and rolling them out to devices without waiting on an app store review. It manages organizations, apps, channels, devices, and API keys, and reports time-series statistics and bundle usage for each app. Bundles are registered from an externally hosted zip URL and checksum, and device overrides let you target a specific build to a single device.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

90%

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

60%

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.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

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

40%

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.

69%

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

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

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Capgo Public API to your agent

Capabilities

Start building with Capgo Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Capgo App Capgo Public API

Jentic AI Readiness Score

Capgo Public 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