The CLI

The CLI tells you in one command whether your key works, what an item returns or why you see no recommendations. It is for diagnostics: to integrate, use the Storefront SDK or the API.

The commands

crossup catalog get --item <id> [--json]
crossup recommendations get --connection <id> --item <id> --placement <key> --surface <surface> [--json]
crossup demo

--json prints a single line ready for jq. Errors go to stderr in both modes.

Configure

It reads the same two variables as the MCP, and nothing else:

export CROSSUP_API_TOKEN="spk_…"
export CROSSUP_BASE_URL="https://salespilot.crossup.ai"

Today the CLI is run from the repository, with bun: bun run apps/cli/src/index.ts …. An installable package is a pending step.

What you will see

crossup catalog get --item itm_demo_remera --json | jq '.item.title, .availability[0].sellable'

{ "en": "Demo T-shirt" }
"in_stock"

crossup recommendations get --connection cn_… --item itm_demo_remera \
  --placement pdp-related-products --surface pdp --json | jq '.decision_id, (.results | length), .reason_codes'

If you don’t see it

What happens	What to do
`configuration_error`	`CROSSUP_API_TOKEN` is missing, or empty. The CLI tells this apart from a `401`
`401`	The key is revoked or badly copied
`404` on an item that exists	It belongs to another store: the key is for another connection
`results: []`	Look at `reason_codes`: Request a recommendation

What’s next

crossup doctor, which tests key, connectivity, quota and a request in one command, and crossup signals tail, to watch signals while you test. Both will reach the MCP too.

The MCP

The same two reads, for an agent.

Your first recommendation

The integration path, for a store.

​The commands

​Configure

​What you will see

​If you don’t see it

​What’s next

The MCP

Your first recommendation

The commands

Configure

What you will see

If you don’t see it

What’s next