Agents act.
You set the terms.
Turn an instruction into a precise spending policy. Choose the action, amount, receiving wallet and the limits that belong around it.
Open Create a Pact and enter a task such as “Send 25 USDG to my recipient” or “Swap 40 USDG for WETH.” The hosted Qwen model reads the action and amount. The workspace suggests an editable budget and action limit; you set the recipient and review the complete policy.
Prefer to enter it yourself? Choose Build manually. You can create, check, save and download a draft without connecting a wallet. Connect through Privy to use your own wallet as the recipient.
The live workspace prepares policies. On-chain funding and agent execution require a deployed PACT vault; saving a draft does not activate spending permission.
Create a PactMake the boundary explicit.
A policy contains one action: a USDG transfer or a USDG-to-WETH swap on Robinhood Chain, chain ID 4663.
| Rule | What you choose |
|---|---|
| Total budget | The overall USDG allowance. |
| Per-action limit | The most USDG a single action can spend, within that budget. |
| Recipient | The exact receiving wallet. |
| Access window | The intended duration after activation. Saving a draft does not start its timer. |
| Action count | The maximum number of permitted executions. |
| Swap floor | The minimum WETH per USDG you will accept. This is your limit, not a market quote. |
USDG inputs support six decimals. Review checks that the task amount fits the per-action limit, the limit fits the budget, and the recipient is a valid nonzero EVM address. It cannot establish who owns a recipient address.
Your rules, kept close.
Review rules creates a structured policy summary. Check an action amount to see whether it fits the draft's budget and per-action limit. This local policy check does not broadcast a transaction or simulate market execution.
Save draft keeps the latest policy in this browser. Open saved draft restores it. Download rules exports pact-policy.json with its action, amounts, recipient, access duration and other terms. The file is marked draft and contains no signing key, allowance or transaction receipt.
Editing a field clears the previous review so it must be reviewed again before saving or exporting.
From a policy to a permission.
The contract implementation is designed to accept an owner-approved USDG budget and record its agent, recipient, action limits and expiry. The owner signs the allowance and creation in their wallet. The model has no signing authority.
Its swap path uses a fixed KyberSwap router, exact action allowances and measured recipient output. Its policy checks reject an action that exceeds its limits. Revocation, expiry or completion return unused funds to the recorded owner. These are the contract's intended execution semantics; a downloaded draft is not an active contract permission.
Qwen2.5-0.5B-Instruct runs on PACT's server. Its structured response is checked against the action and single amount in the instruction. Unsupported assets, ambiguous amounts and model failure stop AI preparation. Manual entry remains available.
A model response is not approval.
Wallet connection uses Privy. A sign-in signature authenticates a wallet; it grants no token spending permission. The workspace does not request your private key or recovery phrase and sends no fund-moving transactions.
The published contract implementation has no operator withdrawal, administrator or upgrade mechanism. It has not received an independent security audit. Review the source and deployment information before approving on-chain permissions.
Instructions go to the hosted model; saved drafts remain in your browser. Read Privacy & data for details.
Look under the surface.
Inspect the vault implementation and interface.
Canonical USDG: 0x5fc5360D0400a0Fd4f2af552ADD042D716F1d168
Canonical WETH: 0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73
KyberSwap router: 0x6131B5fae19EA4f9D964eAc0408E4408b66337b5