Sangria

Commit ONE user-approved match from a prior discover, charging the user's Sangria credit balance (in the account's currency). The Amazon marketplace follows the account's country. Never buy until the user has approved a specific match and its tax-inclusive total. Before calling this tool, state that match's full cost from the discover response — the pre-tax `price_microunits`, the `estimated_tax_microunits`, and the `estimated_total_microunits` their credits will be charged — and get explicit approval of that total. Do this every time, even if those numbers were already shown when the matches were listed; this is the user's last chance to decline, and the tool call itself shows them no prices. Idempotent per (discovery_id, sku). Read `status`: confirmed / failed / running. On a confirmed order the response returns the charge breakdown — `price_microunits` (pre-tax), `tax_microunits`, and `total_microunits` (the tax-inclusive amount charged); tell the user the `total`.

buy

Confirm the signed-in user's Sangria access works (probes balance). Returns {authenticated, balance_microunits} or {authenticated:false, error}.

auth_status

Return the user's available Sangria credit balance (balance_microunits; 1 unit = 1,000,000 microunits) and the account currency (null until the user sets their country).

balance

Find physical products to buy and mint a short-lived Sangria discovery_id. Two ways to call it: (1) intent search — pass `intent` (a short product description) + `reasoning` (why it fits), optionally `min_price`/`max_price` (in your account currency), to get up to 5 matches; or (2) URL lookup — pass `url` (a direct Amazon product-page link) to quote one specific product. The Amazon marketplace follows your account's country, and a pasted URL must be for that same marketplace. Provide intent+reasoning OR url, not both. Do not include card data, authorization codes, credentials, government IDs, health/biometric data, shipping addresses, phone numbers, or other sensitive personal data. Each match reports `price_microunits` (pre-tax), `estimated_tax_microunits`, and `estimated_total_microunits` (the tax-inclusive total the user will be charged at buy) — when you show a match's cost to the user, use `estimated_total_microunits`, NOT the pre-tax `price_microunits`, and show the pre-tax price and estimated tax that make up that total so the user sees what tax adds. When `estimated_tax_microunits` is 0 the displayed price already includes tax, so show the total alone. No money moves. Always discover before buying.

discover

Return recent Sangria orders for the current credential, newest first. Each order includes id, placed_at, item, sku, product_url, status, total_microunits, total, currency, batch_id (non-null when the order was part of one multi-item buy), and the fulfillment facts estimated_delivery_date, carrier and tracking_id. Use this when the user asks about past orders, order status, when something will arrive, or for a tracking number. Any of the three fulfillment fields can be null, which means not known yet — say so plainly and never guess a date or invent a tracking number. All three come back as stored on every status, so deciding when to present them is yours. Give estimated_delivery_date only while the order still has an arrival ahead of it: confirmed, placed and shipped — on delivered say it arrived rather than repeating an estimate that may never have matched, and on cancelled or refunded it is a promise the order is no longer making. Keep reporting carrier and tracking_id on delivered, cancelled and refunded too, since a tracking number records a real package and is what the user needs to follow a delivered parcel or return one from a cancelled order; only running and failed have no package to name.

orders