Accounts and people

POST /v1/signup makes an account with its first key and its balance. The bot that signs up accepts the terms for the business it acts for, and the account keeps the version it accepted. Everything an agent does happens in that account: its records, its call log, its balance and its keys.

The people who run the business open the account page at https://conecto.chat/account. They sign in with a link emailed to them, which works once, within 30 minutes. The page shows the balance, the calls the bots made, the people, the keys and the rentals.

The owner is the person the account answers to. Only the owner raises a spending limit, and the account's warnings and approval requests go to them.

• Named at signup. owner_email makes that address the owner at once. They have nothing to confirm.
• Named later. account_set_owner_email emails the person a link to confirm. Nothing changes until they open it.
• No owner yet. The bot raises its own limits, and a call that needs a person's approval answers no_approver.

account_owner_link makes a one-time link that signs the owner in with no password. Its page opens it where they are needed, like people for a role only the owner gives, or limits. A bot hands that link to the owner when something is theirs to do.

A second owner, like a business partner, gets everything the owner gets. Only the owner adds one.

A bot adds a member or an auditor with admin_save_person: their email, their teams or areas, and for an outsider the last day of their access, like a bookkeeper until the year-end. They are told by email. Making someone an admin, a billing person or an owner is the owner's, on the account page. An account holds up to 100 people besides the owner.

admin_remove_person takes a person's access away at once, with their own assistants.

Anyone on the account can connect their own ChatGPT, Claude or Grok, or a Copilot Studio agent, through a connector. It acts as that person, within their teams and role, so an auditor's assistant only reads. The call log names them, like "Ben, through Claude", and each call is charged to the person's team that holds the tool's area. The owner can list which apps people may connect.

A second bot joins the account with a join code. admin_make_join_code makes one for a team and its areas, and the code can keep the bot to reading or to drafts. It is shown once, works once, and lasts 7 days unless it is set to any number from 1 to 30.

The other bot signs up with the code in place of the usual fields:

{"bot_name": "Accounting bot", "join": "conecto_join_..."}

Its key works for the code's team, within its areas. The reply has joined: true and the key's scope, and brings no free credit. The account's balance pays for both bots.

Once the company proves its email domain, colleagues can join on their own.

1. admin_save_domain adds the domain, like hansenvoss.example, and answers with a TXT record that starts conecto-verification=.
2. Once the record is in the domain's DNS, the same tool with verify: true proves it.
3. joining says what happens next. request lets people ask to join, and an owner, an admin or the bot approves each one. open lets them join at once as members. off stops both. Only the owner turns on open.

When someone asks, the bot gets the event account.join_requested, and admin_decide_join_request lets them in or declines them. People who join come in as members, in the domain's team and areas, and can connect their own assistant. A public email provider, like gmail.com, is refused, since anyone can have an address there. An account holds up to 10 domains, and a person who was declined can ask again after 30 days.

The admin area, at https://api.conecto.chat/mcp/admin, does what the account page does: people and their teams, join codes for other bots, the company's email domains and requests to join, and bridges. It takes a key of the company-wide team with no areas, tool list or read-only limit, or the assistant of the owner or an admin. On an account with no owner email, any key runs it. What stays the owner's answers owner_required, and account_owner_link makes them a link to the page for it.

When a bot starts working for a business, admin_overview reads the account in one call: the balance, the month's spending, the teams, the people, the systems connected and what the owner said about the business.

The owner can connect the company's own identity provider over OpenID Connect, like Okta, Microsoft Entra ID or Google Workspace, at no charge. People on the company's proved domains then sign in through it. With single sign-on required, members on those domains must use it, and the owner keeps the emailed link as a way back in.