How PortMula works
PortMula gives you one agent with its own Algorand wallet. You give it jobs, called automations, and when one runs your agent pays for the information it needs one small payment at a time, and can build the trades you set up.
You don't need to know anything about crypto. Sign in with Google: there's no browser extension to install and nothing to configure. If you already use Algorand, sign in with Pera instead.
What your agent is, and who holds its wallet's key
You get one agent per account. When you make it you only give it a name; what it does is chosen on each automation. One agent means one wallet to fund and one balance to watch. In connected mode its trades come from your Pera wallet, so that balance matters too.
Its wallet is a provisioned agent wallet. PortMula creates it and holds its key, encrypted, so your agent can act when you're not there. That is more custodial than a permission you could revoke, not less. You can export its recovery phrase or withdraw everything at any time, on any plan. A wallet you connect yourself, such as Pera, is a different kind: PortMula holds no key for it and never signs with it.
What a service is
A service, which the old docs called a skill, is a paid web endpoint your agent can call. Read services fetch information, and your agent buys them on its own during a run. Execute services build a transaction, such as a swap or a deposit. A service never signs or sends anything itself.
Payment uses x402, an open protocol for paying per request. Each service's price is on the Services page. A call is paid only once the service has answered successfully, so a failed one costs nothing.
What an automation is
An automation is one job for your agent. You decide what it may do by choosing an outcome, such as Watch and report or Swap, and you set the values it uses, such as an amount. The outcomes on offer, and whether each is available yet, show when you make one. What an outcome is goes further.
An automation runs when you press Run now, or on a schedule if you give it one; its page shows whether the schedule is running and when it runs next. All your automations share your agent's one wallet and one history. What limits a trade is in What bounds your agent.
What a run is
A run is one cycle of your agent's work: it reads what it needs, decides, buys the services it chose, and reports back. Every run leaves a record on the Runs page: what it bought, what each call cost, and each transaction. See Your first run.