Glossary

• Horizontal infrastructure: A general-purpose platform designed to support any kind of automation use case. Like Zapier or Ethereum, it doesn’t dictate what you build—it just gives you the tools.

• Vertical products: Opinionated, use-case-specific tools built on top of horizontal infrastructure. They’re optimized for a particular purpose (e.g. lending, notifications) and require zero setup from the user.

• Workflows: Simple automations that follow predefined logic—if X happens, do Y. Created visually via the no-code builder or programmatically via SDK.

• Agentic workflows: Flows where AI interprets less-structured inputs (like tweets or news) and decides whether a workflow should run.

• Ambient agents: Fully autonomous AI systems that monitor wallet context continuously and take proactive actions without predefined triggers.

• ERC4337: The most known standard for account abstraction on EVM. It enables smart contract wallets to behave like EOAs (Externally Owned Accounts) while supporting more complex features like batching, gas sponsorship, and session keys.

• Session keys: Keys that allow specific, limited interactions on behalf of a user’s smart wallet. That’s what we use to automate transactions.

• Function selector: A way to restrict which specific smart contract function a session key can call. For example, allowing only approve() on the USDC contract—blocking all other calls.

• Call policies: Rules that further restrict how a function is used—e.g., only allowing approve() if the spender is a specific protocol like AAVE, and the amount is below a certain threshold.

• Triggers: The event or condition that starts an automation—e.g., a wallet receives a token, a lending rate drops, or a specific X account tweets.

• Actions: The execution part of an automation—e.g., executing a trade, moving tokens or making an API call.

• Connection points: The data sources and protocols Otomato can read from or write to—e.g., AAVE, Compound, Uniswap, Hyperliquid, X, Coinmarketcap, ....