API License Agreement
1. Grant of License
Subject to your compliance with this Agreement, the Foodashi Terms of Service, and payment of applicable fees, Foodashi ("Foodashi", "we", "our") grants you ("Developer", "you") a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to access and use the Foodashi API to develop, test, and operate your application, website, device, or service ("Developer App").
Your Developer App can be almost any kind of product. Consumer and business apps, websites, meal planners, grocery and shopping list tools, recipe and cooking apps, fitness and wellness apps, smart kitchen devices, chatbots and assistants are all welcome, including products that compete with other food or meal-planning apps. What this license protects is the Foodashi catalogue itself: you may use and show the data returned by the API ("Foodashi Data") inside your product, but you may not turn it into a data product of your own (see Sections 2 and 15).
This license does not convey ownership of the API, its infrastructure, algorithms, or any intellectual property. All rights not expressly granted are reserved by Foodashi.
2. Usage Restrictions
You agree NOT to:
- Sell, resell, rent, lease, or sublicense raw API responses, recipe JSON, or any structured data returned by the API as data, whether as files, feeds, exports, or through an API of your own.
- Use the API or Foodashi Data to build, supply, or enrich a recipe, nutrition, ingredient, or food database, dataset, or API that makes Foodashi Data, or a substitute derived from it, available to third parties. Showing Foodashi Data to the end users of your own Developer App is not restricted by this clause.
- Mirror, index, or store API outputs in a manner that bypasses usage limits or creates a redistributable derivative database. (Caching and storing the specific data your Developer App fetches and uses, in your own database, for your own application, is expressly permitted within the refresh window in Section 15.)
- Use API outputs as the sole basis for decisions where an error could cause serious harm and no qualified professional is involved, such as clinical or medical nutrition, infant feeding, allergen control in food businesses, or mandatory food labels (see the Acceptable Use Policy). Consumer recipe, meal-planning, cooking, and grocery apps that keep the safeguards in Section 3 are not restricted by this clause.
- Reverse-engineer, decompile, disassemble, or otherwise attempt to derive the source code, algorithms, prompts, or system architecture of the API.
- Share, publish, or expose API keys in client-side code, public repositories, forums, or any publicly accessible location.
- Use the API for any purpose that violates the Acceptable Use Policy.
- Exceed the rate limits, request quotas, or other usage restrictions of your subscription tier.
- Circumvent or attempt to circumvent any rate limiting, authentication, or security measures.
3. Food, Nutrition & Allergen Safeguards
Recipes and recipe images are generated by artificial intelligence. Nutrition figures are calculated from food composition data and, where no measured value exists, from estimates. Allergen and dietary indicators are derived automatically. All of it is provided "as is" for information. Foodashi does not guarantee that it is accurate, complete, or suitable for any particular purpose, including food preparation, consumption, labeling, or regulatory compliance.
You do not need a human to review each recipe before your Developer App shows it. Automated display is permitted when your Developer App keeps these safeguards in place:
- AI transparency: Keep the machine-readable AI markers we provide (the
ai_generatedflag and the metadata in our images) and make it clear to your end users that recipes and recipe images are AI-generated. A label or a notice in your app is enough. - Estimates: Present nutrition figures as estimates, not as measured, tested, or certified values.
- Allergens: Present allergen and dietary information as indicative, remind your users to check ingredients and product labels themselves, and do not describe a recipe as allergen-free, allergy-safe, or safe for a medical condition on the basis of Foodashi Data alone.
- No medical claims: Do not present API outputs as medical advice, dietary prescriptions, or clinical nutrition guidance, and do not market your Developer App as a substitute for professional medical, nutritional, or dietary advice.
- Error reporting: Give your end users a way to tell you when content looks wrong, and stop showing content you know to be wrong. You are welcome to pass reports on to us at support@foodashi.com so we can correct the source.
- Laws that apply to your app: Comply with the consumer protection, advertising, food information, and AI transparency laws that apply where your Developer App is offered. If you use Foodashi Data in food labels, menus for sale, or other regulated food information, you must verify it independently first.
Some higher-risk uses need more than these safeguards. The Acceptable Use Policy sets out when a qualified professional must review content first, for example clinical nutrition, infant feeding, allergen control in food businesses, and printed or editorial publications presented as tested.
You decide how your Developer App uses and presents Foodashi Data, and you are responsible for that decision and for the statements you make to your end users. Section 11 explains the limits of Foodashi's liability.
4. AI-Generated Content & Accuracy Disclaimer
Content returned by the Foodashi API, including recipes, ingredient lists, cooking instructions, food descriptions, and food imagery, is generated or augmented by artificial intelligence systems. Nutrition and allergen data are derived from that content by automated processes and may include AI estimates.
You acknowledge that AI-generated content may:
- Contain inaccurate, incomplete, misleading, or entirely fabricated information ("hallucinations").
- Include incorrect ingredients, unsafe food combinations, or dangerous preparation methods.
- Omit critical allergens or food safety information.
- Provide incorrect nutritional values, caloric counts, or macronutrient breakdowns.
- Suggest cooking temperatures or times that are unsafe for certain foods.
- Produce content that inadvertently resembles existing copyrighted recipes or food content.
Foodashi does not warrant the accuracy, safety, originality, or fitness for any particular purpose of AI-generated outputs. The safeguards in Section 3 are how you manage these risks in your Developer App.
5. Availability & Quality Disclaimer
Foodashi targets high availability but does not guarantee uptime, uninterrupted service, or specific response times. The API is provided "as available" and may experience downtime for maintenance, upgrades, infrastructure failures, or causes beyond our reasonable control.
Content quality, taste, authenticity, cultural appropriateness, and culinary merit are subjective and not warranted. Descriptive terms such as "chef-grade," "authentic," "gourmet," or "professional" are marketing expressions and do not constitute guarantees.
Foodashi may modify, deprecate, or remove API endpoints, response fields, or features at any time. We will endeavour to provide at least 60 days' notice before removing or making breaking changes to existing endpoints.
Nothing in this section affects your statutory conformity rights as a consumer under Directive (EU) 2019/770 (Digital Content Directive) or applicable national law implementing it.
6. Branding, Data Credits & AI Disclosure
Hobby plan: a "Powered by Foodashi" credit is required. While you use the Hobby plan, your Developer App must show a visible "Powered by Foodashi" credit, linking to https://foodashi.com, wherever it displays Foodashi Data. The credit must be readable and placed next to the data or on the same page or screen (for example in its footer), not only behind a menu or on a separate screen. A text link is enough; the API documentation provides a snippet you may copy.
Paid plans: no Foodashi branding is required. On the Indie, Pro, and Enterprise plans you do not need to display a "Powered by Foodashi" credit, badge, logo, or backlink. You may present Foodashi Data under your own brand.
Third-party data credits are required. Parts of Foodashi Data come from open databases whose licences require the source to be credited. If your Developer App displays nutrition, ingredient, or barcode product data, you must include, somewhere your users can find it (for example an About, Credits, or Legal screen), either a link to foodashi.com/data-sources or the attribution statements listed on that page. This credit does not need to mention Foodashi.
Open Food Facts data. Parts of Foodashi Data, including barcode product data and some ingredient nutrition values, come from Open Food Facts under the Open Database License (ODbL). Your credits must include this notice: "Contains information from Open Food Facts, which is made available here under the Open Database License (ODbL)." Where you display barcode product data, show the notice next to that data. Nothing in this Agreement restricts the rights the ODbL gives you in Open Food Facts data.
AI disclosure. The AI transparency safeguard in Section 3 applies on every plan. Do not represent AI-generated content as human-authored, professionally tested, or editorially reviewed unless it has actually been reviewed.
7. Intellectual Property
The Foodashi platform, API infrastructure, documentation, branding, trade names, logos, and proprietary algorithms are owned by Foodashi. Nothing in this Agreement transfers ownership of Foodashi's intellectual property to you.
AI-generated recipes, text, and imagery returned by the API may not be eligible for copyright protection under applicable law. Foodashi does not claim copyright ownership over AI-generated outputs and makes no representation regarding the intellectual property status of such content. The Foodashi catalogue as a whole, including its structure and the data we have obtained, verified, and presented, is protected as a database where the law provides such protection.
You are responsible for conducting appropriate intellectual property due diligence before publishing or commercialising content obtained through the API.
8. Data Handling & Privacy
You agree to comply with all applicable data protection and privacy laws (including GDPR, CCPA/CPRA, UK Data Protection Act 2018, and equivalent legislation) in connection with your use of the API and your Developer App.
- You must not transmit personally identifiable information (PII) of your end users to the Foodashi API unless expressly permitted and covered by our Data Processing Agreement.
- You must maintain an appropriate privacy policy for your Developer App that accurately describes how data is collected, processed, and shared, including the use of third-party APIs.
- You are responsible for obtaining all necessary consents from your end users for data processing activities related to your Developer App.
9. Rate Limits & Fair Use
API access is subject to the rate limits and request quotas of your subscription tier. Requests exceeding your
plan's limits will receive a 429 Too Many Requests response.
Foodashi reserves the right to throttle, suspend, or terminate access for any account that engages in excessive, abusive, or anomalous usage patterns, even if within stated rate limits, in order to protect platform stability and other users.
10. Indemnification
You agree to indemnify, defend, and hold harmless Foodashi, its officers, directors, employees, contractors, and agents from and against any and all claims by third parties, and the resulting damages, losses, liabilities, costs, and expenses (including reasonable legal fees), arising out of or relating to:
- Your Developer App or its use by end users.
- Your failure to maintain the safeguards required by Section 3.
- Any allergic reaction, adverse health event, food poisoning, or injury claimed by your end users or other third parties to result from the way your Developer App used or presented data obtained through the API.
- Your failure to comply with applicable food information, consumer protection, advertising, data privacy, or AI transparency laws in any jurisdiction where you or your end users operate.
- Any intellectual property infringement claim arising from your use or distribution of AI-generated content.
- Your violation of this Agreement, the Terms of Service, or any applicable law or regulation.
This obligation does not apply to the extent a claim results from Foodashi's own intentional breach, and it does not apply to consumers where mandatory consumer protection law prohibits it.
11. Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:
- Foodashi shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to damages for loss of profits, revenue, data, business opportunities, goodwill, or anticipated savings.
- Foodashi's total aggregate liability arising out of or related to this Agreement shall not exceed the total fees paid by you in the twelve (12) months preceding the event giving rise to the claim, or one hundred US dollars ($100), whichever is greater. This Agreement governs professional and business use of the API. Where you are acting as a consumer, the consumer liability terms in our Terms of Service apply instead of this limitation, and the $100 floor does not apply to you.
- Subject to the paragraph below, Foodashi is not liable for losses arising from how you or your end users use or rely on Foodashi Data, including decisions about food preparation, consumption, allergens, or diet.
Nothing in this Agreement limits or excludes liability for: (a) intentional breach of contract; (b) damage to human life, physical integrity, or health caused by a breach of contract, which under Section 6:152 of the Hungarian Civil Code cannot be excluded or limited; (c) death or personal injury caused by negligence; (d) fraud or fraudulent misrepresentation; or (e) any other liability that cannot be limited or excluded under applicable mandatory law.
12. Termination
Foodashi will provide at least 30 days' written notice before terminating API access without cause for users on a paid plan. Foodashi may suspend or terminate your API access immediately if you breach this Agreement, the Terms of Service, or the Acceptable Use Policy. You may terminate by cancelling your subscription via the Developer Console.
Upon termination: (a) your API keys will be deactivated; (b) your license to use the API is immediately revoked; (c) you must stop using Foodashi Data in your Developer App within thirty (30) days; and (d) you must delete cached Foodashi Data within thirty (30) days. Data you received under an open licence, such as Open Food Facts data under the ODbL, remains available to you under that licence.
Sections 3, 4, 7, 10, 11, 13, and the restrictions in Section 15 survive termination of this Agreement.
13. Force Majeure
Neither party shall be liable for any failure or delay in performing its obligations under this Agreement where such failure or delay results from circumstances beyond the reasonable control of that party, including but not limited to: natural disasters, pandemics, government actions, war, terrorism, riots, embargoes, acts of civil or military authority, fire, floods, earthquakes, nuclear incidents, internet or telecommunications failures, cyberattacks, power outages, failures or delays by cloud infrastructure providers (including Cloudflare, Supabase, and Stripe), failures or changes in third-party AI model providers (including Google Gemini and DeepInfra), or changes in applicable law or regulation.
If a force majeure event continues for more than sixty (60) consecutive days, either party may terminate this Agreement by providing written notice to the other party, without liability for such termination.
14. General Provisions
- Entire Agreement: This Agreement, together with the Terms of Service, Privacy Policy, Refund Policy, and Acceptable Use Policy, constitutes the entire agreement between you and Foodashi regarding your use of the API. A separate written agreement signed by Foodashi (for example an Enterprise agreement) prevails over this Agreement where it says so.
- Governing Law: This Agreement is governed by the laws of Hungary. Disputes shall be submitted to the exclusive jurisdiction of the courts of Budapest, Hungary. Consumers keep the rights described in the Regional Terms (Section 15A of the Terms of Service), including the right of EU consumers to bring proceedings in their country of residence. Hungarian consumers may also contact the Budapest Conciliation Board (Budapesti Békéltető Testület).
- Severability: If any provision is found unenforceable, the remaining provisions continue in full force and effect.
- Amendments: Foodashi may update this Agreement. We will provide at least 30 days' advance notice of material changes via email or Developer Console notification. If you do not agree to the revised terms, you may terminate your account before the changes take effect. Your continued use of the API after the effective date constitutes acceptance.
- Contact: For questions about this Agreement, contact admin@foodashi.com
15. Data Use, Caching, and Anti-Extraction
This section explains, in plain language, what you may and may not do with the recipe, ingredient, nutrition, and image data returned by the Foodashi API ("Foodashi Data"). Where this section conflicts with an earlier restriction in this Agreement, this section controls.
What you may do
On any active plan, and within your plan's quota and permitted use (commercial use requires a paid plan), you may:
- Call the API and use Foodashi Data inside your own Developer App, whatever kind of product it is.
- Cache and store the specific data that your app fetches and uses, in your own database, subject to the refresh window below.
- Show that data to your own end users as part of your app, including in plans, lists, search results, and recommendations your app builds from it.
- Use software, including AI models running inside your own app, to process the data you fetch for your users, for example to scale a recipe or build a shopping list.
- Do all of the above under your own brand. On paid plans no Foodashi branding is required; on the Hobby plan the "Powered by Foodashi" credit in Section 6 is required. The third-party data credits in Section 6 apply on every plan.
This is a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to use the data inside your app. It is not a sale or transfer of the data or the catalogue.
Cache refresh window
We correct recipes when we find or are told about an error, including allergen and dietary information. So that those corrections reach your end users, you may cache Foodashi recipe data (a recipe and the ingredient, nutrition, allergen, and dietary information that comes with it) for up to thirty (30) days from the time your app fetched it. Before your Developer App shows cached recipe data that is older than thirty (30) days, it must fetch that data again from the API and replace the cached copy. You do not need to re-fetch or delete data your Developer App no longer shows. Re-fetching within this window is ordinary use of the API and counts toward your plan's quota as usual.
What you may not do
You may NOT:
- Systematically download, crawl, enumerate, scrape, or otherwise extract the Foodashi catalogue in whole or in substantial part beyond what your app genuinely needs to serve its own users. Mirroring the catalogue, sweeping recipe IDs, or paginating through the whole dataset is prohibited even if it fits within your quota.
- Republish, redistribute, syndicate, sell, or sublicense the data, or any substantial portion of the catalogue, as data to anyone other than your own app's end users.
- Use the data to build, supply, or train a dataset, API, or AI model that offers Foodashi Data, or a substitute for it, to others.
- Share or resell your API key.
Foodashi retains all intellectual-property rights in the catalogue, including any database rights. These restrictions do not limit rights you have under an open licence for third-party data (see Section 6). Violation of this section may result in suspension or termination of your access, and Foodashi reserves all legal remedies available to it.
Provider Details (Impresszum)
Business registration in progress. Foodashi is operated from Budapest,
Hungary and is in the process of being registered as an egyéni vállalkozó
(Hungarian sole proprietorship). Full statutory provider details — registered name,
seat address, registration number and tax number — will be published here as soon
as registration completes, and before any paid service is offered.
Until then you can reach us at
admin@foodashi.com
for any legal, contractual or data protection matter.