Get early access

    Instinct

    We have not tuned for Instinct. It gets the standard server.

    Not open yet. Opens with early access.

    On this page

    Before you start

    • What Instinct publishes. Instinct (instinct.com, an invite-only personal AI agent) publishes no developer pages, no connector directory and no instructions for custom MCP connections. This page is the settings to try, not a promise that Instinct accepts them.
    • An invite to Instinct. Access is by waitlist or invite.
    • An API key. Create a dedicated key in the console, so you can revoke it without touching anything else. You need an account first.

    Set it up

    Instinct doesn't document the menu path.

    1. In Instinct, in the text interface or the workspace at app.instinct.com, look for an option to add an MCP connection.
    2. Server URL: https://api.theunderstanding.company/mcp.
    3. Transport: Streamable HTTP.
    4. Authentication: one header, Authorization: Bearer <your key>. Send a single opaque token. Do not add a second header.
    5. Enter the key only in Instinct's private credential field. Never paste it into the chat.

    Do not use OAuth for Instinct. Instinct's sign-in identity is not published, so there is nothing for our sign-in to recognize. Do not use the CLIENT_ID:API_KEY form another service documents for Instinct; our server does not accept it.

    What we tuned for this service

    We have not tuned for Instinct. It gets the standard server at https://api.theunderstanding.company/mcp: eleven read-only tools (including three health tools that take derived numbers and presence flags only), the abstain flag first in every result, and nothing worded for Instinct. There is no published description of how Instinct reads tools to tune against, and we did not guess.

    Check that it works

    Run these in order and stop at the first failure.

    1. Ask Instinct to list the tools in the Understanding connection. You should see check_restricted_merchant, classify_spend_type, match_receipt, pair_refund, check_return_window, route_support_message, score_signal_baseline, route_member_message, check_document_complete, ask_closed_question and get_usage.
    2. Ask: Is the merchant DRAFTKINGS with merchant category code 7995 a gambling merchant? The reply should show an answer, a probability and the abstain flag.
    3. Ask about LUCKY COINS LLC with code 5816. A result with "abstain":true should make Instinct say it is unsure.
    4. Look at usage in the console. The calls should appear with the source MCP.

    The tool result for step 2 is one JSON object. The numbers show the format. They are not measured results.

    JSON
    {"abstain":false,"answer":true,"probability":0.97,"reasons":["mcc_7995","rule_gambling_category","kind_sportsbook"],"decision":"restricted_merchant","type":"predicate"}

    Instinct acts on a person's behalf. Our tools only read and classify, but ask Instinct not to send anything or take any action with the result unless you ask it to.

    If it doesn't connect

    • There is no option to add an MCP connection. Instinct may not offer one to your account. We would rather you ask Instinct than guess.
    • The connection shows an error or needs sign-in. Check that the key is the whole usk_live_... value with Bearer in front, and that it has not been revoked. A 401 means the server refused the key.
    • Instinct sends the key but no tools appear. Instinct may need a different transport than the one we serve. We serve Streamable HTTP, and it is stateless.
    • Your data. What you send through Instinct is handled under Instinct's terms. Its policy says message content can be processed by third-party AI providers, and its terms allow training on some content unless you opt out. Send a merchant, an amount, a date and a category code only.
    • Use beyond personal use. Instinct's terms limit use to personal use. They do not clearly allow a bank to build on it.