---
name: orbyte-onboard
description: Set up Orbyte Labs credit billing in a new or existing project. Inspect the codebase, install the CLI and skills, then complete development setup, integration, or migration and verification.
---

# Onboard a project to Orbyte Labs

Follow the project's instructions and preserve unrelated changes. Complete the development integration and tests, asking only for missing account access or business decisions.

## Inspect and install

Identify the server application, runtime, package manager, authentication, billable operations, existing billing, and test commands. Reuse its customer identity, prices, and retry mechanism. In a monorepo, work in the application that owns billing.

Install or update `orbytelabs` with the project's package manager. Version 0.1.1+ includes the SDK, CLI, and skills and requires Node.js 24+. Do not upgrade the application's runtime without agreement. Other languages can use the HTTP API with a separate Node.js CLI environment, as described in setup.

Install the bundled skills for later work:

```sh
npx --yes skills add ./node_modules/orbytelabs \
  --skill '*' --agent <agent-id> --yes
```

Replace `<agent-id>` with your agent ID, such as `codex`, `claude-code`, or `cursor`. Preserve existing agent files. If the SDK is not installed locally or your agent cannot load new skills in this session, read the workflow URLs below directly.

## Choose the workflow

Read the installed skill or its linked Markdown:

- Existing billing: follow [orbyte-migrate](https://docs.orbytelabs.com/skills/orbyte-migrate/SKILL.md). It maps the current contract, then uses setup and integration to implement and verify the migration.
- New integration: follow [orbyte-setup](https://docs.orbytelabs.com/skills/orbyte-setup/SKILL.md) to create `orbyte.config.ts` and deploy its catalog, then [orbyte-integrate](https://docs.orbytelabs.com/skills/orbyte-integrate/SKILL.md) to wire matching `check` and `track` calls.

Use the installed CLI's `--help` and [documentation index](https://docs.orbytelabs.com/llms.txt) when needed. If a command is missing, check the installed version rather than inventing a substitute.

## Complete the work

Continue through implementation and verification without repeated plan approvals. For device login, show the user the URL and code, wait for confirmation, and resume. Ask for prices or target accounts only when the project does not establish them.

Use a development environment and test identities. Prepare live balance transfers, subscription changes, and production cutover separately unless explicitly requested.

Report the config path, linked application and environment, customer identity mapping, prices, changed files, checks run, and remaining user action. Leave a short project note with the billing entry points and maintenance commands, without secrets. Distinguish verified development behavior from a completed production migration.
