Wallet authority

How the authority is bounded

The Base SpendPermissionManager permission identifies the principal account, spender, USDC token, allowance, period, start time, end time, salt, and extra data. Settlement refuses when no matching active permission exists or when the earned amount exceeds the remaining allowance.

The Wallet tab derives and shows the current allowance, period, and expiry from the loaded grant setup. These are current setup defaults, not permanent limits. Read the values shown in Settings, Wallet each time you create a permission.

The Spoolis verification fee is quoted before work and collected on settlement. Network or third-party wallet fees may still apply.

Set up a production wallet

Complete these steps in the Wallet tab under Settings. Moving to production is an account status change, not a separate integration. Your account must be production-enabled before the production settlement path can be used.

1. Register a principal

Enter the public smart account address that will own the permission. The product registers it for your account through POST /api/account/principal. It must match the configured production network.

2. Grant bounded authority

Select Load grant setup. The Wallet tab shows the configured network, spender, SpendPermissionManager, USDC token, allowance, period, and expiry, plus a guided CDP snippet. Run that snippet in your own environment with your own credentials. Do not send credentials or private keys to Spoolis.

3. Verify status

Select Check permission status. The product calls GET /api/account/spend-permission and shows matching permissions, the amount spent in the current period when available, expiry, and revocation status. A production commit still requires the account enablement status.

Two independent ways authority ends

Expiry

Every permission has an onchain end time. Once that time passes, the authority cannot be used. Expiry is an automatic backstop: authority cannot persist indefinitely, including if Spoolis is unavailable.

Revocation

In Settings, Wallet, select Revoke. The product submits POST /api/account/spend-permission/revoke, and the configured spender submits the onchain spender-side revocation.

You can also revoke independently from the principal account by calling revoke on the Base SpendPermissionManager contract at 0xf85210B21cC50302F477BA56686d2019dC9b67Ad with the complete permission struct. This principal-side path works even if spoolis.com is offline. Use the same account and permission values that created the grant. Revocation ends future authority. It does not reverse a transaction already submitted or completed.

expiry: onchain end time passes -> authority cannot be used
service revoke: POST /api/account/spend-permission/revoke -> spender-side onchain revoke
independent revoke: principal calls SpendPermissionManager.revoke with the complete permission struct

Account routes

• POST /api/account/principal registers or replaces the signed-in account's principal.
• GET /api/account/spend-permission reads the signed-in account's stored and onchain permission status.
• POST /api/account/spend-permission/revoke requests spender-side revocation for a permission owned by the signed-in account.

See API troubleshooting for production wallet refusal messages and remediation.