AINIQ for NemoClaw

    Start remote-first, then add host glue only if needed.

    Use AINIQ as NemoClaw’s context layer when you want persistent voice, memory, and values without rebuilding the user model from scratch.

    Recommended: Hosted sign-in
    Same account, billing, and revocation

    1. Sign in

    Sign in first so the connection stays tied to your AINIQ account and can be managed later from one place.

    2. Hosted sign-in

    Recommended path: hosted sign-in.

    3. Use with NemoClaw

    Pairing is the lighter fallback for clients without the full hosted flow.

    Why connect

    Remote-first setup keeps the path simple while the host side is still evolving.
    Use the same AINIQ account across SaaS use and host integrations.
    Keep pairing and API keys available only as fallbacks.

    Channel guide

    Recommended path: hosted sign-in.

    Pairing is the lighter fallback for clients without the full hosted flow.

    Manual keys are the last resort path.

    Sign in to connect

    Your setup state will resume after login

    This connect URL preserves the channel, recommendation trigger, and campaign context. After sign-in, you will land back on the same guided setup page instead of a generic settings dead end.