Architecture
The agent's eyes (mcp) and hands (m-aws), and how they work together.
Architecture
KB pipeline auto-generates docs for both MCPs into docs.maroo.io. Generated content for `@maroo-chain/m-aws` lives at /apis/maws/.
The kit ships two MCP servers — Maroo MCP (read) and m-aws (write). They run in independent processes with different security boundaries. But they share types, ABIs, and chain config via @maroo-chain/kb-core, so an agentId from m-aws works against PCL queries on Maroo MCP without translation.
Maroo is a regulated chain. PCL (Programmable Compliance Layer) and KYA (Know Your Agent) aren't app-layer add-ons — they're protocol-level. When your agent calls policy.preflight or transfer.send, the chain itself rejects non-compliant transactions before they even mempool. Your agent fails fast and clean, not on-chain.
Gas paid in OKRW — a KRW-pegged stablecoin. No volatile fee token, no separate accounting unit. Your agent's operating costs are predictable in fiat. PAYMASTER mode lets your platform sponsor gas if you don't want agents holding OKRW for fees.
The deep API reference for both MCPs lives at docs.maroo.io and is auto-generated by the maroo-knowledge-base pipeline on every push to the source repos. This site (agent.maroo.io) handles the *kit-level* story — install, why, how, what to call when. The long-tail reference (every tool, every error code, every example) updates itself.
Ready? One install away.
npm i -g @maroo-chain/agent-wallet-kit