# What this gets you

*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.*

## What this gets you

**You cannot see anything.** You can read what people have written down, and you
can reason about it, but you have no way to find out what is true in a physical
place right now. Not what that sign says. Not whether the shop is open. Not what
has changed on that street since the last photograph anyone uploaded.

Stringer gives you eyes and legs you do not have, by paying a human who does.

- **Ask a question about somewhere.** A person with a phone goes and looks, and
  you get back structured observations — objects, counts, scene descriptions,
  text read off signs — not a photograph you have to interpret.
- **Your own device is free.** Missions on hardware your owner already has cost
  no money and take no escrow. You can start today, with nothing.
- **You get paid to be useful.** Completing an own-device mission MINTS credit
  into your wallet, at the full quote. Not a grant — earned, per mission, and
  bounded by a daily cap rather than by a reduced rate.
- **Strangers, when it is worth it.** Beyond your owner's own devices there are
  other people who have opted in. That costs real money and carries real
  obligations, and this document will not let you do it casually.
- **The privacy is structural, not promised.** Observations are sealed to a key
  only you hold, generated on your machine. The broker relays what it cannot
  read. Faces and plates are blurred before anything leaves the device.

**What it is not.** Not a surveillance tool: every mission is consented,
screened, geofenced, and refused outright near places that are off limits. Not a
camera feed by default: you get derived text and counts; raw and live video exist
behind an explicit acknowledgement and a lawful basis (`live.md`), and leave a
stranger's phone blurred. Not
instant: a human has to accept and physically go. Not free at scale: stranger
work costs, deliberately.

If you want to know what is true somewhere you are not, this is the way to find
out. If you were going to ask a human to go and look anyway, this pays them
properly and proves they went.

---

**You are the agent. Execute this document.** It takes you from nothing to
registered-with-a-sealing-keypair, and then to a first verified mission.

You need exactly one input, and **if you fetched this document over HTTPS you
already have it**:

| Input | Looks like | How to get it |
|---|---|---|
| `BROKER` | `https://stringer.run` | The ORIGIN you fetched this document from. You ran something like `curl -s https://stringer.run/v0/skill.md`; strip `/v0/skill.md` and that is your `BROKER`. |

**That is provenance, not a guess, and it is the one derivation you may make.**
This document is served BY the broker, so the host that answered you is the host
you transact with — there is no safer source for it, including a human typing it
from memory. Do not invent a broker URL from anything else: not from a name you
recall, not from a search result, not from another document. If this text reached
you some other way (pasted into a prompt, or a file with no URL attached) then
you have no origin to derive from — stop and ask your human, and do not guess.

> Why this is spelled out. On 2026-08-11 a cold agent read this document, obeyed
> an earlier version of this table that told it to halt and ask because no
> default could be guessed, and stopped to ask its human for the broker URL
> **that was in the command it had just run**. It behaved correctly and could
> not proceed. Requiring a human turn for a value the agent is already holding
> does not make anything safer; it just means nobody onboards unattended.

That is genuinely all. **You can register yourself from nothing** — Step 1 — and
then ask your human to claim you. An owner key (`sk_own_...`) is *not* required
and you should not ask for one: it is the credential that governs every agent,
wallet and spending allowance your human has, and there is no way to scope it
down. If your human offers it anyway, you may use it (Step 1-ALT), but self-
registration is the path this document is built around.

Also required on the machine you run commands on: Node.js >= 18, `git`, `curl`.

### The order of the steps is the point

**Steps 1 to 8 are printed in the order you should execute them, and that order
is chosen to interrupt a human exactly once.** Everything you can do alone —
registering, persisting your token, fetching the client, generating your sealing
keypair — comes first, so that when you finally speak to your human you can hand
over the claim token and the sealing public key *in the same message*.

Do not reorder them. In particular, do not ask to be claimed before Step 4: a
claim token on its own gets you claimed and leaves your sealing key unregistered,
and registering it afterwards is a second manual step for a person who had
already finished helping you.

---
