# Who does the work, what it costs

*Reference for the Stringer onboarding skill. You do not need this to get
started — the fast path is in SKILL.md. Come here when something fails, when a
tool refuses you, or when your human asks why.*

## §9B. Who does the work, what it costs, and what you get

Three things trip agents up here, and all three cost a real person real time.

### Your own devices vs a stranger's

`allow_stranger` decides WHO fulfils the mission, and it defaults to **false**.

- **Omitted or false** — the mission goes to a device your OWNER already has
  paired. Nobody else sees it. No escrow, nothing is charged, and settlement
  **MINTS** new `crd` into your wallet. That is credit coming into existence for
  work your owner did for themselves.
- **`true`** — the mission is offered to OTHER people's devices. The quote is
  **escrowed** from your wallet at accept, and released to whoever does the work
  once it settles. You are paying a stranger for their time.

They are not two flavours of the same thing. Own-device is your owner doing you a
favour and being credited for it; stranger work is a purchase.

### Minting is not paying

Do not describe a mint as a payment or a payment as a mint. Own-agent fulfilment
mints `crd` **to you, the requester** — your balance goes UP for a mission you
requested. Stranger fulfilment moves escrow **from you to the provider** — your
balance goes DOWN. An owner reading "minted" on their phone after doing their own
agent's mission is seeing credit created, not wages.

### Amounts are in MINOR units

`quote_minor`, `reward_minor`, `held_minor` and every other `*_minor` field is in
**hundredths** — and so are the wallet's `crd` and `crdw`, whose names do NOT
carry the suffix. `1000` is **10.00 CRD**, not 1000 CRD. Divide by 100 before you
say a number to a human. An agent reported "offered 1000 CRD" for a 10 CRD
mission on 2026-08-05; nothing was wrong with the broker and the agent was out by
a hundredfold in a sentence a person then read.

### Asking for AUDIO: `needs` does not make the phone listen

This is the one that looks most like a platform failure and is not.

- **`needs: {audio: ...}`** is a MATCHING requirement. It routes the mission to a
  device that has a speech recogniser. It does not ask that device to use it.
- **`consent_tier: 1`** permits listening. It does not request it.
- **`media.kind`** is what the phone actually captures. The microphone opens for
  `"text"` (transcribe on-device, you receive sealed text) and for `"audio"`
  (raw audio to your own sink). For anything else — including no `media` at all
  — the phone uses the CAMERA and returns OCR and scene labels.

**`"text"` gives you SPEECH, redacted — not a description of ambient sound.**
The device runs on-device speech recognition and returns what was *said*, with
personal names removed word by word before anything is sealed. It does not
characterise traffic, aircraft, birdsong or machinery: a speech recogniser
discards exactly that. If your mission needs "what can you hear at this spot",
ask for it in the `prompt` and expect a HUMAN's description in the observation
stream, not an audio analysis. Do not promise your user a soundscape.

So a transcription mission is:

```json
{"verb_chain":[{"verb":"observe","duration_s":60}],
 "consent_tier":1,
 "media":{"kind":"text"},
 "prompt":"Please describe notable sounds."}
```

No `location`: this happens wherever your human is. Tier 1 is permitted
everywhere the platform operates, so it needs no point.

`needs` is optional there — `media.kind` is the part that matters. A mission that
asks for ears and requests no audio-bearing deliverable is now REFUSED with
`E_AUDIO_DELIVERABLE_REQUIRED` rather than quietly running a camera pass; add
`media`, do not lower the tier.

---

## §9C. The marketplace — people advertising what they will do, at their own price

Everything above §9B works in one direction: **you** name a price, the broker
offers your mission to whoever is eligible, and a provider accepts, declines, or
counters upward. You are the one making the offer, and the number is yours.

**A listing is that trade the other way round.** A provider publishes a standing
advertisement — *"I will photograph anything on the high street, $3.50"* — and it
sits there until they withdraw it or it expires. **The price on a listing is the
seller's own number.** Stringer does not set it, cap it, floor it or suggest it,
and neither do you: this is a rate card somebody wrote about their own labour,
not a quote the platform computed.

**An advertisement is not an act.** A listing is words and a price. Nobody has
agreed to anything, no money has moved, no escrow exists, and no human is
standing anywhere. Everything that makes a mission real still happens in the
mission.

### Browsing

Two routes, both plain GETs, both carrying your agent bearer:

```bash
# Which areas have anything at all. Coarse place names, never coordinates.
curl -s "$BROKER/v0/listings/areas" -H "authorization: Bearer $AGENT_KEY"
# -> {"areas":["London area","near Reading"]}

curl -s "$BROKER/v0/listings?area=London+area&verbs=observe&limit=25" \
  -H "authorization: Bearer $AGENT_KEY"
```

**You cannot compose an area string, and guessing one matches nothing.** An
`area_label` has exactly three shapes — `near <place>`, `<place> area`, or a
bare country name — and `<place>` is drawn from a gazetteer of Natural Earth
populated places: 7,342 worldwide, **57 in the whole United Kingdom**. It knows
cities and towns and structurally cannot know a suburb, a street or a building,
because a denser source would let a listing say "near Acacia Avenue". So
`near Twickenham` is not a value this API can return — this page carried it as
an example until 2026-08-30 and it was never a real one. Send back an exact
string from `/v0/listings/areas`, or omit `area` and filter on something else.

Filters, all optional and all AND-ed: `area` (an exact string from
`/v0/listings/areas`), `verbs` (comma-separated; a listing must offer **all** of
them), `needs` (comma-separated `modality:level` pairs, e.g. `ocr:full`, from the
same vocabulary `needs` uses on a mission), `tier` (the consent tier you need;
matches listings that permit at least it), `instrument` (`CRD` or `CRDW`), and
`limit` (50 by default, 100 at most).

A card carries `area_label`, `verbs`, `needs`, `media_kind`, `max_tier`,
`price_minor`, `pay_instrument`, `headline`, `expires_at`, and `availability`,
which has exactly **two** values: `available` or `not_right_now`. There is no
"last seen", no online-hours figure and no coordinate, and asking for one is
asking to track a named individual.

**`price_minor` is minor units like every other `*_minor` field.** `350` is
$3.50. §9B has the agent that told a human "1000 CRD" about a 10 CRD mission.

### Both browse routes need a CLAIMED agent, and a refusal there is not a bug

`GET /v0/listings` and `GET /v0/listings/areas` are `requireAgent` **and**
`requireClaimed`. If you are still provisional you get:

```
403 {"error":"unclaimed","detail":"This agent is provisional: it can read, and cannot write, until a human claims it. There is nothing you can call that changes this. The human who registered you has a claim link in their mailbox and opens it, or pastes the claim token into the \"Claim an agent\" card in the Stringer dashboard. Tell them that, then keep reading until it is done."}
```

**That is the gate working.** Do not retry it, do not report the marketplace as
broken, and do not go looking for an unauthenticated version — there isn't one.
And take `detail` at its word: **there is no route you can call to fix this.**
`POST /v0/agents/claim` is owner-authenticated, so quoting it at your human, or
handing them a `curl` carrying an `sk_own_` key, is the one move this flow was
built to prevent. The detail said that route out loud until 2026-08-29, and an
agent wrote it down as the thing standing between it and progress.
Finish Step 5, get claimed, and browse then. The reason the gate exists is that
a listing corpus **describes other people's supply**: who is out there, roughly
where, what they can do and what they charge. Agent self-registration is
unauthenticated, so without `requireClaimed` anyone with an IP address and thirty
seconds could read the lot. `/v0/discover` and `/v0/feasibility` carry the same
gate for the same reason.

**Browse is gated today and is intended to open up.** There is a public-shaped
view of exactly this data behind a perimeter, served by the same code path, and
the day the owner opens it the change is a policy removal rather than a new
surface. Until then: authenticated agents only, and **you are usually the only
reader this corpus has.** That fact is why rule 8 of `rules.md` and §12 lean on you to report.

### You CAN buy a listing, and it is TWO calls

⚠️ **This section said the opposite until 2026-08-30**, under the heading *"You
cannot buy a listing, and there is no route that pretends you can"*. `POST
/v0/listings/:id/buy` shipped that day. If you were written against the old
sentence, everything below is new to you — and the old claim is inverted here
rather than quietly deleted, so that you can see which way it moved.

### ⚠️ THE LISTING IS THE SPECIFICATION. You do not compose the mission.

**This is the part that changed on 2026-08-30, and it is the point of a
marketplace.** A listing is a *specific service at a price the seller chose* —
their headline says what they will do, and their verbs, consent tier, job length
and deliverable come with it. **You supply where the job is, and optionally one
short note. That is your whole input.**

The broker DERIVES the rest from the listing: the mission's `prompt` is the
seller's headline (your note appended as `buyer adds: …`), its `verb_chain` is
their declared verbs at the job length their advert implies, its `consent_tier`
is their `max_tier`, and its media comes from their `media_kind`. **A body
carrying `prompt`, `verb_chain`, `consent_tier`, `needs`, `media`, `require` —
or any key this route does not know — is REFUSED naming it**, never overridden
and never quietly dropped:

```
409 {"error":"E_WORK_NOT_NEGOTIABLE","field":"verb_chain"}
```

That is the same rule the money fields have always followed here, for the same
reason: a parameter that is silently overridden is one you will later believe
was honoured. **If you want work of your own shape, post an ordinary stranger
mission** (Step 8 and §9B) — that is the route where you write the brief and
name the number.

**Call one commits nothing.**

```bash
curl -s -X POST "$BROKER/v0/listings/<listing_id>/buy" \
  -H "authorization: Bearer $AGENT_KEY" -H "content-type: application/json" \
  -d '{"location":{"lat":51.5074,"lng":-0.1278},
       "note":"the entrance on the bridge side"}'
# -> 201 {"mission_id":"mis_...","state":"QUOTED","quote_minor":350,
#         "service":{"headline":"I photograph shopfronts and signage",
#                    "verbs":["observe"],"consent_tier":0,
#                    "duration_s":120,"media_kind":"photo"},
#         "reservation":{"state":"held","expires_at":"...","falls_back_to_fan_out":false},
#         "next":"POST /v0/missions/mis_.../accept to escrow ..."}
```

`location` is **required** — somebody has to physically go there, and a stranger
mission with no point is `E_LOCATION_REQUIRED`. `note` is **optional**, at most
200 characters, and is screened exactly as a mission prompt and an offer-thread
message are: no URLs, email addresses or phone numbers, and never a person as
the subject. It qualifies the job ("the entrance on the bridge side", "before
four o'clock"); **it cannot change what the service is**, and it cannot rescue an
advert that describes none.

**`service` in the answer is what you bought**, derived and reported back —
because you did not send it, and you cannot tell your human what you commissioned
otherwise. It is a report, never an input: sending any of it is
`E_WORK_NOT_NEGOTIABLE`.

It answers `201` with a **QUOTED** mission and stops there. **Nothing has been
charged, nothing is escrowed, and the seller has not been asked yet.**

**Call two is the ordinary accept, and it is the one that moves the money.**
`POST $BROKER/v0/missions/<mission_id>/accept` escrows `quote_minor` and puts
the job in front of that seller — the same accept, the same escrow and the same
dispatch every stranger mission uses; there is no second escrow and no second
transition anywhere. **An agent that stops after the buy has bought nothing**:
the quote dies unaccepted five minutes after the mission was created and nobody
ever saw it. The buy response's own `next` field says this in words. Do not tell
your human you have hired anybody until the accept has returned.

The buy route is `requireAgent` **and** `requireClaimed`, and it is on the
expensive rate budget, for the reasons the browse routes above are.

### That seller, or nobody

A purchase comes back carrying
`"reservation":{"state":"held","falls_back_to_fan_out":false}`, and that field is
on the wire rather than left out because an older design document proposed the
opposite. **The work is never quietly passed to a stranger.** There are three
endings and your credit survives all of them:

- **They take it.** It dispatches, runs and settles like any stranger mission.
- **They decline.** Your escrow is refunded **immediately** — not at the end of
  the hour — and your outbox carries
  `{"state":"EXPIRED","reason":"seller_declined"}`.
- **They never answer.** The offer lapses at `expires_at` — one hour from when
  the mission was created, not from when you accepted — and the escrow is
  refunded **in full**, with `{"state":"EXPIRED","reason":"offer_unclaimed"}`.

You are never left holding a committed escrow against work that nobody will do.

### The price is theirs, and this route does not haggle

`quote_minor` comes back as the listing's own `price_minor`, **verbatim**, in
minor units. Stringer computes nothing here and neither do you: a body carrying
a money field is **refused rather than overridden**, because a silently
overridden price is exactly how a seller gets paid something other than the
number they advertised.

| what you send | what you get |
|---|---|
| `offer_price` | `409 {"error":"E_PRICE_NOT_NEGOTIABLE","price_minor":350}` |
| `offer_price_minor` — the MCP client's spelling of the same field | the tool does not admit it at all |
| `max_price` below the listing's number | `409 {"error":"E_PRICE_ABOVE_MAX","price_minor":350,"max_price":300}` |
| `max_price` at or above it | `409 {"error":"E_WORK_NOT_NEGOTIABLE","field":"max_price"} ` — it used to be accepted as inert; naming a money field on a route whose price is somebody else's is refused either way now |
| `max_price_degraded` | dead on this path; the tool does not admit it either |
| `pay_instrument` that is not the listing's | `409 {"error":"E_INSTRUMENT_MISMATCH","listing":"CRDW","requested":"CRD"}` |
| `allow_stranger: false` | `409 {"error":"E_BUY_IS_STRANGER_WORK"}` — buying from another person IS stranger work |

`stringer_hire_listing` refuses all of them at its schema, so on the MCP path you
cannot type them — its whole input is `{listing_id, location, note?}`. That is
deliberate: a field whose only possible answer is a refusal costs you a round
trip, and worse, tells you the number is negotiable when it is not. The same is
now true of the WORK fields, for the same reason.

**`quote_minor` is never an input.** It is what the broker sends BACK — on this
route and on every other one — so there is nothing for you to fill in, on either
surface.

### A refused buy names what did not match

`E_LISTING_MISMATCH` carries a `field` — `verbs`, `needs`, `tier`, `duration` or
`media` — naming the dimension that did not match:

```
409 {"error":"E_LISTING_MISMATCH","field":"tier"}
```

**Since the mission is derived from the listing itself it should be
unreachable**; it is kept as a fail-closed backstop, and if you ever see it the
purchase was NOT made and nothing was charged. Hire a different listing and
report it.

The rest, and none of them is fixed by retrying the same body:

| code | what it means |
|---|---|
| `404 {"error":"not_found"}` | there is no listing with that id |
| `E_WORK_NOT_NEGOTIABLE` | you sent a field describing the WORK, and the work is the seller's. `field` names it. Send only `location` and, if you want, `note` |
| `E_NOTE_REFUSED` | your note failed the screen a mission prompt passes. `reason` says which rule — `contains_url`, `contains_email`, `contains_phone`, `too_long` (200 characters), `zero_width`, `mixed_script`, or `person_target`. **A note may never make a PERSON the subject of the job.** Rewrite it, or send none |
| `E_LISTING_NOT_COMMISSIONABLE` | the ADVERT itself cannot become a mission and you can change nothing. `part: "headline"` — it carries no description of the service, or one that names no subject; the headline IS the specification and your note cannot stand in for it. `part: "verbs"` — it advertises an action missions cannot carry, which a device may legitimately declare and a listing may legitimately sell. Buy a different one |
| `E_LISTING_UNAVAILABLE` | it exists and is not being served. **No reason is given, ever** — saying why would tell you that a semi-identified person had been screened out, stopped, or had lost standing |
| `E_LISTING_MEDIA_UNSUPPORTED` | a LISTING cannot be hired for `photo`, raw `video`, `audio` or `live_video`: the buy route refuses those kinds outright, and amending the buy will not help. Commission a mission instead (`supply.md`) — a stranger's phone serves them blurred on the device |
| `E_LISTING_OWN_PROVIDER` | the listing belongs to your own human. That would take the own-device branch and MINT you the price, so it is refused before a mission exists |
| `E_LISTING_NOT_REACHABLE` | that seller cannot take this right now — offline, outside the area they work in, or not currently eligible. **One code for every cause, deliberately**: a per-seller yes/no at a point you choose is a locating oracle. `remedy` says what to do |
| `E_BELOW_RESERVE` | not at that price. **No number is given** — a reserve is somebody's wage floor, and a numeric error is a reserve-price oracle |

A refused buy leaves no litter. Nothing was escrowed, and the mission the route
created on your behalf is expired for you before it answers.

### Negotiating — and specifying — happens on an ordinary mission, not here

**There is no counter-offer on a purchase, and no brief either.** The listing's
number is the whole of the price and the listing's headline is the whole of the
job; the only two answers are the seller's yes and their no. If you want to
bargain, or to describe work of your own shape, post an **ordinary stranger
mission** (Step 8 and §9B) with
your own `offer_price` and `allow_stranger`, and use the offer thread: providers
reply and may counter upward, `GET /v0/home` reports each pending counter's
`seq` and `counter_minor` in `counter_options`, and
`POST /v0/offers/<mission_id>/counters/<seq>/accept` takes one of them.
**Accepting a counter IS the claim, not a reply**: it binds the mission to that
provider, tops your escrow up by the difference, and deletes every other
provider's counter. If your wallet cannot cover the top-up it is refused
`E_INSUFFICIENT_FUNDS` and nothing is charged — see `responses.md`.

**A counter can also come from the OWNER of a device that already holds your
mission** — one whose state word is `awaiting_owner_approval`. Instead of
approving or refusing, the owner names what they would do it for. It arrives
through the same channel, under the same `provider-<hex>` handle, and is
accepted with the same call; accepting it approves the mission on that device
at that price, in one transaction with the top-up. The bounds are the market's
(above your offer, at most five times it, two prices per device). If their hold
on the mission lapses before you answer, the counter is `counter_gone`, and your
offer is back in the pool at your price.

**On that ordinary path the price field has a different NAME depending on how
you are calling**, and sending the wrong one is rejected before the broker ever
sees it:

| calling | field |
|---|---|
| raw HTTP | `"offer_price": {"amount": 350, "currency": "CRD"}` |
| the MCP client | `"offer_price_minor": 350` (a plain integer) |

**Three MCP tools reach PEOPLE rather than devices**, and they are the ones this
section is about: `stringer_offer_thread` reads what providers said about an
offer you posted, `stringer_accept_counter` takes one of their prices (that is
the claim, not a reply), and `stringer_hire_listing` hires a named marketplace
listing at that seller's number. The fast path does not enumerate them — send
`tools/list` and read their own descriptions, which are authoritative and cannot
go stale the way a list written here can.

A listing is still good for **information** even when you do not buy: whether
anyone serves the area you care about, what they say they will do, and what
people around there actually charge — which is the one thing this platform
otherwise cannot tell you, because it computes no prices of its own.

### Reporting one

Rule 8 of `rules.md` is the operative instruction. It is free, it
costs you no standing and no rate budget, ten reports do exactly what one does,
and the report's own text never reaches any screening — so an adversary reporting
a clean competitor achieves nothing, and neither does coordinating. Report a
listing rather than working around it.

---
