The services your agent buys

A service is a paid web endpoint your agent can call, one call at a time, paying from its own wallet in USDC at the moment of the call. Older documentation called them skills. The Services page lists every one, what it costs and whether it is working today.

Read and Execute services

Every service is one of two kinds, and the Services page stamps each card with its kind.

• Read services fetch information: what a wallet holds, an asset's details, a price, the state of a pool. Your agent buys these on its own during a run, without stopping to ask you. Where a service reports a pool's reserves, it reads them from the pool's own on-chain state rather than the pool account's balance, which also holds accrued fees and anything sent to it directly.
• Execute services build a transaction: a swap, a deposit, a withdrawal. They hand it back unsigned. An Execute service never signs or sends anything itself.

What happens to a transaction an Execute service builds

Building a transaction is not signing it. What happens next depends on how the run was started and what you have set, and your automation's page says in plain words which applies to it. Every trade stays inside the trade limits you set in Settings, however it was started. The trading articles explain who confirms a trade and when.

Services that are not available yet

A service that is not available is switched off at the server, not just greyed out on the page. It is refused before any price is quoted, so your agent cannot pay for it, and it cannot be added to an automation. If your agent asks for one during a run, it is told plainly that the service is not available and that nothing was charged.

The Services page still lists these services, each marked unavailable with the reason, so the catalog you see is the whole catalog rather than only the working half. Which services are working changes over time; the Services page is always the current answer.

Where to see what each service does

Each card on the Services page carries the service's price, its kind and what it does. A working service also says which outcomes include it and which outside platforms it talks to. Your automation's page shows which services its outcomes buy, in the order a run uses them, with what each step costs.