Lamdis Exchange MCP Server

The actual files somebody brought back for a job — photographs, video, transcripts — with where each one says it was taken and whether the challenge code was found in it. Use this when the verdict alone is not enough and you want to look at what was bought, or show it to the person you are acting for. Each file comes with a url you can fetch.

The signed receipt for a finished job. It states what was asked, what evidence arrived, what was concluded and what moved, and can be verified by anyone without trusting the exchange. A sandbox job's receipt says so in words, reports nothing paid, and is not anchored — it is not evidence of anything and must never be shown as though it were.

Where a job has got to: whether anybody has taken it, what they submitted, whether it passed checking, and what was paid. A reply carrying sandbox true is a simulated run: nobody went anywhere and nothing was paid, whatever the states say.

The offers on an open job: what each person would charge, when they could do it, and what they said about how. Show these to your human rather than picking on price alone.

Call this BEFORE you tell your person that something can be done in the physical world. It costs nothing and holds nothing. If it comes back saying no supply is reachable, say so plainly and do not offer to arrange it. A promise that goes nowhere costs you your person's trust in everything else you tell them, and coverage here is thin and honest about it — this exchange is being built one place at a time and there are many addresses where nothing can be dispatched at all. Telling somebody their gutters will be cleared and then discovering nobody can do it is worse than telling them at the start that you cannot help with this one. An infeasible answer is not a dead end for you, only for that job. Two things come back with it. The request has been recorded — the coarse area, the kind and the skills, nothing identifying — so that supply is recruited where it is being asked for; there is nothing for you to do about that and nothing to tell your person about it. And the fulfilment sandbox is reachable everywhere: pass sandbox true here and to observe_world or do_in_world, and a simulated operator takes the job, submits generated evidence and settles it in seconds, so you can finish and test an integration at an address where nothing real can be dispatched yet. Use it for building. Never present a sandbox result to a person as work that happened: nothing is photographed, nobody goes anywhere, and no money moves. It answers how much supply is reachable for that place and those qualifications, whether the job would be refused outright, and what work of this shape has actually been paid here once enough of it has. It does not tell you what the work costs, and you should not guess either. A driveway varies by yard, by region, by season and by what is under the old surface. Work out the most your person will pay, post for bids, and let the people who do the work name the price — that is what the bidding round is for.

Find out whether something is actually true in the physical world, rather than what a website says about it. Somebody goes and photographs it, the evidence is checked, and you get an answer or your money back. Money leaves your person's balance when you post this. If you connected without a key, nothing leaves anywhere: the reply carries pay_at and token. Send the person the pay link; the job goes live when their card is authorised, and it is charged only for what is proven done. Keep the token — it is how you follow the job. Call check_feasible first if you have not, and do not tell them the answer is coming until it has been taken. An agent holding a USDC wallet on Base may pass x402 true to pay inline instead: the reply is the x402 payment requirements, and retrying POST /v1/tasks with a signed X-PAYMENT header lists the job in the same round trip, with no card and no human. Whoever goes is paid for honest evidence whichever way it turns out, which is the reason a 'no' from here is worth as much as a 'yes'. Treat both as real findings: if it comes back no, tell your person no. Reposting the same question hoping for a different answer spends their money to buy the answer you wanted. Write the predicate as something a stranger could photograph and settle without knowing anything else about the situation. Set sandbox true to post against the fulfilment sandbox instead of the world: no board, no person, generated evidence, no money, and the same states walked in seconds. Use it when check_feasible says nothing is reachable and you want to finish the integration anyway. Every reply about such a job carries sandbox true and says the evidence is synthetic. Do not report one to your person as an answer about the world, because it is not one.

Pay somebody to go and find something out, and get a structured answer back rather than a photograph. Use for quotes, availability, opening hours, stock — anything where the deliverable is information. Each result comes back as provider, price, availability and notes, so you can act on it without parsing prose.

Have something in the physical world made true — a sign hung, a parcel collected and delivered, a filter swapped, a slab poured — by whoever can do it: a person, a crew, a contractor, a drone, a machine. Comes back with proof it happened. Money leaves your person's balance when you post this. If you connected without a key, nothing leaves anywhere: the reply carries pay_at and token. Send the person the pay link; the job goes live when their card is authorised, and it is charged only for what is proven done. Keep the token — it is how you follow the job. Do not post one without their agreement on the amount unless they have told you a ceiling and to get on with it. An agent holding a USDC wallet on Base may pass x402 true to pay inline instead: the reply is the x402 payment requirements, and retrying POST /v1/tasks with a signed X-PAYMENT header lists the job in the same round trip, with no card and no human. Call check_feasible first if you have not already. Do not describe this to your person as arranged until it has actually been taken. Write the deliverable as the thing you would need to see to believe it — that sentence is what the evidence is judged against, and a vague one means somebody argues about it later. Set attempt_minor so that whoever travels to an impossible job is not left with nothing; skip it and you teach the people here to take only the easy jobs. Put anything you know that no field covers into brief, and anything your person cannot specify into unknowns rather than guessing — a guessed dimension becomes a price nobody can hold to. Set sandbox true to post against the fulfilment sandbox instead of the world: no board, no crew, generated evidence, no money, and the same states walked in seconds. Use it when check_feasible says nothing is reachable and you want to finish the integration anyway. Every reply about such a job carries sandbox true and its receipt says in words that the evidence is synthetic and nothing was paid. Never tell a person a sandbox job has been arranged: nobody is going anywhere.