Limio CLI

A command-line client for Limio. Read and change the catalog, check labels, build and publish pages, and look up customers and subscriptions — from a terminal or from an AI coding agent, with no tokens to paste.

We built it for our own solutions team. It is now stable enough that we want to know if you would use it.

How it works

You install the CLI once, then log in to each environment you work with. Login opens your browser, you sign in to Limio as usual, and the CLI keeps the token in your operating system keychain and refreshes it. Each environment — dev or production, EU or US — is a named profile, and any command takes -e <env> to target a different one.

limio env add my-tenant --tenant my-tenant --domain prod --region eu --default
limio login
limio offers --names

The CLI acts as whoever you logged in as. After a browser login it has exactly your Limio user's permissions — if your role cannot publish a page, neither can the CLI. See Users and Permissions for the roles. A client-credentials login is different. It acts as an OAuth client, not a person, so the role model does not apply, and the scopes of the client decide what it can do. Limio sets those scopes when we create the client — they are not a customer setting. By default the api scope allows full access to all API endpoints. If you need to restrict that, use the browser login instead.

What you can do

• Catalog — read any offer, page, product or campaign, and change it in place. Every write re-reads the item, rechecks the version, then verifies the result. Risky edits take a backup first, and --dry-run shows the change without making it.
• Labels — limio labels check finds the label problems that break builds silently: pages that point at no offer, name drift between the offer and the page, and labels missing from the picklist.
• Health check — limio doctor compares the search index against the catalog and reports broken product references, missing billing codes and token scopes. It catches the offers that render correctly but fail at checkout.
• Build and publish — build a page, wait for it, then publish it. When the platform leaves a route out of a build, the CLI names the route and points at the build log.
• Customers and subscriptions — search by email, then read a subscription with its schedules, offers and event trail. Personal data is masked unless you ask for it.
• Any endpoint — limio api GET /api/shop/builds -q path=/pages2/Home for work the commands do not cover.

Built for AI agents

limio docs prints a workflow guide, so an agent such as Claude Code can drive the CLI after one sentence of setup. Three rules keep that safe: a write to a production environment fails in non-interactive use unless you pass --allow-prod, personal data stays masked by default, and the CLI refuses to send your token to any host but the environment's own.

This sits next to the MCP Server. Use MCP for conversational work in a chat client, and the CLI for scripted, repeatable work in a terminal or a pipeline.

Why it matters

Catalog work today means the admin UI or hand-written API calls. The UI is slow for bulk changes, and raw API calls have no guard rails — a change vector with an array index quietly corrupts an item, and a delete commits with no undo. The CLI puts the safe path in one command, and makes the same work repeatable in a script.

---

This is a Labs feature. We're experimenting with this and it's not yet part of the core platform. Interested in early access or want to help shape it?

Request access →