Skip to main content
Haggles documents its economic, regulatory, and technical assumptions explicitly (SPEC.md §§ 1.4, 2.2, 13.2, 17.1).

Core Architectural Assumptions (SPEC.md § 2.2)

Assumption A1 (Micro-payment Economics): Charging PayPal Orders directly on every $0.005 or $0.02 API call is impossible due to fixed per-transaction fees and human checkout latency. Haggles solves this by separating funding (PayPal Orders v2 into a prepaid wallet), per-call settlement (sub-cent double-entry ledger postings), and disbursement (PayPal Payouts v1 to sellers).

Regulatory & Operational Boundaries (SPEC.md § 17.1)

Regulatory Scope (Risk R3): Holding prepaid balances and paying out third-party sellers in live production can implicate money-transmission or stored-value licensing depending on jurisdiction. This hackathon build runs strictly on PayPal Sandbox (PAYPAL_MODE=sandbox or mock) with hard safety caps ($200.00 max top-up, $500.00 max wallet balance, $5.00 max per call). Setting PAYPAL_MODE=live is blocked at startup unless explicitly unlocked after legal review.

Explicit Non-Goals in v1 (SPEC.md § 1.4)

  • No cryptocurrency, blockchain, or custom token/coin: All prices, balances, and payouts are in real USD settled on PayPal rails.
  • No dynamic haggling or multi-round price negotiation in v1: Each 402 challenge states a fixed USD price for that request.
  • No streaming per-token billing in v1: Prices are per HTTP request.
  • No public marketplace or discovery directory in v1: Agents call seller URLs they are configured with or discover via tool catalogues.
  • No multi-currency support in v1: USD only (1 USD = 1,000,000 micro-dollars).