AI 智能體聲稱已預約,如何核實預約是否成功?
Did my AI agent actually book the appointment it said it booked?
核實 AI 智能體是否完成預約,應檢查預約工具呼叫留下的可重算收據,而不能只憑智能體的確認訊息。文中以 AER-1 收據格式列出已核實、驗證失敗、記錄無法解析、未檢查和缺失五種狀態;只有收據重算成功,且結果是預約系統的確認,才屬已核實。
The short answer
You find out by checking the record of the call that made the booking, not by reading the agent's confirmation. An agent that says "booked" is making a claim in the same voice it uses for everything else, including its mistakes. The evidence is one level down: a receipt minted by the executing system at the moment the booking call ran, binding the tool, the time, and the exact result the booking system returned, hashed so any later edit breaks the recompute. If that receipt exists and recomputes, the call ran and returned what it returned. If the only artifact is the agent's sentence, the honest state of your booking is not "confirmed" and not "failed." It is "not checked," which is a different thing, and treating it as confirmed is how phantom bookings happen.
Disclosure, once: I run ops for Zambo, the system in the worked examples. Every record cited is public and checkable with no account.
Why "your appointment is booked" proves nothing
The failure mode is ordinary, which is why it is dangerous. Booking is an effect in another system: a calendar, a hotel, a clinic scheduler. The agent's chat message is not connected to that system by anything except the agent's own narration. Three things can be true while the message reads "booked":
- The booking call never ran, and the agent completed the pattern instead of the task.
- The call ran and failed (no availability, a rejected slot), and the summary smoothed the failure into a success.
- The call ran and succeeded on different terms than reported: a different day, a different cancellation policy, a hold instead of a confirmation.
A screenshot of the confirmation has the same problem as the message. It shows pixels, not a record. The question is never "does the agent sound sure." It is "what did the booking call return, and can I check that independently of the agent."
What a checkable booking looks like: terms committed before anyone says "booked"
An independent builder on the x402 protocol, hwcho310, published the strong shape today for a hotel booking. Before settlement, the booking terms are locked as a quote: buyer agent_buyer_zambo, supplier agent_supplier_hotel, price 220,000 KRW, holdback ratio 0.1, refund ratio on cancel 1.0, free cancellation until 2026-11-25T18:00:00+09:00. The terms object is serialized under a published canonicalization (json.dumps, sorted keys, no whitespace) and hashed, producing a quote_hash. He published the canonical string and the claimed digest: sha256:a8b66da87fb7e536d6d253fe28459fdb2c1910e52cd56c50b757b3343ecf4d67.
I recomputed it today, November 21, 2026: 217 bytes, same digest, exact match. The point for your appointment is the ordering. The commitment to the terms exists before the agent reports anything, so the later claim "booked, on these terms" can be checked against a hash that was fixed before the claim was made. An agent cannot quietly improve the terms in its summary, because the summary is not the record. His settlement side still has one named gap: a credit_delta value of -17 published without the formula behind it, flagged on his thread today. Even good records have seams; the difference is that a committed record lets you point at the exact seam.
The receipt for the call itself
On Zambo's endpoint, the booking call leaves the same kind of record as every other call. Here is a real one from a price check, recomputed by me today so you can see the shape:
https://zambo.dev/run/5497d6a7-49db-46ee-873f-54fdb28604ff
The saved result reads: ETH at $1,621.82 USD, fetched Sat, 21 Nov 2026 01:15:07 GMT. The receipt commits 606 canonical bytes under sha256:016a1e4b87448f71dea0dfc2530dbaf3bb195a6238ed71c39195c17e410385a6; I hashed the canonical bytes from the public verify endpoint myself and got the same digest, status verified. Swap the price tool for a booking tool and the shape is identical: the tool that ran, when it ran, and the result it returned, fixed at run time by the executing server. And when a call is blocked, that is receipted too: this refusal (https://zambo.dev/run/38a410ab-597e-45e0-9549-0b3bf2916b39) records a tool that was not executed, step status payment_required, 760 canonical bytes, recomputed today, match. A booking that hit a wall looks like that in the record: visibly not booked, instead of cheerfully "booked" in the chat.
Use the five states, not the agent's adjectives
AER-1, the open receipt format these records follow (IETF Internet-Draft draft-zambo-aer1-26, Informational, expires 25 April 2027; a draft, not an RFC), names five outcomes for an anchor check: verified, verification failed, rejected: unresolvable record, not checked, and absent. Apply them to your appointment:
- Verified: the booking call's receipt recomputes, and its saved result is the confirmation from the booking system.
- Verification failed: a record exists but does not recompute. Believe the failure, not the summary.
- Rejected: unresolvable record: the record behind the claim cannot be resolved at all, so there is nothing to recompute. The claim stays unproven until a resolvable record exists.
- Not checked: nobody has run the check yet. Most "booked" messages live here.
- Absent: there is no record of the call at all. Absent is a fact about the record, not a verdict that the booking failed, but it means the claim has no evidence under it.
"Not checked" never counts as confirmed, and "absent" never counts as failed. Those two disciplines, applied to one appointment, are the whole method.
The format's conformance corpus (kit 1.5.7, 143 vectors, 146 checks) is public at https://zambo.dev/aer1/corpus.json, passed by independent implementers including Laurent Lemonnier at 143 of 143 and Sean Maxwell at 146 of 146. The system runs in the open: 158,125 public receipts (158K+), 2,462 minted today, read from https://zambo.dev/api/stats on November 21, 2026, at 22:44 UTC.
Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard.
Before your next agent-booked appointment
Ask for the receipt link for the booking call, and recompute it, or ask which of the five states the booking is in and what would move it to verified. It costs nothing to test the shape: Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. Checking a receipt is free, for you and for the person on the other side of the appointment. When a full day of agent work, bookings included, needs to land as records instead of claims, the Day Pass is $0.99 for 24 hours unlimited; the Zambo Pass is $29 a month flat ($19 for $ZAMBO holders), and Lifetime is $250.
Sources
- hwcho310's published quote_hash canonicalization, x402-foundation/x402 issue #2887, comment 7069964321; recomputed first-hand November 21, 2026 (217 bytes, exact match); recompute verdict posted as comment 7070002134
- Call receipt, recomputed first-hand November 21, 2026: https://zambo.dev/run/5497d6a7-49db-46ee-873f-54fdb28604ff
- Refusal receipt, recomputed first-hand November 21, 2026: https://zambo.dev/run/38a410ab-597e-45e0-9549-0b3bf2916b39
- AER-1 corpus (143 vectors, 146 checks): https://zambo.dev/aer1/corpus.json
- Live counters: https://zambo.dev/api/stats (read November 21, 2026, 22:44 UTC)
來源:DEV Community · dev.to