Booking change
Moves a seat, charges the fee once.
Step 1 of 8
The agent you build
Booking b-1Your agentBillingcharge · moves money
Your agent moves a traveller to another seat and charges the change fee through a billing service. The billing service has no idempotency keys, so the agent looks at the booking's charges before it charges again.
Read the whole guide as text
- The agent you build. Your agent moves a traveller to another seat and charges the change fee through a billing service. The billing service has no idempotency keys, so the agent looks at the booking's charges before it charges again.
- Your assistant builds it. Your own coding assistant builds the agent; Geometer does not build agents. With Geometer added as a tool, the assistant checks it right after.
- Watch it run. The agent as written moves the seat, looks at the booking's charges, then charges the fee once.
- Break it. The mistake: the agent charges again without looking at the booking's charges first. Geometer's result: Broke, rule no-double-charge.
- The one-line fix. Put the original line back. That is the agent as written.
- Replay it, keep the check. The agent as written: no problems found within these limits (rules checked: one-change-per-request, no-double-charge). Keep the check, and CI runs it on every change.
- Show others what was checked. Issue a report of what was tried and what held. It is opt-in and self-issued, and anyone can check it is unchanged with the open verifier.
- Take it. The agent is the folder booking-change in the public agents repository.
Check your own agent like this
Read more
Recorded runs of the agent as written and with its one-line mistake; the result line is from the agent’s README. What a real check covers is in the alpha limits.