API key
One credential for everything that talks to mvoom from outside the chat: the CLI, your own scripts over HTTP, and the MCP server (which uses it under the hood).
What the API is
Not the same thing as the MCP server. The API is the versioned HTTP contract; the MCP is a program your agent connects to, and it calls this API with your key.
HTTP contract
discover a page → inspect a piece → wait for the signed quote → buy → download. JSON over HTTPS at api.mvoom.com. Prices are signed by the server; a client cannot propose its own.
Clients that use it
@mvoom/cli (capture, connect, auth), @mvoom/mcp (the server), and anything you write. @mvoom/sdk is different: it runs measured recipes on your DOM and needs no key.
Your key
Shown once. We keep only a hash of it; issuing a new one revokes the previous one on the spot.
Key
Paste it at the prompt of mvoom auth, never on the command line.
mvoom_live_••••••••••••••••Use it from the terminal
Install and authenticate
npm i -g @mvoom/cli mvoom auth # paste the key at the prompt mvoom capture https://example.com --piece ".hero" mvoom connect # pair this folder: what you buy lands here
Projects
Folders paired with mvoom connect receive the components you buy from the chat, the CLI or an agent.