Skip to main content
Every purchase runs the same loop. The agent finds the item, a quote locks the price, and a checkout executes the payment after the user approves it on a Reap-hosted page.

The purchase path

Inside the purchase loop

The agent finds the item

Search products takes the user’s request and returns matching products. Get product details returns the option axes. When a product has options, Resolve variant turns the selected option ids into the purchasable variant id that a quote accepts.

A quote locks the price

Create quote opens the merchant checkout for the chosen variants and returns the itemized breakdown: subtotal, shipping options, tax, and the final amount. Get quote retrieves that quote later. Select shipping option re-prices the quote for a different delivery choice. Quotes expire within minutes; the expiresAt field states the deadline.

A checkout executes the payment

Create checkout opens the payment for the quote and returns a redirect link. Your application sends the user there. The user reviews the order, provides or selects a card, and approves the payment. Reap then completes the merchant checkout.

The agent confirms the order

Get checkout reports the lifecycle status. A completed checkout carries the merchant order reference and the final charged amount, and the agent confirms the order back to the user.
Reap does not send webhook events for agentic resources. Poll Get checkout to track a payment. Webhook events for the agentic lifecycle are on the roadmap.
This capability currently supports Reap Card and Visa cards. Support for additional card types and networks may be introduced in the future.

On the roadmap

The loop above asks the user for a card at every purchase. The planned setup flow removes that step:
  • Reap registers the agent execution identity with the relevant agent registries, so supported merchants can verify checkout traffic through a signed identity instead of treating it as bot traffic
  • A one-time enrollment vaults the user’s card and pays every later purchase with single-use credentials
  • A passkey-approved mandate caps what the agent can spend, so a purchase inside the cap needs no further interaction
  • Webhook events report enrollment, mandate, and checkout transitions without polling

Next steps

Set up for purchases

What your project and your customers need before the first purchase

Make a one-time purchase

The full request flow from product search to the completed order