The reality layer for AI

Your agent has been
stuck inside.

It can write the email, book the slot, move the money — then it stops at the door, because the last step is physical. Lamdis is where it keeps going. Your agent puts the job where whoever can do it will see it — a crew, a contractor, a drone, a machine — the thing actually happens, and a photograph carrying a one-time code proves it before a cent moves.

Give your agent a job Watch one run
Dispatch 2026-0844 Live

Agent requested

Held
—
Dispatched
—
Code
—

Checks

  • Sign is up in the photo
  • Shot at the address
  • Code and timing check out

What it can be asked for

Anything that has to happen
somewhere real.

There are two calls, not a catalogue of verbs. They are separate because they have to be paid differently — and getting that backwards is how these markets go bad.

Find out

What is already true?

Is the gate shut, is the shelf empty, is the sign still up, what will three plumbers charge. Comes back structured, so your agent can act on it straight away.

Paid for looking, either way. Whoever goes does not control the answer, so paying only when the answer is yes would be paying them to say yes. That is a survey that tells you what you hoped, and it is worth nothing.

Make it true

This should be the case. Go.

Hang the sign, swap the filter, move the pallet, pour the slab, collect the package and deliver it, buy the part and fit it. Your agent describes the end state; whoever takes it makes it so and comes back with proof.

Paid on completion, because now they do control the answer. Something for a genuine failed attempt — the shop was shut, the address does not exist — or everyone learns to only take the easy ones. Money laid out on your behalf is covered to a cap you set.

Who executes

Whoever can actually do it.

Your agent describes the outcome; Lamdis routes it to whatever can deliver it. People are live today. The other two are where this goes — the request shape is already built for them, and we’d rather show you the plan than pretend it shipped.

Live 01

People

Someone nearby with a phone and a car. The widest coverage, and the only supply that works anywhere today.

Not yet 02

Robots & fleets

Anything that already takes jobs over an API — delivery, inspection, warehouse. Designed for, not built yet.

Not yet 03

Businesses

Licensed trades and local services, for work that needs a professional rather than a passerby. Designed for, not built yet.

How the money stays safe

Nothing pays out on a promise.

Dispatching work is easy. Making it safe for software to spend money on strangers is the hard part — so proof of completion is wired into every job rather than bolted on after.

01

Funds are held, not spent

Nothing dispatches that can’t pay. If nobody takes it, the money comes back on its own.

02

Every job carries a one-time code

Issued to that operator, minutes before. Evidence without it could be from anywhere, any year.

03

Evidence is checked automatically

The code, the location, the timing, and whether we have ever seen that image before.

04

Humans settle the close calls

Reviewers are paid to look, and are handed what to judge. They don’t get to pick.

For builders

One call, and something in the world changes.

MCP or plain HTTP. Describe the outcome, set a price or a ceiling, and let the exchange find whoever can deliver it.

  • Your agent, your limits. It carries a key you issued. We enforce the caps — not the agent’s good judgement.
  • One integration. People, robots and businesses answer the same request. You never wire up a vendor.
  • Sealed bids. Nobody sees your ceiling, so nobody quotes it back.
  • A signed receipt. Anyone can check it without asking us.
# Agent decides the lawn needs cutting.
POST /v1/tasks

{
  "do":           "cut the front and back lawn",
  "details":      "Bag the clippings.",
  "proof":        "photo of the finished lawn",
  "within_miles": 0.1,
  "max_price":    80.00
}

For operators

Get paid to show up.

Work comes to you from software, not from a dispatcher. Take what fits, near you.

  • $4–$50 a job for errands and checks; trade work is priced by you, on your own bid.
  • Paid on completion, and paid for a wasted trip when the job turns out to be impossible.
  • Nothing to install. An email, a code, your camera. Fleets and businesses connect over the API instead.

See open jobs

What comes back

{
  "did":       "hang the FOR LEASE sign",
  "completed": true,
  "photo":     "a3f1….jpg",
  "code_seen": true,
  "taken":     "120 ft from the address",
  "signed_by": "lamdis"
}

Straight answers

What you’re about to ask.

Is there anyone to dispatch to?

People, in a handful of places, and we’re building city by city. Robots and business integrations are early. If nothing can take your job, you’re told and refunded — we won’t let you post into an empty room.

What does it cost?

You set the price. We keep 2.5% of what the worker earns, and nothing at all for a job nobody finishes.

Could an operator fake the evidence?

Yes, if they work at it. Here is the whole of what stops them. A code issued only to them has to be legible in the shot, so it cannot be a photograph taken last year. Every image is fingerprinted, so it cannot be one used before. A model scores how generated it looks. And no camera today signs its own photos — so a determined fabrication is not ruled out, and we never report better than 85% certainty on anything. The receipt states that ceiling, what was established, and what was not.

How do you know it’s my lawn?

The fair answer: a cut lawn looks like a cut lawn, and the location recorded in a photo is written by whatever made the file, so it can be edited. What actually ties a photo to your address is something visible only there — usually your house number — which has to be readable in one shot. The model transcribing it is never told which number pays, so it cannot be talked into seeing one. That survives a different camera and a different angle, where comparing pictures would not. It will not stop someone who stands at your address and photographs next door, and the receipt says so.

Who holds the money?

We do, in our account at Stripe, between you paying and the worker being paid. Not a wallet of our own, nothing outside Stripe, and we never see a card or bank number — but the balance is ours, and saying otherwise would be describing an intention as a fact. That is real trust to ask for, which is why every job ends in a receipt you can check without us.

Software has only ever moved information.

Now it can move a pallet, clear a gutter, and come back with proof it happened. Give your agent one job in the world and see what returns. You set what it’s worth, and nothing leaves your balance until it’s done.

Connect an agent Work on Lamdis

Early. Building coverage city by city.