More endpoints

    AI assistants (MCP and GPT)

    Connect ChatGPT, Claude, Gemini, or Muse to HelloLedger with an assistant key.

    Connect an AI assistant

    Every assistant uses the same AI assistant key: send Authorization: Bearer <secret>. Company access and permissions come from the key.

    HelloLedger does not run the AI model. Model usage is billed to your own Muse, ChatGPT, Claude, or Gemini plan; HelloLedger only answers the API calls, within the same per-key limits.

    Claude and Gemini connect over MCP at https://api.helloledger.ai/mcp. ChatGPT uses a Custom GPT Action. Muse uses the REST API directly.

    Not supported yet: claude.ai web and mobile custom connectors (they accept only a URL plus OAuth, not an API key header).

    Not supported yet: ChatGPT MCP connectors in developer mode (same reason). Use a Custom GPT instead.

    Not supported yet: The gemini.google.com web app (it cannot connect custom data sources). Use Gemini CLI instead.

    Muse

    Paste the Bearer secret into Muse's HelloLedger connect screen.

    Step 1: In Muse, open the HelloLedger connection.

    Step 2: Base URL: https://api.helloledger.ai/v1

    Step 3: Auth: Bearer token. Paste the secret (starts with hl_live_).

    Base URL
    https://api.helloledger.ai/v1
    Bearer secret
    YOUR_API_SECRET

    ChatGPT

    Build a Custom GPT with a HelloLedger Action. Requires ChatGPT Plus, Team, or Enterprise.

    Step 1: In ChatGPT, open Explore GPTs → Create → Configure → Create new action.

    Step 2: Choose Import from URL and paste https://api.helloledger.ai/v1/openapi.json?profile=gpt

    Step 3: Authentication: API Key → Auth Type Bearer → paste the secret.

    Step 4: Instructions: paste the JSON from https://api.helloledger.ai/v1/guide so the GPT knows which action answers which question.

    Step 5: Share the GPT as Only me or within your workspace. Anyone who uses it reads the companies on this key.

    Action schema URL
    https://api.helloledger.ai/v1/openapi.json?profile=gpt
    API key (Bearer)
    YOUR_API_SECRET

    Claude

    Add HelloLedger as an MCP server in Claude Desktop or Claude Code.

    Step 1: Claude Desktop: Settings → Developer → Edit Config, add the block below to claude_desktop_config.json, then restart Claude. Requires Node.js.

    Step 2: Claude Code: run the command below in a terminal.

    Step 3: Ask Claude something like “Does the balance sheet balance for my company?”

    claude.ai on the web and mobile cannot use an API key yet. Use Claude Desktop or Claude Code.

    Claude Desktop (claude_desktop_config.json)
    {
      "mcpServers": {
        "helloledger": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.helloledger.ai/mcp",
            "--header",
            "Authorization:${HL_AUTH}"
          ],
          "env": {
            "HL_AUTH": "Bearer YOUR_API_SECRET"
          }
        }
      }
    }
    Claude Code
    claude mcp add --transport http helloledger https://api.helloledger.ai/mcp \
      --header "Authorization: Bearer YOUR_API_SECRET"

    Gemini

    Add HelloLedger as an MCP server in Gemini CLI.

    Step 1: Install Gemini CLI, then open ~/.gemini/settings.json.

    Step 2: Add the block below and restart Gemini CLI. Run /mcp to confirm HelloLedger is connected.

    The gemini.google.com web app cannot connect custom data sources.

    Gemini CLI (~/.gemini/settings.json)
    {
      "mcpServers": {
        "helloledger": {
          "httpUrl": "https://api.helloledger.ai/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_API_SECRET"
          }
        }
      }
    }

    OpenAPI and MCP

    Machine-readable contract: https://api.helloledger.ai/v1/openapi.json

    ChatGPT Custom GPT Actions: https://api.helloledger.ai/v1/openapi.json?profile=gpt (30 operations, the GPT Action limit).

    MCP server for Claude and Gemini CLI: https://api.helloledger.ai/mcp (Streamable HTTP, POST only, same Bearer key). Tools match the Assistant API routes; developer write routes are not exposed to assistants.