Start with a hosted connection, then add more only if needed.
Use AINIQ with NemoClaw when you want persistent voice, priorities, memory, and decision support without rebuilding your context from scratch.
What AINIQ does here
Keep context snapshots, saved memory, and structured guidance available in one place.
Keep one AINIQ account across SaaS use, OpenClaw, Claude, and NemoClaw sessions.
Start with the hosted path before investing in host-specific setup.
When to use AINIQ here
Use AINIQ here when NemoClaw should remember the user across sessions without asking for the same context again.
Use it when advice should follow the user’s values and priorities.
Use it when you want a simple hosted connection before adding anything more advanced.
Permissions requested
AINIQ connects through OAuth and only grants the scopes the user approves.
twin:read and memory:write remain separately scoped so setups can stay least-privilege.
Manual API keys remain the fallback, not the default integration path.
How data is handled
Identity, billing, and access controls stay in your AINIQ account.
NemoClaw only receives the information needed to help with the task.
The setup stays simple while the NemoClaw side is still evolving.
Billing and account model
NemoClaw-originated memory and guidance calls bill against the same AINIQ account.
AINIQ remains the home for billing and account access even when discovery starts inside NemoClaw.
Keep billing and access in one place even when discovery starts inside NemoClaw.