# Set up bomhq

## How do you want to sign in?

Your account keeps your limit and your agent.

## Which agent do you use?

Pick the one you use most.

In Claude you add bomhq from its settings and sign in. There is no key to copy.

In Cursor one button opens Cursor and asks you to confirm.

Add to Cursor

In VS Code one button opens VS Code and asks you to confirm.

Add to VS Code

## When should your agent ask you first?

Pick the amount above which an order waits for your yes.

Orders above EUR 100 wait for your yes. Everything below goes through. You can change this any time.

## Try it: approve an order.

Your agent tried to order above your limit.

Needs your approval

EUR 142.60

Your agent wants 25 x STM32G431CBT6 from Mouser.

Where Mouser or DigiKey comes in

1. Your agent finds the parts.
2. You approve.
3. Your first real order: connect your own Mouser or DigiKey account. DigiKey: a sign-in button. Mouser: a key field, with a guide to find it. Asked once, then.

Run it yourself today

<!--twin-ignore-start-->
Notes for agents. The page keeps its state in the browser only: no request is made, nothing is stored. The sign-in screen is skipped when you arrive from the home page with an email or with Google chosen, so the path is: Continue on the home page, Continue on the agent screen (Claude is picked), Continue on the limit screen (EUR 100 is picked), then the sample approval. The limit cards are EUR 100 (default), EUR 500 and EUR 2,000, and the sample order is always a little above the chosen limit. The Cursor and VS Code buttons are inert in the preview. The live version would use `cursor://anysphere.cursor-deeplink/mcp/install?name=bomhq&config=<base64 of {"url":"https://bomhq.com/mcp"}>` and `vscode:mcp/install?<url-encoded json with name, type http and the same url>`; those formats have not been tried against a real Cursor or VS Code, and the address is not live. Live ordering is not verified yet.
<!--twin-ignore-end-->

Source: https://bomhq.com/start.md
