A budget for software
Giving software permission to pay raises a practical question: how much is it allowed to spend, with whom, and for how long? OneLink Pay makes those terms part of a signed mandate.
The mandate has per-charge, daily, and total limits, an expiry, and one approved merchant. The owner can revoke it. Requests outside the policy are rejected during preflight against the onchain contract.
Connecting consent to payment
Magic provides email and Google onboarding. Particle Universal Accounts handle the cross-chain payment path. The application connects those steps to a readable permission screen and a public receipt.
The verified demonstration includes a Base-to-Arbitrum funding flow. The research expense-card example buys two inputs and blocks an additional request above its per-charge limit.
What the demo shows
The research task is a deterministic workflow. It demonstrates payment and policy enforcement without claiming that an LLM independently reasons through the task. Recorded transactions and the replay page let someone inspect the result without connecting a wallet.
The app’s scope page separates the verified flows from the parts that remain examples or future work.

