> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/legal/api-terms-of-service.md).

# API Terms of Service

Terms for the Brewfather API, Connected Apps, MCP and AI-agent access, webhooks, device endpoints, credentials, and API Data.

**Last updated: 19 October 2026**

{% hint style="info" %}
**In short.** This summary is not part of these API Terms and is not binding. If it differs from the full API Terms below, the full API Terms apply.

* You are a Developer when you use any programmatic access (API keys, Connected Apps, MCP servers, AI agents, webhooks, device logging), even a script or AI assistant on your own account. Using the official apps does not count.
* Keep credentials secret. Never ask for, collect or store a user's Brewfather password, one-time code or sign-in session.
* Using your own account for your own purposes ("Own-Account Use") carries fewer duties, but you still may not bulk-extract Brewfather Materials or train models on them.
* Apps serving other people must make the Section 5 disclosures, get each user's authorisation, register if they hold users' credentials, and follow the Section 7.3 safeguards for MCP servers and AI agents.
* Connected Apps need our written approval.
* No training or improving AI models on API Data or Brewfather Materials without our written approval, except your own data under Own-Account Use.
* Competing brewing services get no API permission without a signed agreement. Your legal right to export or switch your own data is not affected.
* Stay within rate limits, which we can change at any time, and do not work around them.
* We can restrict or end access, immediately for a breach. Our liability is limited (Section 22), and mandatory consumer rights still apply.
  {% endhint %}

These Brewfather API Terms of Service ("API Terms") are a binding agreement between **Warpkode AS** ("Brewfather", "we", "us", or "our") and each individual or legal entity that accesses or uses the API Materials ("Developer", "you", or "your"). Warpkode AS is a Norwegian private limited company (*aksjeselskap*) registered in the Register of Business Enterprises (*Foretaksregisteret*) under organisation number **921 463 146**.

You are a Developer whether you write code, operate a service, or connect an AI assistant or other Application to your own Brewfather account. Using Brewfather's official apps and websites as provided does not make you a Developer.

You agree to these API Terms when, after a reasonable opportunity to review them, you:

* accept them;
* create, copy, or use an API key or other credential;
* approve or complete a Connected App or MCP authorisation; or
* access or use the API Materials, or let an Application do so.

If you act for an organisation, you represent that you have authority to bind it, and "you" includes it. If you do not agree, do not access or use the API Materials.

## 1. Definitions

* **API Materials** means:
  * the Brewfather REST API, in every version;
  * the Brewfather MCP server and any other AI-agent, tool-calling, or headless interface we provide;
  * Connected App and OAuth authorisation flows;
  * webhooks, the Custom Endpoint, Custom Stream, and other device-logging endpoints;
  * every other programmatic interface, documented or not, that we make available or use to provide the Service;
  * API keys, user IDs, OAuth client credentials, access and refresh tokens, integration and logging IDs, and other credentials; and
  * documentation, specifications, OpenAPI and other schemas, tool names and descriptions, sample code, software, responses, and related materials.
* **Application** means any software, service, website, script, bot, device, firmware, MCP server or client, AI Agent, or other technology that accesses or uses the API Materials, whether you build, operate, distribute, configure, or connect it.
* **AI Agent** means an Application that uses an artificial-intelligence model to retrieve data, or to choose or carry out actions, through the API Materials. The term includes an AI assistant, chatbot, coding assistant, MCP host or client, browser or computer-use agent, or agent framework.
* **MCP Server** means a server that implements the Model Context Protocol, or a similar tool-calling or function-calling protocol, to expose API Materials or API Data to an AI model.
* **Connected App** means an Application that we have approved to use a Brewfather authorisation flow, such as OAuth, and that appears in a Brewfather User's Connected Apps list. A client connected to the Brewfather MCP server can appear there too.
* **API Data** means any data, content, or information obtained or derived from Brewfather through the API Materials, including User Content and Brewfather Materials. It excludes data you independently originated or lawfully held without obtaining it from Brewfather, even if you also submit it to Brewfather.
* **Brewfather Materials** means data and content that Warpkode AS or its licensors provide, rather than content a Brewfather User created, including shared ingredient, equipment, water, mash, fermentation, style, and other reference databases; default data; calculation logic and formulas; and the structure, selection, and arrangement of the API Materials. Values Brewfather computes for a user's own recipes, batches, and other records are part of that user's API Data.
* **Brewfather User** means a person or entity with a Brewfather account, or a brewery workspace, whose account, workspace, or data is accessed through the API Materials.
* **User Content** has the meaning given in the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md).
* **Own-Account Use** means access by a Brewfather User (an individual or an organisation), with credentials or a connection issued to it, to its own account or to a brewery workspace it is authorised to access. To be Own-Account Use, the access must also be for the user's own internal purposes or, for a workspace, that workspace's, and not for or on behalf of another person or a Competing Brewing Service. Examples are personal scripts, home-brewery or brewery automation, internal reports, and an AI Agent the user connects to its own account or workspace.

## 2. Scope and ways to connect

These API Terms supplement and incorporate the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md). If the two conflict, these API Terms control, but only for access to and use of the API Materials and the handling of API Data. The [Privacy Policy](https://docs.brewfather.app/legal/privacy-policy.md) describes how we process personal data.

The API documentation, including [API](https://docs.brewfather.app/api.md), [Connected Apps](https://docs.brewfather.app/connected-apps.md), and [Webhooks](https://docs.brewfather.app/webhooks.md), forms part of these API Terms. Additional written terms may apply to particular endpoints, access tiers, beta features, or approved partnerships. A separate written agreement signed by Warpkode AS overrides these API Terms only to the extent it expressly says so.

We currently offer these routes:

1. **API keys.** The account holder can create API keys with selected scopes, for Own-Account Use or for an Application they authorise. The Service and documentation show the plan requirements, number of active keys, scopes, expiry, and any workspace binding. A key's secret value may be shown only once.
2. **Connected Apps.** A third-party Application may use a Brewfather authorisation flow only after we approve it in writing under Section 6, except as Section 7.2 allows for our MCP authorisation. Users can review and revoke Connected Apps in the Service.
3. **The Brewfather MCP server and other AI Agents.** An AI Agent connects with an API key the user creates for it, or through the OAuth authorisation of our MCP Server or other AI-agent interface, which the user approves (Section 7.2).
4. **Webhooks and the Custom Endpoint.** We can send data to an HTTPS endpoint the user configures.
5. **Device-logging endpoints.** Devices and services can send readings to Brewfather using a logging URL or integration ID.

We decide which routes, scopes, tools, and data to offer, and may require an Application serving more than one Brewfather User to use a particular route, such as an approved Connected App flow. An authorisation screen, inclusion in Connected Apps or our documentation, an integration listing, or technical access does not expand the licence in Section 3 or replace a required written agreement.

## 3. Limited licence

Subject to your continuing compliance with these API Terms and the API documentation, we grant you a limited licence to access and use the documented API Materials solely to develop and operate a Permitted Integration. The licence is revocable, non-exclusive, non-transferable, and non-sublicensable, and lasts only while these API Terms remain in effect.

A **Permitted Integration** is an Application that complements a Brewfather User's use of Brewfather and complies with these API Terms. Examples are Own-Account Use, a brewing-device or hardware integration, a reporting tool, an AI Agent acting for the user, and an internal workflow.

A **Competing Brewing Service** (Section 10) is not a Permitted Integration and receives **no permission or licence** under these API Terms to access or use any API Materials or API Data. Only a separate written agreement signed by Warpkode AS that expressly identifies the Competing Brewing Service and the authorised use can grant it. A Brewfather User's consent, possession of credentials, an integration's appearance in documentation, our silence, or prior technical access does not.

Any other use not expressly permitted is prohibited unless we approve it in a prior written agreement, and a Brewfather User's consent to an Application does not by itself authorise a use these API Terms prohibit. You can ask for authorisation at <hello@brewfather.app>, but it exists only if we grant it in writing. No licence is implied, and we reserve all rights not expressly granted. Where API or MCP access is included in a paid subscription you hold, Sections 12, 13, 19, and 24 govern changes, fees, suspension, termination, and updates to these API Terms. Otherwise, access is a revocable licence, not a right.

## 4. Credentials and security

You must:

1. give accurate and current information about yourself and your Application when we ask;
2. access only accounts, workspaces, and API Data that you own or that a Brewfather User has expressly authorised your Application to access, and only within the scopes, workspace, and role granted;
3. use only the documented authentication methods, and request only the scopes your Application needs, telling each Brewfather User which they are;
4. never ask for, collect, or store a Brewfather User's password, one-time code, or sign-in session, or ask a user to sign in to Brewfather through a page you control;
5. keep API keys, tokens, client secrets, logging IDs, and other credentials confidential and securely stored, encrypted at rest where you hold them for other people;
6. not publish credentials, embed them in public or client-side code, or sell, transfer, or share them, except with an Application that the Brewfather User has expressly authorised and that complies with these API Terms;
7. not use one Brewfather User's credentials to access another user's account or workspace, or share one set of credentials across multiple users; and
8. promptly revoke or rotate compromised credentials, and report any actual or suspected unauthorised access to <hello@brewfather.app>.

You are responsible for all activity through credentials issued to or accepted by you, and for the acts and omissions of your employees, contractors, agents, service providers, AI Agents, and Application as if they were your own. If you are a consumer, this paragraph covers only activity you authorised and loss caused by your breach of these API Terms, such as failing to keep credentials secure.

Creating another API key does not revoke an existing one, so you must separately revoke any key that is no longer needed or may be compromised.

Authorisation ends when:

* an API key, grant, or Connected App approval is revoked or expires;
* a refresh token is rejected, or a `401 Unauthorized` response is not resolved by the documented refresh flow;
* the plan, role, or workspace membership that access depends on is lost;
* the user withdraws authorisation or tells you to stop; or
* we notify you.

You must then stop attempting access and delete affected API Data as Section 9 requires. An access token that expires while its grant remains valid may be renewed through the documented refresh flow. A response refusing a particular scope or operation ends access to that scope or operation only, and you must not retry it repeatedly or try to obtain it another way.

## 5. User authorisation and transparency

This Section does not apply to Own-Account Use.

Before accessing a Brewfather User's API Data, you must tell the user clearly and accurately:

* who operates the Application and every AI Agent or MCP Server involved;
* what API Data the Application will access and what actions it can take, including whether it can create, change, or delete data;
* why the data is needed and how it will be used, stored, disclosed, and deleted;
* every third party that will process the data, including each AI model provider, and the retention and training practices that apply to it; and
* how the user can withdraw authorisation and request access, correction, export, or deletion.

You must obtain every consent and other legal basis the law requires. Authorisation must be specific and informed, freely given where consent is the legal basis, and obtained without deceptive interfaces or misleading statements. You must make the required disclosures, and obtain any required new authorisation, before you access additional data, take new kinds of action, or use API Data for a materially different purpose.

An Application made available to anyone other than you must have an accurate, easily accessible privacy policy and end-user terms that comply with the law and do not conflict with these API Terms or the Brewfather Terms of Service.

Before you make available to other people an Application that stores or uses their Brewfather credentials, including a hosted MCP Server, you must register it with us at <hello@brewfather.app>, naming the Application, its operator, and its purpose. Integrations listed in Brewfather documentation are registered. We may refuse or withdraw a registration at any time. Registration is not approval as a Connected App or an endorsement, and does not expand the licence in Section 3.

## 6. Connected Apps

A Connected App must:

1. have our written approval before it uses a Brewfather authorisation flow, and comply with any partner agreement we require and any brand guidelines and technical requirements we provide;
2. use only the client identity, redirect addresses, and scopes we have approved;
3. identify the Application and its operator accurately on every authorisation;
4. handle each user's authorisation separately, honour revocation in Connected Apps immediately, and respect any per-account connection limit;
5. verify that data it receives from Brewfather came from Brewfather where the documentation provides a method, and process it only for the authorised purpose; and
6. provide its own user support, except for questions about Brewfather itself.

We may approve, refuse, suspend, or withdraw a Connected App, change its scopes, or require changes to it, at our discretion, subject to any separately signed agreement. Section 22 governs any liability.

## 7. MCP, AI Agents, and automated actions

### 7.1 Connecting an AI Agent to your account

If you connect an AI Agent or other Application to your Brewfather account or workspace, you authorise it to act for you within the scopes and workspace you grant. In that case, we may treat every request made with your credentials or authorisation as yours. You are responsible for choosing the Application, its AI model provider and settings, and your instructions to it, and for reviewing what it does.

AI Agents can misread instructions, produce inaccurate summaries, or be manipulated by text in the data they read ("prompt injection"). Grant only the scopes an AI Agent needs, prefer read-only access, keep an independent backup, and review its changes. We are not responsible for an AI Agent's output, decisions, or actions, or for changes to or loss of data made through credentials or authorisations you provided, except to the extent mandatory law makes us responsible.

Data an AI Agent reads from Brewfather is disclosed to its operator and model provider under their own terms and privacy notices. We do not control their retention, training, or other practices, so review those terms and settings before you connect.

### 7.2 The Brewfather MCP server

Our MCP Server and any other AI-agent interface we offer, including its tools, scopes, data, eligibility, plans, limits, and supported clients, may change or be withdrawn, and may be offered as a preview. Access may require an eligible paid plan and is checked on every request, so losing eligibility, workspace membership, or role ends access without notice. Approving a client gives it access only to the workspace and scopes shown on the authorisation screen, and you can revoke that access in the Service.

We decide which AI clients may use our MCP authorisation and may block any client. A client that can complete the authorisation may use it only to act on each user's own requests, for that user. That does not make it an approved Connected App, and its operator needs our written approval for any other use, such as access for its own purposes or building a dataset.

### 7.3 Building or operating an MCP Server or AI Agent

If you build, host, distribute, or operate an MCP Server or AI Agent for anyone other than yourself, you must also:

1. authenticate each Brewfather User separately with that user's own authorisation, never a shared key, and keep each user's data and conversation context separate;
2. request read-only scopes unless a feature the user has chosen needs write or delete access;
3. obtain the user's explicit confirmation before each action that deletes data, changes more than one record, or cannot easily be reversed. Only the user can turn off confirmation for a kind of action other than deletion, through a clearly visible setting for that kind of action that is on by default. Confirmation before deletion cannot be turned off;
4. describe every tool and action accurately, and not hide tools or capabilities;
5. treat API Data and other tool output as untrusted input, and design the Application so that instructions embedded in API Data cannot cause actions the user did not request or disclose data to anyone the user did not authorise;
6. make every AI model call with API Data that you make or control only to perform the user's request, under terms that prohibit the provider from using the data to train or improve its models. You must disclose that provider to the user as Section 5 requires;
7. where you return API Data to an AI client the user chose, tell the user that the client's own terms apply, and not configure or direct that client or its provider to train on the data;
8. keep a record of the write and delete actions taken for each user that is sufficient for the user and us to investigate them; and
9. not use an AI Agent to create Brewfather accounts, accept terms, make purchases, or change a subscription for a user, or to retrieve data in bulk or systematically beyond what the user's request needs.

### 7.4 No rights for AI providers

An AI model provider, MCP host, or other intermediary that receives API Data because a Brewfather User or Developer sent it does not, by receiving it, obtain any licence from Warpkode AS to Brewfather Materials or API Materials. Warpkode AS reserves all rights to use them for text and data mining, including training, fine-tuning, evaluating, or grounding AI models, as Section 15 describes.

## 8. Webhooks, Custom Endpoint, and device-logging endpoints

You are responsible for the security, availability, and lawful use of any endpoint you configure to receive data from Brewfather, and for the data once it is delivered. Use HTTPS and keep endpoint addresses and secrets confidential. We may retry, delay, batch, drop, or stop deliveries, disable an endpoint that fails or is used abusively, and change payloads as documented. Delivery is not guaranteed.

Logging URLs and integration IDs are credentials. Send only data from devices or services that you own, control, or are authorised to use, respect the documented minimum logging interval, and do not use a logging endpoint as general-purpose storage or to send unrelated data. We may ignore, rate-limit, or discard readings that do not comply.

## 9. API Data use, privacy, and security

You may collect, use, store, and disclose API Data only as necessary to provide the user-facing functionality of the Permitted Integration that the relevant Brewfather User expressly authorised and that you clearly disclosed. Unless we have given prior written approval, you must not:

* sell, rent, license, or otherwise monetise API Data;
* use API Data for advertising, marketing profiles, surveillance, data-broker activities, or eligibility, credit, insurance, employment, or similar consequential decisions;
* use API Data, API Materials, or Brewfather Materials to train, fine-tune, distil, evaluate, benchmark, or otherwise improve an artificial-intelligence or machine-learning model, or to build a dataset for that purpose;
* allow another person, including an AI model provider, to do so;
* keep API Data in an embedding index, vector database, search index, or cache except to serve the same Brewfather User's authorised requests, and then only for as long as this Section allows; or
* combine API Data with other data in a way that exceeds the user's authorisation or attempts to identify an anonymous or pseudonymous person.

**Own-Account Use.** For Own-Account Use:

* the restrictions above, and the retention and deletion duties in this Section and in Sections 4 and 19, do not limit how you use or keep data about your own account, or about a workspace you own or administer. That data includes values Brewfather computes for your records;
* processing of that data by an AI provider you choose is not a breach; and
* for your own User Content and the values Brewfather computes for your records, these Own-Account Use rules prevail over any inconsistent purpose, service-provider, retention, or deletion requirement elsewhere in these API Terms, including in Sections 11 and 18.

Even for Own-Account Use, you must not extract Brewfather Materials in bulk, use them to train or fine-tune a model, or make them available to others, and Section 7.4 still applies to any AI provider. These Own-Account Use rules do not exempt anyone who operates an Application for other people, grant rights in Brewfather Materials, or affect privacy and security law.

**Disclosure.** You may disclose API Data to a service provider only where:

* the disclosure is necessary to operate the Permitted Integration;
* the service provider is contractually bound to confidentiality, security, purpose-limitation, and deletion obligations at least as protective as these API Terms; and
* you remain responsible for its acts and omissions.

You must not disclose one user's non-public API Data to another user or a third party without specific authorisation and a valid legal basis.

**Your duties.** You must:

1. comply with all applicable privacy, data-protection, cybersecurity, direct-marketing, export-control, and sector-specific laws;
2. maintain appropriate technical and organisational safeguards proportionate to the nature and sensitivity of the API Data, including encryption in transit, appropriate protection at rest, least-privilege access controls, secure credential storage, timely security updates, logging, monitoring, and tested incident-response procedures;
3. keep API Data only for as long as necessary for the authorised purpose;
4. unless the law requires longer retention or the Records paragraph below permits it:
   * promptly delete affected API Data when the user requests deletion, withdraws authorisation, or deletes the relevant account or workspace, or when your access or these API Terms end; and
   * in all cases complete deletion within 30 days;
5. protect retained backups from further use and delete them through the ordinary secure backup lifecycle; and
6. support applicable user rights, including access, correction, deletion, objection, restriction, and portability.

**Records.** After authorisation ends, you may keep the action records Section 7.3 requires, and other minimal security metadata, for as long as necessary and lawful to:

* investigate an incident;
* establish or defend a legal claim; or
* show compliance with these API Terms.

You must restrict access to them, use them only for those purposes, leave out credentials and API Data content unless strictly necessary, and never use them to keep the integration running or for a purpose this Section prohibits.

**Privacy roles.** Roles depend on the actual purposes and means of processing, not on labels in these API Terms. Where each of us processes personal data for its own purposes, each is an independent controller. If the facts make us joint controllers, or one of us the other's processor, we must first enter the arrangement or data-processing agreement the law requires; these API Terms are not one. Before processing begins, you must put in place any data-processing agreement, international-transfer mechanism, data-protection impact assessment, regulatory consultation, or other compliance measure your processing requires.

**Security Incidents.** If you become aware of actual or suspected unauthorised access to, or acquisition, disclosure, alteration, loss, or destruction of, API Data or credentials (a "Security Incident"), you must:

* notify us at <hello@brewfather.app> without undue delay and, if you act in a business or professional capacity, in any event within 72 hours;
* take prompt steps to contain and remediate it;
* preserve relevant evidence; and
* reasonably cooperate with us.

If you act in a business or professional capacity, you must not make a public statement about a Security Incident that identifies Brewfather without first consulting us, unless the law requires the statement. These duties do not delay or prevent a notification that the law requires you to make to a regulator, supervisory authority, user, or other affected person.

## 10. Competing Brewing Services have no API permission

A **Competing Brewing Service** is any software, service, platform, product, or AI model, agent, or assistant whose primary purpose is to replace, replicate, or compete with Brewfather's core brewing-software functionality, whether delivered through a conventional interface or an AI Agent. That functionality includes beer-recipe design or management, brew and batch tracking, brewing inventory management, or brewery production management, or a substantially similar combination of those functions.

Two things are not a Competing Brewing Service on their own:

* a device, appliance, or hardware-vendor service merely because it has ancillary recipe or batch features needed to operate its own hardware; and
* a general-purpose AI assistant or MCP host merely because a user can discuss brewing with it or connect it to Brewfather. Its operator still obtains no licence to Brewfather Materials or API Materials (Section 7.4).

In every case, primary purpose is assessed separately for each product, feature, application, plugin, custom assistant, skill, or agent, so a brewing-specific component of a broader platform or device ecosystem can be a Competing Brewing Service.

An integration listed in Brewfather documentation may use the API Materials only for its documented complementary purpose and within any separate written authorisation. Listing never authorises competitive migration, general data extraction, or use beyond that purpose.

Without the separate written agreement required by Section 3, you must not, directly or indirectly:

1. use the API Materials or API Data to build, operate, improve, promote, support, or supply a Competing Brewing Service;
2. access, pull, extract, copy, aggregate, synchronise, transform, transfer, or disclose API Data for import into, population of, or migration to a Competing Brewing Service;
3. offer or enable an export, migration, switching, bridging, mirroring, or ongoing synchronisation feature whose purpose or effect is to move Brewfather Users or their data to a Competing Brewing Service;
4. use user-supplied credentials, shared accounts, an AI Agent, an MCP Server, an intermediary, a proxy, automation, or any other method to carry out a use prohibited by this Section;
5. use the API Materials, API Data, Brewfather data structures, tool descriptions, or API responses to:
   * replicate Brewfather;
   * create a substitute service or dataset;
   * conduct competitive analysis or benchmarking for a Competing Brewing Service; or
   * train or improve a competing product or model; or
6. encourage, assist, or permit another person to do any of the above.

Access or use by or for a Competing Brewing Service without that agreement is outside the licence, prohibited, and unauthorised (Section 18).

These API Terms do not stop you from writing or publishing a review, rating, comparison, or performance assessment of Brewfather, including one you give to a publisher or review site, unless it is knowingly false or misleading. This does not permit access or copying that these API Terms otherwise prohibit.

**Your own data.** This Section restricts Developers and Applications. It does not restrict you, as a Brewfather User, from:

* exporting your own content with the export features in the Service and taking the exported file anywhere;
* switching to another provider, or using one alongside Brewfather, under Section 13 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md); or
* obtaining your own content through a right that mandatory law gives you, including retrieval on termination, data portability, and any statutory connected-product data-access right, whether you make the request yourself or through a representative you authorise.

Nothing in this Section requires you to waive such a right, and a term in this Section has no effect to the extent it would do so. Nothing in these API Terms claims ownership of a Brewfather User's data or limits a right that cannot lawfully be waived or restricted.

Users can get their data through:

* [backup export](https://docs.brewfather.app/data-safety.md#id-1-export-a-full-backup-web) and recipe and inventory exports in common formats;
* the free consumer retrieval route in Section 13 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md); and
* where applicable, statutory data requests sent to <hello@brewfather.app> or by any other method the law requires us to recognise.

We will facilitate and fulfil valid statutory requests as that law requires. Except for an EU Data Act switch, described below, these routes are separate from API licensing. They give no Competing Brewing Service or other third party a general API permission, or permission to access or use the API Materials or build a migration integration.

**EU Data Act and other non-waivable law.** A non-waivable law may require us to make particular data available to a user or a user-chosen recipient, or to support a user's switch to another provider. If it does, we will comply to the extent and by the method that law requires. Section 13 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md) describes consumer retrieval and switching. Such laws include Regulation (EU) 2023/2854 (the **EU Data Act**) where it applies to data generated by a connected product or related service (Chapter II) or to switching between data processing services (Chapter VI).

During a switch the user has requested under Section 13 of the Brewfather Terms of Service, the destination provider the user names may, as the user authorises and the law permits:

* use the export or switching process we designate for that switch; and
* receive, import, keep, and use that user's exportable data to provide its service to that user.

This permission applies despite the rest of this Section and Sections 3, 9, 11, and 19. That permission covers only the switching user's exportable data and the switch itself. It is not a public API licence and gives:

* no general API access;
* no access to other users' content;
* no rights in Brewfather Materials or our software beyond what the law requires; and
* no permission for ongoing synchronisation, mirroring, or any other extraction or competitive use of the API Materials.

The switching timetable and these limits apply only to a switch and do not restrict a separate statutory data-access right, which we will meet as that law requires.

Every restriction in this Section applies only to the maximum extent permitted by applicable competition, data-access, consumer, and other mandatory law.

## 11. Other prohibited conduct

You must not, and must not enable or assist another person to:

* access or use the API Materials in breach of law, third-party rights, these API Terms, the Brewfather Terms of Service, or the API documentation;
* access an account, workspace, endpoint, field, scope, tool, or system without authorisation, or undermine authentication, permissions, workspace boundaries, privacy settings, or access controls;
* scrape the Brewfather Service, use undocumented or internal interfaces, or access API Data by any method other than a documented interface we authorise for that purpose;
* use a browser, computer-use, or other AI Agent to operate the Brewfather user interface to extract data, to act at a volume or speed beyond ordinary individual use, or to avoid the API Materials, their scopes, or their limits;
* reverse engineer, decompile, disassemble, or attempt to discover source code, non-public schemas, algorithms, prompts, model configurations, or trade secrets, except to the limited extent mandatory law prohibits this restriction;
* attempt to extract system instructions, hidden tool definitions, credentials, or security controls from the Brewfather MCP server, AI Brewing Assistant, or any other Brewfather AI feature;
* bypass or interfere with rate limits, fees, subscription or plan requirements, security measures, usage restrictions, or technical controls;
* introduce malware or harmful code, probe or test vulnerabilities without prior written authorisation, or disrupt, overload, degrade, or damage Brewfather or any other system;
* re-expose, resell, sublicense, or syndicate the API Materials or API Data, or provide an abstraction layer, proxy, public MCP Server, or other general-purpose service for them. The exception is an Application that serves each Brewfather User only with that user's own authorisation and complies with Sections 5 and 7.3, including registration under Section 5;
* create a cross-user dataset from API Data, except where strictly necessary to operate an authorised Permitted Integration;
* remove or alter proprietary notices or required attribution;
* misrepresent your identity, your Application's purpose or capabilities, the source or ownership of API Data, or your relationship with Brewfather; or
* use Brewfather's name, trademarks, or branding except as Section 15 permits.

## 12. Technical requirements, rate limits, and changes

You must follow the current API documentation and all technical requirements, scopes, quotas, and rate limits. You must also design your Application to handle errors, retries, revocation, paging, API changes, and `429 Too Many Requests` responses safely, honour any `Retry-After` header, and avoid unnecessary polling.

You must not exceed or evade a limit that applies to you by any method, including by:

* creating additional API keys, grants, MCP connections, or Brewfather accounts you control;
* rotating credentials;
* creating duplicate Applications; or
* where a limit applies to each key or connection, spreading one Application's or one user's traffic across several keys or connections to get a higher allowance.

Using each Brewfather User's own credentials solely for that user's authorised requests is not circumvention.

We may:

* set and change rate limits and quotas at any time;
* set different limits for each route, Application, plan, workspace, or Developer;
* count requests made through an AI Agent or MCP Server toward any applicable limit;
* require an Application to identify itself in its requests; and
* monitor API usage to operate, secure, improve, and enforce the API Materials and these API Terms.

We may add, change, deprecate, suspend, or discontinue any endpoint, tool, field, scope, feature, access tier, or version. We will use reasonable efforts to announce material breaking changes when practicable, but we do not guarantee backward compatibility, continued availability, support, or any service level. If API access forms part of a paid consumer digital service, changes, conformity, notice, termination, and remedies remain subject to Sections 9, 12, and 13 of the Brewfather Terms of Service and mandatory law.

Beta, preview, or experimental features may be changed or withdrawn at any time and may be incomplete or unreliable. You must not use them in a safety-critical or production-dependent workflow unless we agree otherwise in writing.

## 13. Fees

API, MCP, and other programmatic access may require an eligible Brewfather subscription and may be subject to additional fees or access tiers. We may introduce or change those fees on at least 30 days' notice to existing subscribers, consistent with Section 9 of the Brewfather Terms of Service. If you do not agree to a new fee, you may stop using the affected API Materials or cancel the affected subscription before the fee takes effect. You are responsible for all applicable taxes and for your own costs of developing and operating an Application. Mandatory consumer remedies are not affected.

## 14. Review, audit, and cooperation

We may review an Application, including by testing it and reviewing its tool descriptions, disclosures, and data flows, and may investigate suspected non-compliance. On reasonable request, you must give us accurate information and evidence reasonably necessary to verify your compliance, including about your Application's ownership, functionality, data flows, AI model providers, security controls, service providers, user disclosures, and deletion practices. You must cooperate promptly with a compliance inquiry and remedy identified violations within the period we specify, which for a consumer will be reasonable. We may require a written certification of compliance or deletion.

If you act in a business or professional capacity and we have reasonable grounds to suspect a material breach, we may, on at least 14 days' written notice, have an independent auditor bound by confidentiality check your compliance. From the notice, you must preserve the relevant records. An audit covers only relevant records, systems, and processes, takes place in normal business hours, and may happen at most once in 12 months unless an earlier audit found a material breach. The auditor may access personal data only to the extent necessary for the audit. You must cooperate with it, and pay the auditor's reasonable costs if it finds a material breach.

Review, audit, inaction, or approval of an Application does not waive these API Terms or make us responsible for the Application.

## 15. Ownership, Brewfather Materials, and branding

Warpkode AS and its licensors retain all rights in the API Materials, Brewfather Materials, the Brewfather Service, documentation, branding, and related intellectual property. These API Terms do not transfer ownership of a Brewfather User's User Content or of your Application to us.

Without claiming ownership of user-created content, and to the extent database rights exist, Warpkode AS holds them in the databases made available through the API Materials, based on its investment in obtaining, verifying, organising, and presenting their contents. Except to the extent mandatory law permits, you must not:

* extract or re-utilise all or a substantial part of such a database; or
* repeatedly and systematically extract or re-utilise insubstantial parts of it in a way that conflicts with normal use of the database or unreasonably harms our legitimate interests.

Warpkode AS expressly reserves all rights to reproduce and extract the API Materials, Brewfather Materials, and Brewfather databases for text and data mining, including to train, fine-tune, or evaluate an artificial-intelligence model. This reservation is made under Article 4(3) of Directive (EU) 2019/790 and any corresponding national law, as Section 11 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md) describes. These API Terms grant no licence for those purposes. The reservation does not cover the help documentation at docs.brewfather.app.

You may state accurately, in plain text, that your Application works with Brewfather. Without our prior written approval, you must not:

* use a Brewfather logo, icon, or trade dress;
* use "Brewfather" or a confusingly similar term in the name of an Application, MCP Server, tool, domain, account, or company; or
* suggest sponsorship, endorsement, or an official relationship, including by naming, describing, or presenting an Application, MCP Server, or tool in a way that suggests it is official or that Brewfather built, provides, sponsors, endorses, or is responsible for it.

We may require you to change or stop any use of our name or marks. Goodwill from any use belongs to Warpkode AS.

If you offer an Application to other people in a business or professional capacity, we may identify you and that Application by name and logo as an integration in documentation, integration directories, and marketing. You may ask us to stop future uses at any time, and we will remove listings within a reasonable time after your access ends.

Section 11 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md) applies to suggestions and feedback you give about the API Materials. That Section also preserves our freedom to develop, acquire, or offer features, integrations, MCP servers, or products similar to or competing with your Application.

## 16. Confidentiality

Non-public API Materials and documentation, credentials, partner and pricing terms, beta and preview features, security information, and any other information we identify as confidential or that you should reasonably understand to be confidential are our confidential information. You must use it only to perform these API Terms and protect it with at least reasonable care. You must disclose it only to personnel and service providers who need it for that purpose and are bound by confidentiality obligations at least as protective as these API Terms.

This Section does not apply to information that is or becomes public through no fault of yours, that you lawfully knew or received without a confidentiality obligation, or that you developed independently without using our confidential information. You may disclose confidential information where the law requires, after giving us notice where lawful. Nothing in these API Terms prevents you from reporting suspected unlawful conduct to a competent authority.

## 17. Third-party content and services

API Data may contain content owned by users or other third parties. You are responsible for obtaining any rights your use needs and for preserving required notices and attribution. We grant no rights to third-party content merely because it is available through the API Materials.

Your Application is independent of Brewfather. You alone are responsible for the Application, its users, support, legal notices, security, AI model providers, processing of personal data, claims, and compliance. We are not responsible for third-party services, including AI clients, MCP hosts, model providers, and integration platforms, or for their availability, acts, omissions, or data practices.

## 18. Enforcement and legal action

A violation of Section 10, unauthorised access, misuse of credentials or API Data, circumvention of technical controls, or failure to delete API Data is a material breach of these API Terms.

If we reasonably believe that the API Materials have been used in breach of these API Terms, whether by you, through your Application, or by another involved third party, we may, with or without prior notice where the law permits:

* investigate the conduct and preserve relevant usage and security records;
* restrict, suspend, or revoke API access, credentials, OAuth grants, Connected App approval, accounts, or related Brewfather services;
* block an Application, MCP Server, client, account, credential, domain, IP address, or other access path;
* require the conduct to stop, and require the return or permanent deletion of API Data and written certification of deletion;
* notify affected users, or relevant hosting, distribution, AI-platform, directory, or service providers, where we have a reasonable, good-faith basis and the notification is necessary and proportionate to protect Brewfather, users, or third parties; and
* report suspected unlawful conduct to competent regulators, law-enforcement authorities, or other authorities.

We may take legal action against the Developer and any responsible third-party developer, operator, distributor, or other participant in an unauthorised integration. To the fullest extent the law allows, remedies may include:

* cease-and-desist demands;
* interim or permanent injunctive relief or equivalent court orders;
* specific performance;
* deletion or return of API Data;
* damages;
* recovery of unjust enrichment; and
* recovery of reasonable enforcement costs where awarded.

A claim against a person who is not a party to these API Terms must rest on an independent legal basis, not on these API Terms alone. If you act in a business or professional capacity, you accept that a breach of Section 4, 7, 9, 10, 11, 12, 15, or 16 can cause us harm that damages alone cannot adequately remedy. This does not imply that damages adequately remedy a breach of any other Section.

Conduct that breaches these API Terms is contractually prohibited and unauthorised. For these API Terms, "unauthorised" means outside the contractual permission granted in Section 3. Depending on the facts and applicable law, such conduct may also breach civil or criminal law, such as laws on unauthorised system access, confidentiality, intellectual property, privacy and data protection, consumer protection, or unfair competition. These rights and remedies are cumulative and add to any other remedy the law provides.

## 19. Suspension, termination, and effect of termination

You may terminate these API Terms at any time by stopping all use of the API Materials, revoking your credentials and connections, and deleting all API Data in your possession or control, subject to lawful retention obligations.

We may restrict, suspend, or terminate access immediately if you:

* breach these API Terms;
* create a material security, legal, or operational risk;
* expose Brewfather or a user to a material risk of liability or harm; or
* fail to respond to a compliance inquiry.

Enforcement will be proportionate to the breach and risk where practicable, but we may immediately block access by or for a Competing Brewing Service, because it has no permission under these API Terms. We may also discontinue API Materials, or your access to them, on reasonable advance notice, for convenience or where continued access is no longer commercially or technically feasible.

For Own-Account Use by a consumer, Sections 12 and 13 of the Brewfather Terms of Service govern notice, proportionality, and refunds. If we terminate a paid consumer subscription for any reason other than your breach, fraud, or abuse, we will provide the refund that Section 13 of the Brewfather Terms of Service or mandatory law requires.

On suspension, termination, or discontinuation, you must immediately stop accessing the affected API Materials, stop representing that your Application integrates with Brewfather, and complete the deletion Section 9 requires. Section 4 (as to responsibility for past activity), Sections 7.4, 9 to 11, 14 to 18, and 20 to 25, and any other provision that by its nature should survive, survive termination. Sections 10 and 11 continue to apply to API Data you obtained, for as long as you keep or use it, and to any later access by you or on your behalf.

## 20. Your representations, warranties, and indemnity

You represent and warrant that:

* you have the legal capacity and authority to enter into these API Terms;
* your Application and use of the API Materials will comply with these API Terms and applicable law;
* you have all rights, permissions, notices, and legal bases your processing requires; and
* information you give us and users is accurate and not misleading.

If you act in a business or professional capacity, the following indemnity applies to the fullest extent permitted by law. You will indemnify, defend, and hold harmless Warpkode AS and its officers, directors, employees, agents, affiliates, licensors, and suppliers from third-party claims, proceedings, losses, liabilities, damages, judgments, penalties, costs, and reasonable legal fees arising from or relating to:

* your Application;
* actions taken by your Application or AI Agent;
* your use of the API Materials or API Data;
* your breach of these API Terms;
* your infringement or violation of another person's rights; or
* a Security Incident caused by your failure to comply with these API Terms.

The notice, defence, and settlement procedure in Section 16 of the [Brewfather Terms of Service](https://docs.brewfather.app/legal/tos.md) applies to these claims as if they were covered claims under that Section. If we take over the defence, you remain responsible under this Section 20. This indemnity does not apply to consumers or to the extent a claim was caused by our own unlawful conduct. A consumer remains responsible under applicable law for loss caused by their breach of these API Terms.

## 21. Disclaimers

If you act in a business or professional capacity, then to the fullest extent permitted by law, the API Materials and API Data are provided **"as is"** and **"as available"**. In that case, and to the fullest extent permitted by law, they are provided without warranties, representations, conditions, or guarantees of any kind, whether express, implied, or statutory. We do not warrant that the API Materials will be uninterrupted, secure, error-free, complete, accurate, compatible, or available for any particular period or purpose, or that an AI Agent, MCP client, or model provider will interpret API Data correctly.

If you are a consumer, Section 14 of the Brewfather Terms of Service applies instead of the first paragraph of this Section.

You are responsible for how you use the API Materials and for any reliance on API Data or on output produced from it. An Application must not rely on the API Materials as the sole control or safety mechanism for brewing equipment or any process where an error, delay, or outage could cause personal injury, property damage, contamination, or other material harm. Nothing in these API Terms excludes a warranty, remedy, or right that cannot lawfully be excluded.

## 22. Limitation of liability

Section 15 of the Brewfather Terms of Service, including the time limit for business claims in Section 15.5, applies to the API Materials and these API Terms. If you are a consumer, Section 15.4 of those Terms governs our liability to you, and the rest of this Section applies to you only to the extent consistent with it.

If you use the API Materials in a business or professional capacity, this paragraph applies to the fullest extent permitted by law. Warpkode AS and its officers, directors, employees, agents, affiliates, licensors, and suppliers will not be liable for indirect, incidental, special, exemplary, punitive, or consequential loss; loss of profits, revenue, goodwill, business opportunity, anticipated savings, or data; costs of substitute services; or interruption arising out of or relating to the API Materials, API Data, an Application, an AI Agent, or these API Terms, regardless of the theory of liability and even if advised of the possibility.

In that case, the total liability of Warpkode AS and the persons listed in the previous paragraph to you arising out of or relating to the API Materials, API Data, and these API Terms is capped. The cap applies to all events in any rolling 12-month period together. It is the greater of **EUR 100** and the amount you paid for the subscription that includes the relevant API access during the 12 months before the event giving rise to the claim. This cap is shared with, and not in addition to, the cap in Section 15.3 of the Brewfather Terms of Service.

Nothing in these API Terms limits liability that cannot lawfully be limited, including liability to the extent caused by fraud, wilful misconduct, gross negligence, or other conduct for which mandatory law prohibits a limitation. Mandatory consumer rights remain unaffected.

## 23. Export controls and sanctions

You represent that neither you nor any person who owns or controls you or operates your Application:

* is located in, organised under the laws of, or ordinarily resident in a country or region subject to comprehensive sanctions; or
* is listed on, or owned or controlled by a person listed on, a sanctions list maintained by Norway, the European Union, the United Kingdom, the United Nations, or the United States.

You must not access, use, export, or make available the API Materials or API Data in breach of export-control or sanctions law. We may suspend or terminate access immediately where needed to comply with those laws.

## 24. Changes to these API Terms

We may update these API Terms for legal, regulatory, security, technical, operational, or business reasons, and post the current version at this URL. We will give reasonable advance notice of a material adverse change when the law requires it or it is reasonably practicable, but a change needed to address law, security, abuse, or an urgent operational risk may take effect sooner. Changes to incorporated API documentation that materially reduce your rights or increase your obligations get the same notice, except changes to rate limits, quotas, endpoints, fields, tools, and other technical details, which Section 12 governs.

For a material change to an ongoing consumer contract, we will give the notice and termination rights the law requires and request affirmative acceptance where required. Otherwise, by continuing to access or use the API Materials after updated API Terms take effect, you agree to them where the law recognises that method after adequate notice. If you do not agree, you must stop using the API Materials before the updated API Terms take effect and complete the required deletion.

## 25. General

**Governing law and courts.** These API Terms are governed by the laws of Norway, without regard to conflict-of-law rules. The same applies to any dispute or claim arising out of or in connection with them, the API Materials, or API Data, including non-contractual disputes or claims. The courts of Norway have exclusive jurisdiction, except where mandatory law provides otherwise.

For a Developer acting in a business or professional capacity, the agreed venue is the district court for Warpkode AS's registered office when the proceedings start. Warpkode AS may also bring proceedings against such a Developer in the courts of the place where the Developer is domiciled when the proceedings start. A company or other legal person is domiciled where it has its statutory seat, central administration, or principal place of business. If that option is invalid in a particular case, the proceedings must be brought at the agreed venue, and the rest of this Section still applies. Either party may ask any competent court for urgent interim or protective measures.

If you are a consumer, this choice does not deprive you of mandatory protections under the law that would apply without the choice. If mandatory consumer-jurisdiction law permits you to sue in the courts where you live, you may do so, and we will bring proceedings against you only in a court permitted by that law.

**Events beyond our control.** We are not liable for a failure or delay caused by an event beyond our reasonable control. Such events include natural disaster, epidemic, war, terrorism, civil disorder, government action, labour dispute, cyberattack, or a failure of utilities, networks, hosting, or other third-party services we rely on. This does not affect a consumer's mandatory rights.

**Assignment and change of control.** You may not assign or transfer these API Terms, API access, Connected App approval, or credentials without our prior written consent. We may assign these API Terms to an affiliate or as part of a merger, reorganisation, financing, sale of assets, or transfer of the Brewfather business, provided consumer rights are not reduced contrary to law. You must tell us within 30 days if you, or the operator of your Application, undergo a change of control or come under the control of, or start operating for, a Competing Brewing Service. We may then end any Connected App approval, registration, partner arrangement, or other access beyond Own-Account Use with immediate effect.

**Subcontractors.** We may use subcontractors and other service providers to provide the API Materials, perform our obligations, and exercise our rights under these API Terms.

**Set-off.** If you act in a business or professional capacity, then to the extent the law permits, we may set off amounts you owe us under these API Terms against amounts we owe you. If you act in a business or professional capacity, then to the extent the law permits, you must also pay us in full, without set-off or deduction.

**Severability.** If a provision is held unenforceable, the remaining provisions remain in effect. For a Developer acting in a business or professional capacity, the provision will be enforced to the maximum lawful extent. A term that is unfair to a consumer does not bind the consumer and will not be rewritten to make it enforceable.

**Interpretation.** Words such as "including" and "for example" introduce examples and do not limit the words before them. A reference to a law includes that law as amended or replaced. The summary at the top of these API Terms and the headings are for convenience only and do not affect their meaning. If we provide a translation, the English version controls to the extent the law permits.

**Waiver and relationship.** A failure or delay in exercising a right is not a waiver. These API Terms do not create a partnership, joint venture, agency, or employment relationship.

**Entire agreement.** These API Terms, the incorporated terms, the API documentation, and any applicable additional written terms are the entire agreement concerning your use of the API Materials and replace prior discussions or understandings about that subject. A waiver or individually negotiated amendment must be in writing by an authorised Warpkode AS representative. If you act in a business or professional capacity, you have not relied on any statement, promise, or representation that is not set out in these documents, and you have no remedy for one, except for fraud.

**Third parties.** Only you and Warpkode AS may enforce these API Terms, except that the officers, directors, employees, agents, affiliates, licensors, and suppliers that Sections 20 and 22 protect may rely on those Sections to the extent the law permits.

**Notices.** We may give you notices by email to the address associated with your account or Application, in the Service, or, for notices to all Developers, in the API documentation. Questions, requests for written authorisation, security notices, and legal notices about these API Terms may be sent to <hello@brewfather.app>.

**Warpkode AS** (Norwegian private limited company, *aksjeselskap*)\
Registered in the Register of Business Enterprises (*Foretaksregisteret*)\
Organisation no. 921 463 146 MVA\
Head office: Florø, Norway

Brewfather © Warpkode AS\
Revision: 20261019


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brewfather.app/legal/api-terms-of-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
