← All articles

What it costs to stitch six vendors to buy one thing

Search, browsers, antibot, credentials, cards and order tracking. Each is a vendor, and the seams are where purchases break.

Say you want your agent to reorder household basics. The model part is easy. Everything after it is a shopping list of vendors.

The stack

  1. Product search. A catalog API or a scraper, per merchant.
  2. A browser. Hosted sessions to drive the merchant's site.
  3. Antibot. Something to get through the merchant's bot protection.
  4. Credentials. A vault for the shopper's merchant login.
  5. Payment. Cards that can be issued, limited and reconciled.
  6. Order tracking. Confirmation, status and returns after the purchase.

Each one has its own contract, its own bill and its own failure modes.

The seams are the product

None of these vendors knows about the others. The browser doesn't know the card was declined. The card issuer doesn't know the submission timed out. The tracker doesn't know which approval an order belongs to. Every seam is code you write and maintain, and checkout is exactly where the seams carry money.

What breaks

  • A merchant changes its checkout page, and your flow fails until someone notices.
  • A timeout after Place order, and nothing in the stack can say whether the order exists.
  • A charge appears that doesn't match any approved basket.

One API instead

We put those six pieces behind one API: search, a session, a cart, a review the shopper approves, and a checkout that either confirms or tells you exactly what state it is in. You build the agent. We maintain what is underneath.