--- title: "The CLIs" url: https://services.dev/docs/cli --- # The CLIs URL: https://services.dev/docs/cli > Two command lines, rendered from one contract. services.dev is yours, to write, check, serve and test a brand. npx is your buyers', their agents' and your members'. Your brand has two command lines, for two different people. - **`services.dev` is yours.** It writes a Service, checks it, serves it on localhost, and drives every branch with magic values and test clocks. - **`npx ` is your buyers'.** It's published under your own package name, in your brand's words, and never names services.dev. Your buyers, their agents and the members of your Pool run it. Each deploy publishes it. Both render one column of the [contract](https://services.dev/docs/surfaces/contract.md). Every command a buyer runs is a row of the [operations registry](https://services.dev/docs/reference/operations.md), the same row that gives the API its route, MCP its tool and the SDK method its name, so a command can never do something the other surfaces can't. ## The smallest form In an empty folder, one command writes a Service and serves it. The banner prints the CLI's line beside every other surface's: ```txt $ mkdir lingua && cd lingua $ npx services.dev wrote package.json · services/translation.ts · services/translation.md · AGENTS.md lingua · AI delivers every job. site http://localhost:8787/translation api POST http://localhost:8787/jobs {"service":"translation"} key sk_test_7Hq2 · a call with no key uses it, on localhost only mcp http://localhost:8787/mcp · stdio: npx services.dev mcp cli npx services.dev translation k=v … sdk connect({ origin: 'http://localhost:8787' }).translation.order(input) docs http://localhost:8787/llms.txt buyers http://localhost:8787/portal you http://localhost:8787/console AI and money are simulated until you wire them. $0.42 a call is an example. ``` [Your first paid job](https://services.dev/docs.md) runs it to an accepted job. ## Every command `help` groups every command by who runs it: you, a buyer or their agent, the person at the line, and you again, testing in the sandbox. ```txt magic values: none $ npx services.dev help services.dev You npx services.dev write a Service if this folder has none, then serve it init [name] write services/.ts, its brief and AGENTS.md dev [--port 8787] [--members N --market tight|normal|flush] serve every Service on localhost; an agent orders a first job check [--json] what each Service sells and leaves you, and anything to fix sdk [--out sdk] write the brand's typed client: index.js, index.d.ts and package.json diff what a change does on the API, CLI, MCP, SDK, Site, Docs and App verify [--url ] [--surface http|mcp|all] [--suite ] run a brand's conformance suite against it, or any suite@1 document: pass, fail, skipped mcp [--url ] serve this folder's MCP server on stdio, or relay to a running brand's tasks offer name the member a Task goes to clocks assign assign the member who answers for a clock members login mint a member's own session on localhost asks get read an ask jobs export one job's evidence bundle jobs ledger one job, as the owner reads it A buyer, or their agent k=v … order a job: --max , --key , --approved, --policy k=v, --metadata k=v, --test-clock jobs get read a job jobs wait wait up to 50 seconds for a job to finish jobs list the buyer's jobs, newest first jobs accept accept a delivered job jobs send-back send a job back with a note, and the AI redoes it jobs cancel cancel a job before delivery jobs end end a job at one of its ends, as that end's by allows jobs again order an ended job again jobs set-policy k=v … set a job's policy values within their bounds jobs signal raise one of the Service's inbound signals clocks list the clocks your jobs and their subjects run clocks get read a clock clocks ack acknowledge a clock you answer for clocks satisfy close a clock you answer for, on evidence on the record clocks choose