The services.dev CLI · services.dev

83 commands. Yours read the folder; the rest are the operations registry's CLI column, each calling one operation against a running brand, and v2's short names stay as aliases. Every command takes --json and exits by the type of its answer: Errors has the codes.

Yours

Command	Does	Who runs it	Operation
`npx services.dev init [name]`	write `services/<id>.ts,` its brief and AGENTS.md	you	—
`npx services.dev dev [--port 8787] [--members N --market tight\|normal\|flush]`	serve every Service on localhost; an agent orders a first job	you	—
`npx services.dev check [--json]`	what each Service sells and leaves you, and anything to fix	you	—
`npx services.dev sdk [--out sdk]`	write the brand's typed client: index.js, index.d.ts and package.json	you	—
`npx services.dev diff <before> <after>`	what a change does on the API, CLI, MCP, SDK, Site, Docs and App	you	—
`npx services.dev verify [--url <url>] [--surface http\|mcp\|all] [--suite <file\|url>]`	run a brand's conformance suite against it, or any suite@1 document: pass, fail, skipped	you	—
`npx services.dev mcp [--url <url>]`	serve this folder's MCP server on stdio, or relay to a running brand's	you	—
`npx services.dev help`	print this	you	—

Calls to a brand

Command	Does	Who runs it	Operation
`npx services.dev jobs get <job>`	read a job	buyer	`job.get`
`npx services.dev jobs wait <job>`	wait up to 50 seconds for a job to finish	buyer	`job.wait`
`npx services.dev jobs list`	the buyer's jobs, newest first	buyer	`job.list`
`npx services.dev jobs accept <job>`	accept a delivered job	buyer	`job.accept`
`npx services.dev jobs send-back <job> <note>`	send a job back with a note, and the AI redoes it	buyer	`job.send_back`
`npx services.dev jobs cancel <job>`	cancel a job before delivery	buyer	`job.cancel`
`npx services.dev jobs end <job> <end>`	end a job at one of its ends, as that end's by allows	buyer	`job.end`
`npx services.dev jobs again <job>`	order an ended job again	buyer	`job.again`
`npx services.dev jobs set-policy <job> k=v …`	set a job's policy values within their bounds	buyer	`job.policy`
`npx services.dev jobs signal <job> <signal>`	raise one of the Service's inbound signals	buyer	`job.signal`
`npx services.dev jobs message <job> <text>`	say something in the job's thread as the client	buyer	`job.message`
`npx services.dev jobs messages <job>`	read the job's messages, oldest first	buyer	`job.thread`
`npx services.dev jobs record <job>`	a job's record as you may read it, oldest first	buyer	`job.record`
`npx services.dev jobs approve <job>`	approve, sign or do a job waiting on a person	person	`job.approve`
`npx services.dev members add <pool> <email> k=v …`	join a Pool, email first and resumable	person	`member.join`
`npx services.dev me availability <availability>`	set your availability	person	`member.availability`
`npx services.dev me ledger`	read your conflicts ledger	person	`member.ledger.get`
`npx services.dev me ledger add <name> k=v …`	add a party to your conflicts ledger	person	`member.ledger.add`
`npx services.dev me ledger checks`	every check of your conflicts ledger	person	`member.ledger.checks`
`npx services.dev me missed`	the open Tasks your own declarations kept from you	person	`member.missed`
`npx services.dev tasks list`	your feed	person	`task.list`
`npx services.dev tasks get <task>`	read a Task's teaser	person	`task.get`
`npx services.dev tasks sheet <task>`	read a Task's sheet	person	`task.sheet`
`npx services.dev tasks pass <task> <reason>`	pass on a Task	person	`task.pass`
`npx services.dev tasks claim <task>`	claim a Task	person	`task.claim`
`npx services.dev tasks clear <task>`	clear a held Task	person	`task.clear`
`npx services.dev tasks packet <task>`	read a cleared Task's packet	person	`task.packet`
`npx services.dev tasks release <task>`	give a held Task back before it is done	person	`task.release`
`npx services.dev tasks offer <task> <member>`	name the member a Task goes to	you	`task.offer`
`npx services.dev tasks attest <task> k=v …`	attest the Task you claimed and cleared	person	`task.attest`
`npx services.dev tasks send-back <task> <defects>`	send the work back with its defects	person	`task.send_back`
`npx services.dev tasks decline <task> <memo>`	decline the Task, with a reasoned memo only the client reads	person	`task.decline`
`npx services.dev tasks recuse <task>`	step aside from a Task you hold, for a conflict	person	`task.recuse`
`npx services.dev tasks extend <task>`	extend your hold on a Task, once	person	`task.extend`
`npx services.dev tasks contest <task> <reason>`	contest a send-back your attested work received	person	`task.contest`
`npx services.dev tasks message <task> <kind> <text>`	reach the client through the job's thread, by kind	person	`task.message`
`npx services.dev subjects list`	the subjects your jobs joined	buyer	`subject.list`
`npx services.dev subjects get <subject>`	read a subject	buyer	`subject.get`
`npx services.dev me subjects`	the subjects where you are of record	person	`member.subjects`
`npx services.dev subjects withdraw <subject> <successor>`	withdraw as the member of record, naming your successor	person	`subject.withdraw`
`npx services.dev clocks list`	the clocks your jobs and their subjects run	buyer	`clock.list`
`npx services.dev clocks get <clock>`	read a clock	buyer	`clock.get`
`npx services.dev clocks ack <clock>`	acknowledge a clock you answer for	buyer	`clock.ack`
`npx services.dev clocks satisfy <clock>`	close a clock you answer for, on evidence on the record	buyer	`clock.satisfy`
`npx services.dev clocks choose <clock> <option>`	choose one of a clock's lapse options at its date	buyer	`clock.choose`
`npx services.dev clocks assign <clock> <member>`	assign the member who answers for a clock	you	`clock.assign`
`npx services.dev subscriptions list`	your subscriptions	buyer	`subscription.list`
`npx services.dev subscriptions get <subscription>`	read a subscription	buyer	`subscription.get`
`npx services.dev subscriptions cancel <subscription>`	cancel a subscription	buyer	`subscription.cancel`
`npx services.dev members login <member>`	mint a member's own session on localhost	you	`member.login`
`npx services.dev asks get <ask>`	read an ask	you	`ask.get`
`npx services.dev asks reissue <ask>`	reissue an open ask's link, to hand to its party again	buyer	`ask.reissue`
`npx services.dev jobs files list <job>`	the files a job holds, each by its sha256	buyer	`job.files.list`
`npx services.dev jobs files put <job> <path>`	put a file in a job's documents plane under its own sha256	buyer	`job.files.put`
`npx services.dev jobs files get <job> <sha256>`	read a file a job holds, by its sha256	buyer	`job.files.get`
`npx services.dev jobs export <job>`	one job's evidence bundle	you	`job.export`
`npx services.dev jobs ledger <job>`	one job, as the owner reads it	you	`job.ledger`
`npx services.dev test-clocks create <frozen_at>`	make a test clock frozen at a time	test	`test_clock.create`
`npx services.dev test-clocks advance <clock> <to>`	move a test clock to a time, or by a span	test	`test_clock.advance`
`npx services.dev events list`	the brand's events after a seq	test	`event.list`
`npx services.dev listen [--forward-to <url>]`	the brand's events	test	`event.stream`
`npx services.dev watches create <url>`	watch events at a URL	test	`watch.create`
`npx services.dev watches list`	the watches this key holds, with their deliveries	test	`watch.list`
`npx services.dev watches delete <watch>`	stop a watch	test	`watch.delete`
`npx services.dev watches replay <watch>`	deliver to a watch again every event it covers after a seq	test	`watch.replay`
`npx services.dev events send <type>`	send an event in	test	`event.inbound`

Aliases

Command	Does	Who runs it	Operation	Status
`npx services.dev order <service> k=v …`	order a job: --max `<usd>,` --key `<key>,` --approved, --policy k=v, --metadata k=v	buyer	`service.order`	alias
`npx services.dev get <job>`	jobs get	buyer	`job.get`	alias
`npx services.dev wait <job>`	jobs wait, until it stops working	buyer	`job.wait`	alias
`npx services.dev accept <job>`	jobs accept	buyer	`job.accept`	alias
`npx services.dev send-back <job> <note>`	jobs send-back	buyer	`job.send_back`	alias
`npx services.dev cancel <job>`	jobs cancel	buyer	`job.cancel`	alias
`npx services.dev approve <job>`	jobs approve	person	`job.approve`	alias
`npx services.dev tick <span> [--to <time>] [--test-clock <tc_>] [--trace] [--compare] [--market <m>]`	test-clocks advance: move dev's own clock, or --test-clock that one, by a span such as 7d or --to a time, only forward; --trace prints each timer fired (owed, fired, order, kind); --compare runs the span three ways and prints each record's sha256; --market checks dev's simulated market	test	`test_clock.advance`	alias
`npx services.dev trigger <type>`	events send: fire a synthetic event, or raise a signal	test	`event.inbound`	alias

What help prints

Output

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/<id>.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 <before> <after>             what a change does on the API, CLI, MCP, SDK, Site, Docs and App
  verify [--url <url>] [--surface http|mcp|all] [--suite <file|url>]  run a brand's conformance suite against it, or any suite@1 document: pass, fail, skipped
  mcp [--url <url>]                 serve this folder's MCP server on stdio, or relay to a running brand's
  tasks offer <task> <member>       name the member a Task goes to
  clocks assign <clock> <member>    assign the member who answers for a clock
  members login <member>            mint a member's own session on localhost
  asks get <ask>                    read an ask
  jobs export <job>                 one job's evidence bundle
  jobs ledger <job>                 one job, as the owner reads it

Taking it live

Command	Does	Who runs it
`npx services.dev deploy`	deploy the brand to its domain, every surface and app at once	you
`npx services.dev preview`	deploy the change to a preview address, on test keys	you
`npx services.dev keys`	make the brand's test and live keys, and rotate them	you
`npx services.dev logs`	tail the brand's request log, live or test	you
`npx services.dev payouts`	read each member's payouts and the Pool's schedule	you

Running it live

Every command the Operate tab runs, with its API call and the page that explains it:

Command	API	Explained in
`npx services.dev deploy`	`POST https://services.dev/v1/deploys`	Deploy
`npx services.dev deploy --live [--breaking]`	`POST https://services.dev/v1/deploys/:version/live`	Deploy
`npx services.dev deploy --live --stages <shares> --hold <span>`	`POST https://services.dev/v1/deploys/:version/live { stages, hold }`	Deploy
`npx services.dev deploy --live --break-freeze --reason <why>`	`POST https://services.dev/v1/deploys/:version/live { break_freeze }`	Deploy

Yours#

Calls to a brand#

Aliases#

What help prints#