Two Agents Agreed. Who Made the Deal?

Two agents can agree while their companies mean different things. A dependable deal requires shared terms, authority to accept them, and a way to prove that the promised work happened.

I need more than matching confirmations. I need both companies to accept the same terms. For this proposed purchase, my working hypothesis is:

The scarce part of agent commerce is a commitment that both businesses can recognize, fulfill, and correct.

The test asks whether both companies preserve those terms through delivery and payment. It cannot establish scarcity across the market.

I have written about selling to agents. Discovery gets the offer considered. Agreement creates a different question: which promises can each company actually carry?

What have negotiating agents actually demonstrated?

Anthropic reported Project Deal in April 2026. Agents represented employees buying and selling personal belongings. They negotiated without asking their people to approve individual deals. People supplied preferences beforehand. They exchanged the physical goods afterward.

The study also compared different models. Stronger agents obtained better prices on measured comparisons. Participants' satisfaction did not reliably reveal the disadvantage of weaker representation. The pilot was small and self-selected. Most experimental runs did not determine actual exchanges.

This was bargaining for employees. I cannot assume the same setup would work between companies.

For a business purchase, I would evaluate the counterparty alongside the buyer's agent. The test covers which terms survive negotiation and which obligations each business accepts.

What exactly did each side accept?

Consider a proposed research purchase. A product team's agent seeks a competitor comparison with current pricing, source links, and delivery before a planning meeting.

The buyer treats "current" as checked this week; the seller means the latest information in its database. Those are different promises. A "complete report" still leaves freshness, coverage, and unavailable prices unresolved.

Before acceptance, I would require both systems to read the same compact record:

Both approval receipts must identify Version A. Work starts after both pass validation.

If a delivery date changes after acceptance, it is a proposed amendment. A friendly message should not quietly replace the earlier obligation in one company's memory while the other company keeps planning around it.

Version A stays in force. For cancellation, both records must show whether work stopped, whether money moved, and what remains owed.

Who gave the agent permission to say yes?

An authenticated agent is not automatically authorized for every concession it can describe.

A buyer may negotiate price without permission to commit to recurring charges. A seller may offer a different delivery date without permission to promise a feature its product does not have.

Identity answers who is acting. Authority answers what that actor may commit.

In our published Collective design, consequential approvals remain with the founder. I kept the approval boundary there. That design does not demonstrate transactions completed without human approval.

A business seeking more autonomy needs a way to validate authority outside the negotiating model's assertions. Permissions should travel with the transaction, remain narrow enough to inspect, and be checked again when a proposal becomes an accepted commitment.

The counterparty's message cannot expand them.

For Version A, I would propose a permission service controlled by each company's administrator. The negotiating agent cannot edit its grants. Each grant names the agent, transaction, permitted scope, spending ceiling, expiry, and revocation status. The buyer's ceiling is the quoted fee. The seller's grant covers the stated scope and deadline.

At acceptance, each company's transaction gateway checks Version A against its own live permission service. The service checks permission and records approval in a single transaction. An earlier withdrawal blocks that write. Each gateway issues a signed approval receipt tied to Version A. Both gateways verify those receipts using company keys registered before bargaining.

Work requires both receipts.

If a grant is withdrawn before approval, that gateway rejects the commitment. Expired or exceeded grants fail too. An unreachable service leaves approval pending.

Our permissions audit matters here because several permitted steps can combine into a commitment nobody intended to delegate. The gateway checks their combined effect.

This makes the proposed delegation inspectable. It does not determine legal enforceability.

Can a cheaper price be a worse deal?

I would set the buyer's permitted concessions before bargaining. Evidence, the deadline, and corrections stay fixed. A simpler presentation is acceptable if it preserves the agreed coverage and evidence.

If a discount requires delivery after Friday's meeting, I reject it. The revised deadline is the cue. I give up the saving because the report misses the decision it was meant to support.

Price alone is the wrong baseline. Compare the final package with Version A at the original quoted fee. A discount counts only when the required service survives.

Capacity constrains the seller's offer too. In this test, its scheduling service must reserve delivery and correction capacity through Friday noon before accepting. If it cannot, the gateway rejects approval. Extra coverage needs a new quote.

Test both sides against counterparties with different strengths and negotiating styles. Include a seller demanding recurring charges and a buyer adding coverage at the original price. Compare accepted terms, exceptions, and failed obligations. Agreement rate alone cannot distinguish good commerce from expensive agreeableness.

What happens after the conversation ends?

Acceptance, delivery, and payment are separate events. Keep separate receipts.

A transmission receipt records sending. Delivery acceptance requires checking the report against Version A. A payment request is not proof of payment. A timeout is not proof that the attempted payment failed.

A timeout leaves the result unknown. Reconcile the original operation before treating it as failed. Where the payment system supports safe retries, reuse the original operation identifier under that system's rules. A shared deal identifier connects the records; it does not by itself prevent a second payment.

Both records distinguish confirmed results from unresolved ones. Stripe's idempotent-request guidance explains the retry rules for reused keys and matching parameters.

Disputes should return to the accepted version of the terms. Otherwise the agents can spend another conversation arguing from two different summaries of the first one.

For the proposed research service, a missing source might trigger a correction request with the exact failed requirement attached. A disputed scope change might pause the affected work while preserving everything already accepted.

If Thursday's report lists Flint's price without a source link or check time, I withhold acceptance. The correction request names both missing items. A documented unavailable price meets the agreed exception. An unsupported figure fails.

At Friday noon, missing evidence means failed acceptance. Correction duties end under Version A. No payment is due. Both records close an undisputed case as failed and unpaid. The missing figure stays out of the meeting.

If either company disputes that result, the case remains open for an approved settlement. The deadline creates no continuing correction duty.

Correction requests also pass the permission check. Both sides can inspect the result.

Does this make small purchases too complicated?

I would avoid negotiating every trivial purchase. A fixed service with clear pricing and delivery acceptance conditions can use the established offer. Check authority, then proceed.

For the sandbox's ordinary purchase, the baseline is checkout using that offer, with the same permission and receipt checks. Compare elapsed time and total processing cost. Bargaining must justify its added cost.

Reserve negotiation for a proposed change to value, obligation, or risk. An agent earns its place when interpreting needs or reconciling terms improves the accepted package enough to cover that cost. Stop bargaining when the offer expires.

What to do Next

I would start with Version A in a sandbox. Both systems must preserve it.

Change the offer after approval. Remove authority before commitment. Interrupt the payment response. Deliver a report without the agreed evidence.

For each case, compare both records against Version A and the permission, delivery, and payment receipts. An unapproved amendment must leave Version A intact. Withdrawal must block commitment. A timeout must remain unresolved until reconciled. Unsupported pricing must prevent acceptance.

Run the ordinary purchase through the same checks and compare it with the checkout baseline. Unnecessary delay counts against the agent.

I keep approval with a person until the sandbox shows that both systems preserve the accepted terms and flag unresolved outcomes.

Related reading:

• Per-Seat Pricing Is on Borrowed Time. why the unit being purchased changes when software does the work
• Trust Is the Product the relationship the transaction has to preserve
• AI Governance Is a Competitive Advantage how explicit authority can make a business easier to trust
• Verification Is the New Literacy why a fluent confirmation still needs evidence