Source: https://tenderlead.co.uk/cli
Documentation index: https://tenderlead.co.uk/llms.txt

# Let an agent qualify your tenders.

Install `@tenderlead/cli` and give a scoped token to your coding agent or scripts. They can use the same tender, profile, pipeline and insight tasks as the signed-in product, subject to your account tier.

Use the same qualify, check and prepare workflow from an agent. Bid-preparation workspace commands require separately enabled Team-pilot access; installing the CLI does not unlock them. [See the preparation pilot.](https://tenderlead.co.uk/product#preparation)

[Read as Markdown](https://tenderlead.co.uk/cli.md) [Documentation index](https://tenderlead.co.uk/llms.txt)

[View @tenderlead/cli on npm](https://www.npmjs.com/package/@tenderlead/cli)
[See the CLI in the product](https://tenderlead.co.uk/product#cli)

Requires Node.js 18 or newer and an active TenderLead account.

```
# Install once
npm install --global @tenderlead/cli
 
 # Open API access in TenderLead Settings
tenderlead login
 
 # Search, score a match, then move it into the pipeline
tenderlead tenders search
tenderlead tender score CONTRACT_ID
tenderlead pipeline add CONTRACT_ID
```

## Choose what each token can access.

The CLI connects only to TenderLead. Each token has explicit read and write scopes for tenders, profile, pipeline, insights, feedback and workspace routes. Your account entitlement still applies; existing Starter accounts retain their limits.

Profile updates require `profile:write` ; on-demand scoring requires Pro or Team and `tenders:write` . Other saved-work commands use their own scopes.

Tokens are customer-scoped, shown once, revocable and expire after 90 days. The CLI does not store them on disk. Keep them in your environment, never in a repository or shared prompt.

Sign-in, token management, subscription changes and permanent account deletion remain in the browser.

Connecting Zapier? Read the [TenderLead API reference](https://tenderlead.co.uk/api-docs) for authentication, requests, response fields and errors.

## Set up the CLI.

- 01

### Install the package.

Install `@tenderlead/cli` globally with npm on the machine where you want to qualify tenders.

- 02

### Create a token in Settings.

`tenderlead login` opens API access. Sign in, create a token, then set it as `TENDERLEAD_API_TOKEN` in your shell.

- 03

### Work with your agent.

Ask it to search and score notices, update the matching profile, manage pipeline stages, read insights, send feedback or work with bid drafts and evidence on eligible tiers.

## CLI commands.

### Tenders and matching

`whoami`
`brief`
`tenders search`
`tender score`
`profile show|apply`

### Pipeline and learning

`pipeline list|add|update|remove`
`insights`
`feedback tender|product`

### Bid workspace

`bid-profile show|apply`
`outlines show|create`
`drafts list|show|create|export|import`

Available only where the account is explicitly eligible for the workspace.

### Evidence and templates

`evidence list|enrich|upload`
`templates list|upload|remove`
`evidence-packs list|show|create`

Workspace evidence follows the same eligible-account boundary.

Pro covers search, scoring, pipeline and insights. Existing Starter accounts retain alerts and search. Workspace commands need an eligible account. Run `tenderlead --help` for flags. Commands that change or remove saved data ask for a typed confirmation. Reviewed automation can pass `--yes` .

## Need the briefing before you have an account?

Start with one personalised preview brief, then decide whether TenderLead is useful for your firm.

[Score tenders for my firm](https://tenderlead.co.uk/personalised-preview)