Connect Claude, ChatGPT or Gemini
Add BillingMart to an AI assistant, sign in, choose what it may see and do, and know what to check on the consent screen before you allow it.
You connect an assistant by adding BillingMart's address to it, signing in on a BillingMart page, and choosing what the assistant may do. You sign in on our page, not inside the assistant. It gets only the access you tick, and you can narrow or remove it later.
Before you start: We test the BillingMart side of this on every change. The menus inside Claude, ChatGPT and Gemini belong to those products and change without notice, and we have not walked each one through on a fresh account. Treat the steps inside each assistant as a guide, not a promise.
What you need
- To see the AI agent and Connections pages, be an owner or an admin. A connection never gets more than its person's role allows, so a viewer's connection can only read.
Find the address
- In BillingMart, open AI agent in the sidebar.
- Press Copy address. It is
https://api.billingmart.com/mcp. The tabs Claude, ChatGPT and Another assistant show short steps.
BillingMart speaks Streamable HTTP only.
Add it in your assistant
- Claude: Settings, then Connectors, then Add custom connector. Paste the address.
- ChatGPT: Settings, then Connectors. Turn on developer mode if it asks, create a connector and paste the address.
- Another assistant: any that can add a remote Streamable HTTP connector can use the same address.
- Gemini for organizations: your Gemini administrator adds the connector with a client ID and secret you create first. In Connections, under Registered apps, press Register an app. Name it and keep the redirect address that is filled in. Copy the ID and secret at once: the secret is shown once. A registered app connects only to the workspace that registered it. Registering needs a recent sign-in and the same plan feature as API keys. We have not run this against a Gemini tenant, and we make no claim about the consumer Gemini app.
What the consent screen shows
A BillingMart page opens, headed Connect and the assistant's name.
- Check the badge and address. The page shows where it will send you back to. Verified app means a known Claude, ChatGPT or Google Gemini address. Registered by your business means an app you registered. Local app runs on your own computer. Connect an Unverified app only if you started it.
- Account. Sign in with Google or email and password, or create an account.
- Verify. Shown only when needed: confirm your email, or enter or set up your second sign-in step. A link lets you connect with read-only access instead.
- Workspace. Pick one, unless you have only one. If you have none, you can create one on this page.
- Permissions. Under This app will be able to, access is grouped by area, such as Clients or Payments, each row in plain words. Everything the assistant asked for is ticked, except seeing client email addresses, phone numbers and addresses, which is off unless you tick it. Untick what you do not want. A greyed row is not available to your role.
- How it works. Choose Ask (the default) or Plan. Auto is not offered here. See Modes and rules for connected assistants.
- Press Allow, or Deny to share nothing. The page then says Connected.
Read-only access needs no extra checks. Anything that lets the assistant change data needs a recent sign-in, a verified email and your second sign-in step where it applies. The page says which is missing.
After you connect
Open Connections in the sidebar. Connected apps shows each connection's mode, what it can do and whether customer contact details are shared. Edit access lets you untick things or change the mode. Revoke ends it at once. The sign-in page points to Settings, then Connected apps, but the list is on the Connections page.
What a connected assistant sends to a customer waits for a person to approve it, unless the owner set a capped rule. Approve in Approvals, or on your phone: see Approve requests on your phone. For sends to unconfirmed addresses, see Verified contacts.
Related articles
- Modes and rules for connected assistantsWhat Ask, Plan and Auto mean for a connected assistant, who can change them, what the owner's capped rules can cover, and what always needs a person.
- API keys and the REST APICreate an API key for your own software, choose what it may do, understand test and live keys, and handle retries and rate limits when you call the REST API.
- Verified contacts and why a send is blockedWhat a verified email or phone means, the three ways a contact becomes verified, what an unverified contact can and cannot receive, and why a send is held back.
- Approve requests on your phoneHow an Agent or assistant request reaches your phone, what the app shows, what it asks you to confirm, and which links open the app.