AINIQ agent integrations

    One private context layer for every assistant.

    AINIQ lets ChatGPT, Claude, OpenClaw, Slack, Telegram, Generic MCP clients, and other agents request the right scoped context without copying your whole profile everywhere.

    Open guided setupReview privacy model
    Every assistant gets a scoped context passport, not your whole account.
    Hosted OAuth, pairing codes, and manual access keys stay under one AINIQ account.
    You can revoke access centrally while keeping the same private profile layer.

    Integration options

    Choose the surface first. Keep the context in AINIQ.

    These are connection paths, not separate products. The private context layer, billing, revocation, and permission boundaries stay with AINIQ.

    ChatGPT

    Personal chat

    Available

    Bring AINIQ context into ChatGPT so the assistant starts with your voice, priorities, and decision rules.

    Personal answers that stop starting from a blank prompt.

    Voice and toneDecision prioritiesMemory when approved
    Connect ChatGPT

    Claude

    Remote MCP

    Available

    Use AINIQ as a persistent personalization layer for Claude-style clients that support hosted setup.

    Workflows that need continuity, constraints, and remembered preferences.

    Twin summaryGuidance contextOptional memory write
    Connect Claude

    OpenClaw

    Local bridge

    Guided setup

    Keep the existing OpenClaw bridge path for local agent workflows, pairing codes, and quick CLI setup.

    OpenClaw, local scripts, and bridge clients that need a light setup.

    Pairing codeRemote MCP endpointBridge status helper
    Connect OpenClaw

    Generic MCP

    Any compatible client

    Available

    Point a compatible MCP client at AINIQ and request only the context scopes that client needs.

    Custom assistants, local tools, and agent clients that speak MCP.

    Protected resource metadataOAuth or pairingRevocable access
    Open MCP setup

    Slack and Telegram

    Team and chat surfaces

    Integration settings

    Invite AINIQ into messaging surfaces when a thread should receive scoped profile context instead of a generic bot reply.

    Quick asks, shared threads, reminders, and context-aware team prompts.

    Selected profile slicesThread contextBot-level permissions
    See messaging setup

    Agent Access keys

    Fallback path

    Advanced

    Use manual access only when a client cannot complete hosted OAuth or pairing, while keeping revocation in AINIQ.

    Developer workflows, private prototypes, and controlled fallback clients.

    API keyAccount billingRevocation log
    Manage access

    Permission model

    Start with hosted OAuth when the client supports it.

    Use short-lived pairing for OpenClaw, local scripts, and bridge clients.

    Use manual Agent Access keys only for controlled fallback workflows.