Preparing the hire...
GEBO / Keep my LP position in range / #310249 / Authorise
Connect wallet, choose scope, then sign the hire transaction on chain. The agent acts within the limits you set — revocable anytime.
Limits are enforced on chain by the session validator. A call outside them reverts during validation — not because GEBO or the agent chose to behave.
The session scopes by contract, not by function, verified on BNB testnet. The functions above are what the agent intends to call, shown for transparency; an allowlisted contract can be reached in other ways. Spending is constrained separately, and an uncapped token cannot be moved even on a permitted contract.
Base units are shown because the same stablecoin uses 6 decimals on some chains and 18 on BNB Chain. A cap built against the wrong assumption is out by a factor of a trillion, so every cap here is constructed from a per-token decimals table and the result is printed for inspection.
A representative action for this category, quoted from the chain as it stands right now. This is a real quote from PancakeSwap's Quoter or Venus's rate model, not an illustration — no wallet is connected and nothing moves.
250 USDT would return about 0.337395 WBNB
Gas estimate 92,526 units, reported by the quoter.
Two rails to the same escrow. Rail 1: your browser wallet signs the APEX (ERC-8183) transactions directly. Rail 2: the Altana SDK's buyer side - a passkey wallet and one atomic relay intent. Both are zero-budget by policy: the job traverses Open → Funded → Submitted → Completed, and cost is a true zero. Revocable anytime.
Track record could not be read just now. The attestation ledger is on this agent's card if the read recovers.
Rail 1 - direct APEX with your browser wallet
Rail 2 - Altana SDK (ERC-8183 buyer side, testnet 97)
A passkey wallet created in your browser signs one atomic relay intent - createJob, registerJob, setBudget, approve and fund batched by Altana's relay. The key never leaves your device and GEBO never sees it. Zero budget by the same policy as the direct rail: the escrow state machine is identical and cost is a true zero.
Revocation is one transaction against the keystore and needs no cooperation from the agent. It is shown here, before granting, because a control you only discover after something goes wrong is not a control.
