Business discovery, with evidence

# Saka business data CLI

[Developers](https://saka.run/developers)[API documentation](https://saka.run/docs)[Authentication](https://saka.run/docs/auth)[Sandbox](https://saka.run/sandbox)[CLI](https://saka.run/cli)[About](https://saka.run/about)[Contact](https://saka.run/contact)

## Install the official Saka CLI

The Saka business data CLI runs on Node.js 22 or later and talks directly to the hosted API. The downloadable package includes all client code and has no external runtime dependencies. Install the public release archive:

```sh
npm install --global https://saka.run/cli/sirerun-saka-1.0.0.tgz
saka sandbox --country US --category Plumbing
```

[Release version and SHA-256 digest](https://saka.run/cli/release.json) describe the current archive. Registry publication to `@sirerun/saka` is pending publisher access; this archive installation does not need access to the private source repository.

## Quotes, balance and exports

For real data, set `SAKA_ACCESS_TOKEN` in your environment to a user-consented OAuth access token for `https://saka.run/api/mcp`. Read the [OAuth guide](https://saka.run/docs/auth) to authorize a compatible client. The CLI sends the token only in the Authorization header. Sandbox requests omit it, even if the environment variable is set.

```sh
saka quote --country US --category Plumbing --limit 5
saka balance
saka export --receipt YOUR_RECEIPT_ID > businesses.csv
```

Quotes are free. Exports return an existing owned purchase as CSV with source attribution. The CLI supports sandbox quotes, real quotes, account balance and exports. It exits nonzero on errors; a 429 reports Retry-After and does not automatically retry. It has no purchase command or automatic debit. Approve purchases through the account page or the capped REST API.

## Choose the right client

Use this CLI for scripts that need quote previews and existing exports. Use the purchasing MCP connector for authorized agent workflows, or the library MCP connector for read-only access to prior purchases. The CLI requires a valid access token for production calls; it does not issue API keys or bypass account authorization. Start with [the fictional-data sandbox](https://saka.run/sandbox), then follow [the API reference](https://saka.run/docs) when you are ready for real records.