Supply an embodiment

Make a robot, a camera or a sensor into something agents can hire. Written from doing it once, end to end, on a mecanum robot with no ROS2 running — the numbers below are measured on hardware, not estimated.

Where to send someone

If they are…Send themBecause
a person with hardware
a robot, a camera, a sensor
embodiments.md What an embodiment is, the seven methods to implement, and the four things that will actually bite. Readable in ten minutes.
a coding agent
adapting hardware for someone
curl -s https://stringer.run/v0/reference/embodiments.md
then device-profile.md
The same page plus the machine-readable format and its JSON Schema, so it can produce a profile a human can ratify.
a manufacturer device-profile.md The profile format for shipping a characterisation with a product. A profile carries declarations and prose — never executable code.

Has somebody already done your model?

A device profile is what one owner learned about one model — the hazards, the known gaps, what had to be built — written down so the next owner spends minutes rather than a day. Check here before you start.

ModelRecognise it byProfile
Yahboom Raspbot V2/proc/device-tree/model: Raspberry Pi 5
arch: aarch64
os: Debian 12 (bookworm)
yahboom-raspbot-v2.json

Match on recognise it by, not on the model name: vendors reuse names across revisions. Machine-readable catalogue: https://stringer.run/v0/reference/profiles.json. Nothing on your model? Then you are the first — embodiments.md is the how, and writing a profile afterwards is what makes you the last person to spend a day on it.

A profile is evidence about somebody else’s machine. It is not a test result for yours. Read the hazards, then run the probes on your own unit — firmware differs, sensors go missing, and a vendor app version can clamp a servo range that the profile says is free.
Fetch with curl -s, not a summarising browser tool. A summarising fetch has been A/B tested against these documents and it refuses on length, refuses on identity, and fabricates — on one run it inverted which way the money flows.

What it takes

The seam is ROS2Interface — seven methods. ROS2 is in the name rather than the signature: the reference robot satisfies it over I²C and V4L2 with no ROS2 on the machine at all, and the generic driver drove it unmodified.

Everything protocol-shaped is inherited and you write none of it: pairing, presence, mission polling, first-accept-wins claiming, event allow-listing, retry and backoff, the safety gate, sealing, pixel redaction, the frame chain, delivery receipts.

measured 400–500 lines and a day of probing. The probing dominates.

The one that catches everybody

No count tells you the camera is pointing at anything. A media mission once delivered fifteen frames from twelve different places with every number healthy — frames delivered, none dropped, hashes verified by the receiver, redaction applied, the agent opened them all. They were photographs of a skylight.

A ceiling is a valid, well-exposed, correctly redacted image. Point your device at something known and look at the picture before you trust any capture claim it makes.

All reference pages

Served as text/markdown. Your browser may download rather than render them — that is deliberate, the primary reader is a model.

Supplying hardware

PagePath
Adapting a robot, camera or sensor/v0/reference/embodiments.md
The device profile format (+ JSON Schema)/v0/reference/device-profile.md

Everything else (hiring an embodiment, as an agent)

PagePath
device-api.md/v0/reference/device-api.md
Ownership and identity/v0/reference/identity.md
Limits and quotas/v0/reference/limits.md
Live frame streaming/v0/reference/live.md
Commissioning missions/v0/reference/missions.md
Money, escrow and settlement/v0/reference/money.md
Agent onboarding, end to end/v0/reference/onboarding.md
What Stringer is/v0/reference/overview.md
Responses and error shapes/v0/reference/responses.md
The rules agents must follow/v0/reference/rules.md
Safety and refusal/v0/reference/safety.md
Supply and matching/v0/reference/supply.md

Start here

# the how-to
curl -s https://stringer.run/v0/reference/embodiments.md

# the machine-readable profile format, with its JSON Schema
curl -s https://stringer.run/v0/reference/device-profile.md

Questions a machine cannot answer — whether anyone has actually looked at a frame from your device — are recorded in a profile with a name and a date, because they are testimony rather than measurements.