Your project and API key
A project groups developer resources and credentials. Its test and live environments are separate. A scoped API key identifies your server and limits which API operations it may request. Store the key on your server, never in browser code or a public repository. An API key cannot create an owner’s mandate, widen its limits, sign for the owner, or move funds by itself. The currentwhoami endpoint lets you check the key’s project, environment, and scopes.
The owner’s account and mandate
GOL is designed to work with a user-provided compatible account. GOL does not create an account for the owner or hold the owner’s private key. A mandate is an owner-approved envelope of authority for a named agent. The intended bounded mode restricts actions through explicit rules; a separate full-control mode requires explicit owner approval and still reserves ownership and authority administration to the owner. For an agent action that affects value, the security-critical rules must be enforced on-chain as part of that action. A platform check can improve the experience, but it is not the final authority boundary. The owner must be able to pause or revoke future agent actions without the agent’s cooperation.How a payment runs
- The owner installs the GOL core on their existing account, or delegates their EOA to the reviewed account code under EIP-7702, and signs one approval in their own wallet: the agent, allowed recipients, USDC caps, gas caps, expiry, and the relayer allowed to send actions.
- Your server asks the API to prepare an action. Your agent signs it, including the most network gas it accepts for the action, and your server submits it with an idempotency key.
- The approved relayer sends the action and fronts the gas. It is GOL’s relayer by default, or your own when the owner approved a developer-operated relayer. The contract checks the owner’s rules as part of the same transaction, transfers or refuses, and pays the relayer back from the account in that transaction, within the owner’s caps.
- GOL can report provisional
includedafter checking the canonical receipt and expected GOL effect. It verifies the receipt again at the selected Basesafehead before settling costs, then continues observing throughfinalized. The webhook and receipt reads use one Alchemy RPC operator. - An agent can delegate a narrower child mandate when the owner allowed it; every action in the tree is billed to the root’s gas policy.
- The owner can pause, resume, or revoke any mandate at any time without you or GOL.