DEV Community

Discussion on: Selling eSIMs to AI agents: the seller's side, tried on a laptop in 32 seconds

 
whiteknightonhorse profile image
whiteknightonhorse •

The ARGUS rule is the part I'd copy. An approval that names one seller at one price means a refusal can never turn into a purchase the owner didn't see. And cheaper_elsewhere hands the owner the reason to say yes again.

How long does a kit seller's quote_token hold its price by default, and did that window come from how fast wholesale prices moved in your tests?

Thread Thread
 
alexar76 profile image
Alex •

Ten minutes: QUOTE_TTL_SECONDS=600. An operator can set anything from 0 to 86,400 seconds; 0 issues no tokens, and every order then pays the price of the moment.

It didn’t come from price data. We picked ten minutes on 17 November, when we added the tokens after your first question, and nothing we’ve measured backs it. The tests move the wholesale price inside a stub, and our reference node runs in demo mode: it reads eSIM Access’s live catalogue but sells nothing and keeps only its latest copy, so we have no record of how often or how far wholesale prices move.

What limits the risk is the rest of the design, not the number:

The node reads the wholesale catalogue again only when its copy is 15 minutes old, or at once after the wholesaler refuses an order. Its own view of a price can already be older than the quote window.
The kit never honours a quote below the current wholesale cost (quote_below_cost), so a rise inside the window can eat the seller’s margin but never makes it sell below cost.
If the wholesaler refuses the order at its new price, nothing is charged: the node settles only after the eSIM exists.

How long does your quoted price hold, and did you set it from your own price history?