What an agent on AI3 plugs in.

Connected once per agent, for every agent: bookings any agent makes appear in an AI3 calendar inside Google, and when your own Google calendar is busy no agent offers that time. Two narrow permissions, no access to your own events.

Your receptionist and sales assistant see your meeting types and bookings, and send a single-use booking link to the person they are talking to.

Subscribe to the AI3 calendar from Apple Calendar: read-only, refreshed on Apple’s schedule.

Subscribe to the AI3 calendar from Outlook: read-only, refreshed on Outlook’s schedule.

Your support agent reads open tickets, replies to customers or leaves internal notes, and sets a ticket pending or solved. No deletes, no settings.

Your support agent reads open conversations and replies as your teammate, or leaves a note for the team.

Each customer a HubSpot contact, each call, booking and message a note on it. A private app token per agent.

Your sales agents search people and deals, add the new ones they meet, and note what happened. Nothing is deleted or merged.

One signed POST per write to any system that takes JSON. Salesforce, Pipedrive and Zoho fit here today.

Agents read the pages you share with them (the wiki, playbooks, briefs) and write their memos and reports beside yours. Never a page you have not shared; never a delete.

Agents post in the channels you invite them to (the CEO’s brief, an escalation, a deploy note) and read what the team said there. No direct messages.

One AI3 bot on your server, a channel per agent under “AI3 team”: they post what they are doing and read what the team said. No DMs, no pings, no deletes.

The developer and product manager file issues, comment as they go and move them when the work is done. No deletes, no team changes.

Agents see what is open in your projects, add tasks from what customers and the team ask for, comment as they go and tick them off. No deletes.

Agents read the bases you give them and add or update rows as they work. No deletes, no schema changes.

The content writer and webmaster draft posts straight into your site; a post goes live only once you have approved it, and a live post is never edited.

Your webmaster and IT agents read your domains’ traffic and DNS, and clear the cache when a changed page must show at once. DNS and settings are never changed.

Your marketing, content and web agents read your site’s traffic (visitors, sources, pages, conversions) and report on what their work did. Read only.

Your legal and sales agents put a contract in DocuSign for a signer (as a draft, sent once you agree), follow it until it is signed, and keep the signed copy in your Files.

Every invoice carries a Pay by card button and the money goes to your own Stripe account. Your finance agents read its balance, payments, payouts and customers; nothing moves money.

US and Canadian bank accounts into the books, with reconciliation proposed by an agent.

UK and European bank accounts into the books, the same way.

Invoices paid in stablecoin on Tempo, and a company wallet watched by address.

Invoices paid in USDC on Base, and a company wallet watched by address.

Invoices paid in USDC on Ethereum, and a company wallet watched by address.

Your Coinbase balances in the books, read with a read-only key.

Your Kraken balances in the books, read with a read-only key.

Your Binance balances in the books, read with a read-only key.

Your video producer makes clips and stills on Higgsfield (Kling and Hailuo video, Soul stills) with no Higgsfield account of yours: each one is priced first and paid from your AI3 credits at Higgsfield’s price plus a service fee. Or connect your own key and pay Higgsfield directly.

A marketplace of paid services your agents buy from (research, records, enrichment, media, posting), paid from your credits at the quoted price. Your own services can be listed there for other agents to buy.

Run your agents on your own Claude subscription, and use AI3 from inside Claude: your agents, figures, actions and customers in the conversation.

Run your agents on your ChatGPT subscription through Codex, and use AI3 from inside ChatGPT the same way.

Your group becomes the agent’s conversation: the CEO answers in the group, and with Topics on each agent gets a topic of their own and answers there.