Where it plugs in

    The Understanding API is one service with three doors: a REST endpoint, a remote MCP server, and function definitions for your own agent. This page lists where each door fits, the address to use, and how you sign in. Each service has its own page with the exact steps.

    Not open yet. Opens with early access.

    On this page

    Pick your service

    You are using Address Sign in with Page
    You are usingAddressSign in withPage
    A banking product, a card program or a back-office toolPOST https://api.theunderstanding.company/v1/understand, and /v1/understand/batchAn API keyBanking apps
    ChatGPThttps://api.theunderstanding.company/mcp/chatgptSign in (OAuth)ChatGPT
    Claude Desktop, claude.ai or Claude Codehttps://api.theunderstanding.company/mcp/claudeSign in. Claude Code can also use a key.Claude
    Grok Bothttps://api.theunderstanding.company/mcp/cursorSign in when the app asks, or a key if it offers a headerGrok Bot
    Grok Build and the Grok chat apphttps://api.theunderstanding.company/mcp/grokA key in a header (Grok Build). The sign-in Grok shows (Grok chat).Grok Bot
    Meta's Muse, Muse Code, Meta Model APIhttps://api.theunderstanding.company/mcp/muse, or function definitionsA keyMuse
    Instincthttps://api.theunderstanding.company/mcpA key (settings to try)Instinct
    Cursor and VS Codehttps://api.theunderstanding.company/mcp/cursor for Cursor, https://api.theunderstanding.company/mcp for VS CodeA key in a header, or sign inCursor and VS Code
    Your own agent on OpenAI's APIhttps://api.theunderstanding.company/mcp/chatgpt, or GET /v1/tools?format=openaiA keyOpenAI API
    Your own agent on Anthropic's APIhttps://api.theunderstanding.company/mcp/claude, or GET /v1/tools?format=anthropicA keyAnthropic API
    Your own agent on xAI's APIhttps://api.theunderstanding.company/mcp/grok, or GET /v1/tools?format=xaiA keyxAI API

    Anything else that speaks MCP uses https://api.theunderstanding.company/mcp and a key. See Connect via MCP.

    What is the same everywhere

    • The questions. Is this merchant a restricted one, is this spending essential or discretionary, which charge does this receipt belong to, which transaction is the refund for this purchase, and your own yes, pick-one or scored question. Also: can this purchase still be returned, which support queue fits a message, and three health questions that take derived numbers only. The eleven tools are 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. The three health tools are offered at the standard, Claude and Cursor addresses and not at the ChatGPT, Grok or Muse ones.
    • The answer. A closed answer, the model's probability, reason codes and an abstain flag. When abstain is true, a person decides. The probability is not calibrated.
    • Read-only. No tool on your key moves money or changes anything. Each is marked read-only and idempotent. (Card controls exist only for our own keys: Cards and balances.)
    • The price and the limits. A call costs the same through any door, and counts toward the same limit of 60 requests a minute per key. See Pricing and Rate limits.
    • The input checks. A request that holds a full card number, a Social Security number or an account number with its routing number is refused with a 400 before it reaches the model.

    What differs

    Each assistant reads tool descriptions and results differently, so the MCP server has a tuned address for each: wording, the shape of the result, and which tools are offered. A tuned address never changes what a tool does, what it costs or who can call it. Instinct gets the standard server, because it publishes nothing to tune against. The ChatGPT, Grok and Muse addresses offer the banking tools only: those services have their own rules about health data. The table is on Connect via MCP.

    Not sure which door?

    If you are building a product, start with Banking apps and the Quickstart. If you want an assistant you already use to answer questions about your own statements, start with its page above. If you build agents on a model API, use the page for that API.