Structured capabilities, agent-owned logic
Nilyo handles account connectivity and provider actions; Hermes decides when and why to use them according to your instructions. The same boundary applies to memory, scheduling and long-running plans.
Prefer events to blind polling when available
When a supported account event can reach the runtime, the agent can fetch the exact message or conversation through MCP instead of repeatedly opening a website just to check whether anything changed.
Use multiple accounts without merging their semantics
LinkedIn profiles, WhatsApp chats and email threads remain different resource types even when one agent reasons across them. Nilyo keeps those provider objects explicit so cross-channel context does not become an untraceable text blob.
“When a relevant reply arrives, fetch the full context and tell me why it matters.”
“Use my email history and the person’s LinkedIn profile to prepare a briefing.”
Common questions
Is Nilyo an automation builder?
No. It is the account capability layer for the agent.
Can Hermes use the same Nilyo MCP as other compatible agents?
Nilyo is designed around MCP-compatible agent clients; exact client setup depends on the runtime.
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.