canonical: https://jentic.com/apis/capgo.app/capgo # Capgo App Capgo Public API 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. ## For AI agents Register app bundles, attach them to release channels, target devices, and read per-app update statistics through the Capgo live-update API. ## Scope Does not handle app store submission, native source builds, or crash reporting. Use for Capacitor over-the-air live updates and bundle distribution only. ## Capabilities - Register a new app bundle from a hosted zip URL and checksum - 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 - Manage organizations, members, and API keys - Update bundle metadata such as its release link or comment ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Fetch the time-series statistics and bundle usage distribution for one app over the current period ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/app/` | List apps visible to the API key | | POST | `/app/` | Create a new app | | POST | `/bundle/` | Register a new bundle from a hosted zip URL | | 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 | ## Key resources - **Apps** — App creation, listing, retrieval, update, and deletion - **Bundles** — Bundle registration from a hosted zip URL, channel attachment, and metadata updates - **Channels** — Release channel creation and configuration - **Devices** — Device links and bundle or channel overrides - **Statistics** — App, organization, and user-level usage statistics - **Organizations** — Organization and member management ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 62 / 100 - Developer Experience & Jentic Compatibility: 67 / 100 - AI-Readiness & Agent Experience: 52 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 88 / 100 - **View full report:** https://jentic.com/apis/capgo.app/capgo/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Visual App Center API** — App Center distributes mobile app builds and has historically offered CodePush-style live updates. - **Bitrise API** — Bitrise builds and tests mobile apps in CI before a bundle is shipped. - **Vercel API** — Vercel deploys the web backend or hosted assets an app depends on. ## FAQ ### 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.