COHO API & MCP terms

These terms, effective from 8 October 2026, apply when you use the COHO API, or connect an AI assistant or other tool to your COHO account through our MCP server. They work alongside our terms and conditions, subscription terms, data processing agreement, privacy policy and acceptable use policy. If anything in these terms conflicts with our other terms, these terms win for anything to do with the API and MCP server. Our data processing agreement still wins for anything to do with handling personal data on your behalf.

You accept these terms on behalf of your organisation when an owner or admin first creates an API key or turns on MCP access for your account.

Who these terms are between

These terms are between you, the COHO account holder, and Company For Life Ltd, trading as COHO (“we”, “us”). Our company details are in our terms and conditions.

Who can use the API and MCP server

  • Only owners and admins of your account can create API keys or turn on MCP access.
  • MCP access is off by default for other users. An owner or admin can turn it on for them.
  • You’re responsible for everyone you give access to, and for everything done using your API keys and MCP connections.

Keeping access secure

You must:

  • keep API keys secret, and never put them in code that runs in a browser or on someone else’s device;
  • give each key and connection only the access it needs;
  • revoke a key or connection straight away if you think it’s been compromised, and tell us at team@coho.life.

AI assistants

When you connect an AI assistant, such as Claude or ChatGPT, through our MCP server:

  • you choose the assistant, and the data it reads through MCP is sent to its provider on your instruction. This is one of your documented instructions under our data processing agreement;
  • the assistant’s provider is not our sub-processor. Your relationship with them is between you and them, under their own terms;
  • anything the assistant does in your account through MCP is treated as done by you;
  • we don’t check what an assistant tells you or does. Check its output before you rely on it.

Credits and your free allowance

We measure use of the API and MCP server in credits:

Use Credits
A successful request or tool call that reads data 1
A successful request or tool call that creates, changes or deletes data 2
A request or tool call that fails 0
Connecting, and protocol messages such as listing tools 0

API and MCP use share one pool of credits for your account. Each account has a free allowance of credits each calendar month. Your allowance, usage tiers and their prices are shown in your account settings.

Usage tiers

If you need more than your free allowance, you can choose a usage tier with a higher monthly ceiling.

  • When you reach your allowance or your tier’s ceiling, further requests and tool calls are refused until the 1st of the next month, unless you move up a tier.
  • When you move up a tier, requests and tool calls work again straight away.
  • Usage tiers are charged in arrears, as one line on your monthly Atrium invoice for the previous calendar month. If you moved up during a month, you’re charged for the highest tier you reached.
  • Prices are shown excluding VAT. We add VAT at the current rate. Payment is taken by card through Stripe, as set out in the Atrium terms.

Fair use and limits

The API and MCP server are shared by all our customers. To keep them working well for everyone:

  • we set rate limits for each key, user and account. Requests over a limit are refused, and can be retried after a short wait;
  • you must not scrape data, resell or share access with anyone outside your organisation, overload our systems, or try to get around any limit or security measure;
  • our acceptable use policy applies to everything done through the API and MCP server.

We monitor use to protect our systems. We may slow down, pause or revoke a key or connection if it exceeds its limits, puts our systems or data at risk, or breaks these terms. Where we can, we’ll tell you first and give you a chance to put things right. In urgent cases, we’ll act first and explain afterwards.

Promotional allowances

We may give your account a larger or unlimited allowance for a set period, for example for attending a launch event. Any promotional allowance:

  • lasts only for the period we tell you, and then your account returns to your normal allowance;
  • doesn’t change rate limits or fair use, which still apply;
  • may be withdrawn early if it’s misused.

Usage records

We keep records of each request and tool call, including the key or user, the time, what was used and how many credits it counted for. We use them to run the service, keep it secure, enforce limits and bill you. You can see your account’s usage in your account settings. Our Privacy policy explains how we handle them.

Changes to the API and MCP server

We’ll give you at least 30 days’ notice before we change your free allowance, the prices of usage tiers, or remove anything from the API or MCP server that you rely on, unless we need to act sooner for security or legal reasons.

Our responsibility to you

The API and MCP server are part of our service, and the limits on our responsibility in our Terms and conditions apply to them. We don’t promise that they’ll be uninterrupted or error free. We’re not responsible for loss caused by an AI assistant or other tool you connect, or by anyone using your keys or connections.

Changes to these terms

We may update these terms from time to time. The effective date at the top shows when they were last changed. If a change materially affects you, we’ll tell you at least 30 days before it takes effect.

Law

These terms are governed by the law of England and Wales. The courts of England and Wales deal with any dispute.