Build with AI agents

Ubriot is built to be driven by AI agents as well as people. This page lists every entry point and the rules an agent should follow.

Commands below marked 1.3.0 or 1.4.0 fail with "unknown option" or "unknown command" on older CLI releases. Check with npm view ubriot version and ubriot --version.

Read the docsCopy Anchor Link

Every docs page also has Copy as Markdown, Open in ChatGPT and Open in Claude buttons.

Use UbriotCopy Anchor Link

Always check the latest package version with npm view <package> version rather than trusting a number on a page.

Getting accessCopy Anchor Link

• A person signs up at ubriot.dev/signup, verifies the account's email from the dashboard banner (builds and store submissions return email_not_verified until then) and verifies a payment card at ubriot.dev/dashboard/billing to start a 14-day trial. The $1 card check is refunded, and billing for the chosen plan starts when the trial ends. There is no free tier. An agent must not sign up, enter card details or choose a plan for someone.
• The person creates an API key at ubriot.dev/dashboard/api-keys and gives it to the agent through an environment variable or the MCP client config, never in chat or in a committed file.
• Signing credentials (Apple certificates and keys, Android keystores, Google Play service accounts) are uploaded by a signed-in person. API keys cannot read or upload them.

Safe ways to tryCopy Anchor Link

There is no sandbox or test mode. Every build, store submission, OTA update and push notification acts on a real app and can reach real users. Safe, read-only starting points:

• ubriot apps list, ubriot builds list, ubriot builds show <id> and ubriot builds logs <id> on any release; ubriot builds last-good and ubriot builds queue need 1.3.0, and --json needs 1.4.0.
• MCP tools ubriot_list_apps, ubriot_app_readiness, ubriot_list_builds, ubriot_build_status and ubriot_build_logs.
• ubriot migrate eas and ubriot migrate codepush without --apply print the migration plan and change nothing.
• ubriot ship ios --no-submit builds without submitting to a store. It still runs a real build on Ubriot's machines.

Add Ubriot to your repository's agent rulesCopy Anchor Link

Paste this into AGENTS.md, CLAUDE.md or .cursor/rules in your app's repository and replace myapp:

## Mobile releases (Ubriot)

- Releases run on Ubriot. Docs for agents: https://docs.ubriot.dev/llms.txt
- The Ubriot app slug is `myapp`. Auth comes from the UBRIOT_TOKEN environment variable; never print or commit it.
- Use the ubriot CLI (`npm install -g ubriot`) or the ubriot MCP server. On ubriot 1.4.0 or later, add `--json` when you need to parse output.
- Read-only commands are always fine: `ubriot builds list --app myapp`, `ubriot builds show <id>`, `ubriot builds logs <id>`.
- Only when asked: `ubriot ship ios|android --app myapp` (store release), `ubriot update --app myapp --channel <channel>` (OTA to real users), push sends.
- After a failed build, read `ubriot builds logs <id>` before changing code or retrying.

Not available yetCopy Anchor Link

• A hosted MCP server with OAuth sign-in. Today every client runs the local stdio server with an API key.
• A published OpenAPI document, stable error codes with documentation links on every error (today only the newer errors carry them; see HTTP API), and idempotency keys on writes.
• A sandbox or test mode.
• Browser or device sign-in for the CLI. People use ubriot login with a password; automation uses API keys.