CLI

@baseline-markets/cli is the Baseline command-line interface for launching Baseline tokens, inspecting deployments, and installing agent skills.

It exposes two Baseline commands:

• baseline launch builds wallet-compatible launch calls for a new Baseline token.
• baseline info inspects a deployed Baseline token.

It also exposes baseline skills add, which installs packaged Baseline agent skills for agents that can run shell commands.

Use the CLI when you want an unsigned launch artifact before approving anything. Use the SDK when you are building launch, swap, stake, borrow, or leverage flows directly into an app with viem clients.

Install Agent Skills

If your agent supports skills, install the Baseline skills into its environment:

npx @baseline-markets/cli@latest skills add

This installs the packaged Baseline skills, including general CLI workflow guidance, generated launch and info command references, and a Base MCP launch flow for agents that use Base Account approval.

After installing the skills, you can ask your agent to use the Baseline CLI to prepare a launch, inspect a token, or follow the Base MCP flow when Base MCP is available.

For Base MCP specifically, the base-mcp-baseline skill tells the agent how to prepare unsigned calls, validate the artifact, submit the calls through send_calls, show the Base Account approval link, and poll request status after approval.

Build Launch Calls

baseline launch builds a launch artifact with chain, account, bToken, and ordered calls.

npx @baseline-markets/cli@latest launch \
  --mode zrp \
  --chain-id 84532 \
  --account 0x0000000000000000000000000000000000000001 \
  --name "Example Baseline Token" \
  --symbol EBT \
  --reserve 0xB85885897D297000A74eA2e4711C3Ca729461ABC \
  --total-supply 1000000000 \
  --output .context/launches/example-launch.json

The output artifact is a superset of the Base MCP send_calls payload:

{
  "chainId": 84532,
  "chain": "base-sepolia",
  "account": "0x0000000000000000000000000000000000000001",
  "bToken": "0xBToken",
  "calls": [
    { "to": "0xTarget", "data": "0xCalldata", "value": "0x0" }
  ]
}

For external executors, submit artifact.chain and artifact.calls exactly as emitted. Keep chainId, account, and bToken for validation and reporting.

For Base MCP, this maps directly to send_calls.

Launch Modes

ZRP

zrp is the default zero-reserve pool launch mode. It mints the full BToken supply straight into the pool and starts without an initial reserve seed, so the deployer needs no balance or approvals.

The artifact contains a single call: Relay launch.

Use --initial-fdv to set the launch valuation — the fully diluted valuation in reserve units, quoted when circulating supply first exits the frozen zone (5% of supply). It defaults to the protocol minimum.

Standard

standard launches with reserve liquidity. It requires both initial pool BTokens and initial pool reserves:

npx @baseline-markets/cli@latest launch \
  --mode standard \
  --chain-id 84532 \
  --account 0x0000000000000000000000000000000000000001 \
  --name "Example Baseline Token" \
  --symbol EBT \
  --reserve 0xB85885897D297000A74eA2e4711C3Ca729461ABC \
  --total-supply 1000000000 \
  --initial-pool-btokens 900000000 \
  --initial-pool-reserves 1 \
  --output .context/launches/example-launch.json

The call order is:

1. Relay createBToken
2. BToken approval to the Relay
3. Reserve token approval to the Relay
4. Relay createPool

Launch Flags

Supported Chains

Use the chain ID and reserve token for the selected network:

Robinhood also supports USDG (0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168) as a reserve token.

Treat Ethereum mainnet, Base mainnet, HyperEVM, and Robinhood Chain as production. Confirm the chain, token name, symbol, supply, reserve, fees, creator, and fee recipient before submitting calls.

Base MCP Handoff

When using Base MCP, keep the CLI in unsigned mode and submit only the artifact fields Base MCP needs:

{
  "chain": "base-sepolia",
  "calls": [
    { "to": "0xTarget", "data": "0xCalldata", "value": "0x0" }
  ]
}

Use artifact.chain directly and preserve call order. Do not include artifact.account in the send_calls payload; Base MCP uses the connected Base Account session for approval and execution.

Execute Locally

By default, baseline launch only builds unsigned calls. Execute locally only when you explicitly want the CLI to submit transactions with a private key:

BASELINE_PRIVATE_KEY=0x... npx @baseline-markets/cli@latest launch \
  --execute \
  --mode zrp \
  --chain-id 84532 \
  --name "Example Baseline Token" \
  --symbol EBT \
  --reserve 0xB85885897D297000A74eA2e4711C3Ca729461ABC \
  --total-supply 1000000000

Do not use --execute when another execution layer is responsible for approval and submission. Base MCP, for example, consumes the unsigned calls artifact and handles user approval through Base Account.

Inspect A Token

After a launch completes, inspect the bToken:

npx @baseline-markets/cli@latest info 0xBToken --chain-id 84532

Use --format json for structured output:

npx @baseline-markets/cli@latest info 0xBToken --chain-id 84532 --format json

Safety Boundaries

• Prefer unsigned artifacts for agent-assisted or externally executed launches.
• Do not give an agent a private key unless the user explicitly chooses local CLI execution and understands the signer boundary.
• Preserve the emitted call order and calldata.
• Validate account, chainId, chain, and calls before submission.
• zrp artifacts should have one call; standard artifacts should have four calls.
• Ambiguous failures should be recovered from by reading on-chain state before retrying.