What your AI can do in Base Captain

Your AI, connected to Base Captain, finds an app, creates your base, lists and opens your bases, and works in them and changes them. It works as you: it sees what you see and changes only what you may change. What it reaches is what you chose when you allowed it: all your bases, or one base (Sign in and allow your AI). Ask it to:

• Find an app: list the apps a base starts from, such as Hair salon, with the add-ons that change each. If you continued without signing up, it can send what your business does, and Base Captain picks the app and the add-ons that fit, and makes a short name for your base from your words, as the homepage's box does (Make a temporary base). For a base of yours, list the modules it has and those you can add (Start from an app and add or remove modules).
• Create your base, if you allowed it to create bases, from an app and the add-ons you want with it, or with no app. It asks you for your base's name, then makes your base on the Free plan, with its sample data or empty (What the Free plan includes). Each time, it makes a new base, as Create your base does on the web. For a free base, your AI also gets the day the Free plan ends and, once the base is read-only, the day its data is deleted, so it can tell you. If you continued without signing up, it makes a temporary base, with the name it got from your words or the name you give it, else the app's name (A temporary base made from a chat).
• List your bases: every base where you have a role, with its address. An invitation you have not accepted yet is not among them.
• Open a base: it gives you a link that opens the base in your browser. It never asks for your password.
• Work in a base: name the base, or it asks you which. It reads, adds and changes items, runs buttons and workflows, and uses the views, chat and files of the base, under your role there.
• Change a base, if you build it: its tables, fields, views, automations and code. In a base, your AI has the same tools as the assistant (What an AI client can and cannot do in a base). What your role does not reach is refused.

Where the assistant in the base shows a card for you to apply, your AI does the change at once: read what it is about to do before you allow a tool. Its changes show under your name in the item's history, "via API", and a change to the base is a new version in Versions.

Limits and details

• Your AI cannot copy or delete a base: an owner does that in the base's Settings, General (Copy a base).
• Your AI cannot make or revoke API tokens, connect another AI, or change your password, two-factor sign-in or sessions.
• A base that keeps its data from the assistant and agents refuses its calls (When the base keeps its data from AI).
• If you lose your role in a base, your AI loses that base too; a connection to that base alone is removed.

These prompts try your AI with Base Captain: send them in a chat where Base Captain is on, one after the other. Put your own business in place of the hair salon.

• "I want to use basecaptain.com to manage appointments for my hair salon, which I also want to customize": your AI finds the Hair salon app, asks for your base's name, makes your base with its sample data, gives you the link to open it, and asks what to change.
• "Send an email to customers 3 hours before their appointment": your AI adds an automation to the base that mails each client before their appointment. A temporary base sends no mail until you keep it.
• "Which clients have no appointment booked this month?": your AI reads the clients and the appointments and answers in the chat. It changes nothing.

If you continued without signing up, your AI makes a temporary base: a real base, with its sample data (Make a temporary base with no sign-up). The clock of a temporary base made from a chat is the same as on the web:

• It is open for 24 hours from the time it is made, with the assistant as its only AI.
• Then it is closed for 24 hours. Nothing in it changes, and your AI's calls to it are refused, with the time left before it is deleted. You can still keep it.
• 24 hours after it closes, it is deleted for good, with all its data.

Your AI gets the time the base closes with every answer about it, so it can tell you.

Keep the temporary base

1. Ask your AI for the keep link and open it, or click Sign up to keep this base. on the base's banner.
2. Sign up, or sign in if you are a user already.
3. Check your base's name: the temporary base becomes your base, with all you put in it, and nothing moves (Keep a temporary base as your own).

Once you have signed in, your AI can keep the temporary base for you too: tell it your base's name, and it keeps the base on the Free plan. Your AI stays connected and from then on works as you, in all your bases.

Limits and details

• The link that opens a temporary base works once, for 10 minutes: ask your AI for a new one when you need it.
• You may make a limited number of temporary bases in 24 hours, and until you keep one it sends no mail, has no other users and does not export its data (What a temporary base does not do).

An AI client working in a base, with a token of all your bases or of that base alone, has the same tools as the assistant in the base. The client works as the person who made the token or connected it, under that person's role: with the salesperson's token it sees his orders and none of the manager's, and it changes only the fields he may change. A customer with an external role, as in the base's customer portal, gets what that role allows, and the base refuses the rest. The client is offered only the tools the person's role reaches.

What an AI client can do for everyone

• Items: list the base's tables and read a table's fields; list items, with filters, groups of them joined by or among them (Match any of several conditions (an or filter)), and read one; count and add them up, by a field or by a day, week, month or quarter of a date, such as last quarter's sales by customer; create, update and delete an item, or many at once, and hear the warnings that held (Warn about a value without stopping the save); sort a list by several fields and move an item to its place in a manual order (Drag items into the order you choose); ask which items a reference may take, such as the products a line of an order may have (Offer only the items that fit in a picker, and add one with + New); ask what an item's form would fill in, warn about and offer before it is saved, such as the price of a 12-piece line; read an item's history, read its comments and add one, mentioning users, and edit or delete a comment of your own. An item it creates gets its fields' defaults, as one made in the base does.
• Buttons and workflows: run an item's button, or one on many items; start or stop a workflow on an item, approve a step, send it back or pick its outcome, on one item or on many at once (Pick an outcome for many items). On many items, a button runs on those it applies to and names the others.
• Undo and restore: undo a change, list a list's recently deleted items and bring one back.
• Exports and imports: export a list and answer with the file's link; give the link to all of the base's data, with its Chat and its Files, for its admins; import a spreadsheet into a list, for anyone who may add its items.
• Views: list the saved views, and save or delete your own.
• Inbox and notifications: say what waits for you, list your open notifications and the open mail you may see, mark a notification or all of them done, and follow or stop following an item.
• Mail: for the users who see the base's Mail (Get and answer mail in a shared inbox), list and read its mails, mark one Done or Open, take one, give it to another user or give it back, and make an item from one. It never answers a mail: only a person does (Use Mail with an API token or an AI client).
• Chat: list the channels you may read with their unread messages, read a channel or a thread, send a message or a reply, and edit or delete your own (Use Chat with an API token or an AI client).
• Search: search the lists of the base you may see.
• Files: list the files of the Files page you see, by folder, tag or a word inside them, and make, change, move and delete files and folders. It does not read a file's picture or PDF: that uses the plan's AI, and only the assistant and the base's agents do it (Use Files with an API token or an AI client).
• Customer links: list the links an item's customers were sent, send a step's link again, and revoke one. The list starts with the item's lasting link, with its address, when its table has one (Give each item a lasting link: a check page).
• Your settings: change your theme, date format, time zone, notifications or name, or give your date format and time zone back to the base's. Your password, two-factor sign-in, sessions, email address, API tokens and calendar links it never changes.
• Base Captain itself: read a page of the site that answers a question about Base Captain, such as the Terms, the legal pages, the pricing page or the docs, with the tool read_base_captain_page. Called with no page, it lists them.
• Jobs and problems: see the base's background jobs (its imports, exports and queued agent runs) and how they went, and tell us of a fault of Base Captain itself.

What an AI client can do for the users who build the base

• read the base's tables, roles and their rules, settings, automations, workflows, forms, print templates, saved replies and agents, and the names of its secrets, never their values; and change the base itself, as the Builder does: its tables, automations, workflows, forms, print templates and saved replies;
• read the base's code and write it, as the assistant does: it tries a change of code on one item first, where nothing is saved or sent, and reads the code's last runs to say why one failed;
• import a Slack export into the base's channels;
• read the base's Versions and what each changed, or restore a version;
• erase a deleted item for good, with its history: an item that is not deleted is refused, delete it first;
• read what changed in the base, its History, and export it;
• run a scheduled automation now, or send its mails to you alone first (See a schedule’s mails before anyone gets them);
• list the held mail, and release or delete one (Release or delete held mail);
• read the agents' runs, each with everything it did;
• read what the base did, the numbers of the Statistics page (See what the base did: statistics).

What an AI client can do for the admins and the AI managers

For the admins, an AI client also can change the roles and their rules and the base's settings; list the users, invite one, change a user's role or remove one; and read the Storage page's storage (See your base's storage: the Storage page). For the admins and the AI managers, it can pause or resume agents and workflows, change the agents, skills and MCP servers, read whether an MCP server answers and which machines are paired, find a service's MCP server on the product's list and get its Connect link, and put a machine agent on a machine (Run agents on your own computer: machines). Nobody gives an agent a role with more than they have (Roles and their types: admin, staff and external).

An AI client acts without a card

Where the assistant in the base waits on a card you apply, such as before a delete, a change to many items or a change to the base, an AI client does it at once: it is the client that asks you before each call, as Claude Code does. Read what it is about to do before you allow it, and think twice before you allow a tool for good. A file it attaches, such as the spreadsheet of an import or a comment's file, is one it uploaded first with the same token.

An agent that works by itself and uses Base Captain's MCP server as one of its MCP servers is different: nobody is there to allow a call, so it gets only the tools an agent gets by itself in its own base (Let an agent work by itself from an automation or a workflow).

An AI client gets no tools of the base's MCP servers, such as your ticket system or Linear, whatever your role. The client does what a card would ask you at once, so it could act in another service with no person to read the card first. Use them through the assistant in the base, which asks you on a card (Work in your other services through MCP servers).

Save a file in the base

To keep a file in the base, such as a report it made or a page's picture it took, an AI client saves it in two steps:

1. It calls upload_file with the file's name, type and size, such as {"name": "report.csv", "type": "text/csv", "size": 18234}, and sends the file to the address that answers.
2. It calls save_file with the key it got, the file's name and one place: a files field of an item (table, item and field), a new comment on an item (table, item and comment, the comment's text) or a folder of Files (folder). It answers where the file went, such as "Saved "report.csv" to Attachments of ORD-00005 (orders)."

Your permissions decide, as for every call: a field you may not change or an item you may not see is refused, and so is a key another base gave.

Limits and details

• An AI client cannot open pages, set a list's filters or fill a form in your browser, and it does not look into the photos and PDFs attached to items.
• An AI client does not search the web or take a page's picture through your machines either: your AI client has its own way to the web.
• Its changes to items show under your name in the item's history, "via API"; a change to the base lands as a new version in Versions, as one made in Builder or Settings does.
• Revoke its token in Settings, API tokens, and the client is refused at its next call. A person removed from a base loses it for every token: their tokens of that base alone are deleted.

While Keep item data from the assistant and agents is on in Settings, General, Base Captain's MCP server refuses every call of every AI client in that base. What the switch stops, for AI clients and scripts too, is on one page: Keep your records away from AI.