Lyren Terms of Service
These Terms govern your use of Lyren API, the developer dashboard, billing flow, API keys, and public developer features, including Chat, Tools, Memory, Knowledge Base, Workflows, Scheduler jobs, Calendar-ready flows where enabled, Connectors, and Business insights. By using Lyren API, you agree to these Terms.
1. The Service
Lyren API is a developer-facing AI platform provided by EASEFY LLC. The Service may include:
- Developer API: public API endpoints that customers call from their backend using an API key.
- Chat: endpoints for building AI chat assistants and conversational features.
- Tools: utility endpoints such as summarize, translate, rewrite, extract, fetch, and fetch plus summarize.
- Memory: saving, searching, deleting, and retrieving user-scoped memory items where enabled by plan.
-
Knowledge Base: uploading files through routes such as
/v1/knowledge/uploadand asking document-based questions through routes such as/v1/knowledge/askwhere enabled by plan. - Workflows: saving and listing reusable workflow definitions where enabled by plan.
- Scheduler: creating, listing, and canceling scheduled jobs such as reminders, follow-ups, webhook calls, and optional email jobs where enabled by plan.
- Calendar-ready flows: booking or availability-related flows where calendar features are enabled in the applicable deployment.
- Connectors: source configuration features such as sitemap, RSS, URL list, and webhook-style configuration where enabled by plan.
- Business insights: structured business endpoints such as lead scoring, churn risk, and revenue leak analysis where enabled by plan.
- Developer portal: account, login, API key, dashboard, billing, and subscription management features.
Features may vary by plan, account status, technical availability, deployment configuration, and usage limits. We may add, change, restrict, or remove features over time.
Lyren Chat, Lyren Meet, Lyren Agent, and internal code tools are separate product features unless they are specifically offered through Lyren API.
2. Accounts, API Keys, and Access
- You are responsible for keeping your account credentials and API keys secure.
- Do not share API keys publicly, commit them to public repositories, expose them in frontend browser code, or include them in screenshots.
- Rotate API keys immediately if you suspect misuse, leakage, or unauthorized access.
- You must provide accurate account information and keep it updated.
- You are responsible for all activity that occurs under your account, API keys, users, integrations, or systems.
- We may suspend, limit, or revoke access if we believe an account or API key is compromised, misused, unpaid, or creating risk.
3. Plans, Limits, and Quotas
Lyren API plans may include feature access rules, monthly quotas, daily caps, rate limits, plan-based restrictions, and other usage controls. Limits may apply to Chat, Tools, Memory, Knowledge Base, Workflows, Scheduler, Calendar, Connectors, Business insights, and other modules.
- You are responsible for staying within the limits of your plan.
- We may reject, throttle, delay, block, or rate-limit requests that exceed usage limits or create operational risk.
- Plan features and limits may change over time with reasonable notice where required by law.
- Unlimited or high-limit language means subject to technical, abuse-prevention, security, fair-use, and infrastructure limits.
4. Acceptable Use
- Do not attempt to bypass security controls, authentication, authorization, rate limits, quotas, billing checks, or access restrictions.
- Do not upload malware, harmful payloads, malicious code, or content intended to compromise systems, networks, accounts, or users.
- Do not use the Service for abuse, fraud, illegal activity, harassment, spam, deception, rights violations, or platform disruption.
- Do not use the Service to generate, distribute, or support harmful instructions, credential theft, cyber abuse, weapons misuse, self-harm facilitation, or other unlawful activity.
- Do not disrupt, overload, scrape, reverse engineer, attack, or interfere with the Service or its infrastructure.
- Do not resell, sublicense, or provide access to the Service in a way that violates these Terms or bypasses plan limits.
- Avoid submitting highly sensitive secrets, raw private keys, passwords, full payment card numbers, or regulated data unless you have confirmed that your intended use is appropriate and permitted.
5. Customer Content
You retain ownership of content you submit to the Service, including prompts, messages, uploaded files, extracted text, memory items, workflow definitions, scheduler payloads, connector configurations, business endpoint inputs, and other submitted data (“Customer Content”).
You grant Lyren API permission to process Customer Content as needed to provide, secure, maintain, debug, support, and improve the Service, including generating outputs, running tools, retrieving memory, answering from knowledge content, running scheduled jobs, storing configurations, and enforcing limits.
- You are responsible for ensuring you have the rights to upload, submit, process, and use Customer Content.
- You are responsible for providing notices and obtaining permissions or consents from your own end users where required.
- You are responsible for reviewing outputs before using them in production, publishing, customer communications, or business decisions.
- Where deletion controls are available, you may remove certain content using available product, dashboard, API, or support channels.
6. User-Scoped Features
Some features are designed to be scoped by a customer-provided identifier such as x-user-id.
These may include Memory, Knowledge Base, Workflows, Scheduler jobs, Calendar-ready flows, Connectors, and Business insights.
- You are responsible for choosing stable, appropriate, and lawful user identifiers.
- Lyren does not create or verify the real-world identity behind a customer-provided
x-user-id. - You are responsible for preventing one end user from accessing another end user’s data through your own application.
- You are responsible for handling end-user access, deletion, correction, or privacy requests in your own product where required.
7. Workflows, Scheduler Jobs, and Calendar-ready Flows
The Service may allow you to save workflow definitions and schedule jobs such as reminders, follow-ups, webhook calls, optional email jobs, and calendar-ready scheduling actions where enabled.
- No guarantee of delivery: scheduler jobs, reminders, notifications, webhook calls, follow-ups, and calendar-ready flows may be delayed, blocked, throttled, duplicated, fail, or be unavailable.
- Customer responsibility: you are responsible for verifying bookings, confirmations, scheduled actions, webhook results, and business outcomes.
- No critical reliance: do not rely solely on Workflows, Scheduler, or Calendar-ready flows for emergencies, critical deadlines, medical matters, legal obligations, financial obligations, safety-critical decisions, or other high-risk use.
- Third-party dependencies: integrations may depend on external systems such as email providers, calendar providers, webhooks, CRMs, hosting providers, or network services. Their outages, policies, and limits may affect results.
8. Connectors and External Sources
Connector features may let you store source configurations such as sitemap URLs, RSS URLs, URL lists, webhook configuration, or similar source metadata.
- You are responsible for ensuring you have permission to access, process, index, or use any source you configure.
- External content may be unavailable, inaccurate, incomplete, outdated, blocked, rate-limited, or changed by the source owner.
- Connector availability, ingestion behavior, and sync behavior may vary by plan, configuration, and deployment.
9. Business Insights
Business endpoints may provide structured outputs such as lead scores, churn risk estimates, revenue leak analysis, drivers, recommendations, or summaries.
- Business outputs are informational and may be inaccurate, incomplete, outdated, or unsuitable for your exact circumstances.
- You are responsible for verifying business outputs before making sales, financial, operational, staffing, customer, or strategy decisions.
- Business insights are not financial, legal, tax, accounting, investment, or professional advice.
10. Billing
Paid plans, prices, usage caps, billing periods, and billing terms are shown at purchase, checkout, or in your account. Payments may be processed by third-party payment providers such as Stripe. Taxes may apply depending on your location.
- Failure to pay may result in suspension, downgrade, limitation, or termination of access.
- If your plan includes usage limits, you are responsible for staying within those limits.
- We may change pricing, packaging, or plan limits with reasonable notice where required by law.
- Subscription access may depend on successful payment, subscription status, fraud checks, and account standing.
- Billing disputes must be raised promptly so we can review them.
11. Availability and Changes
The Service is provided on an “as is” and “as available” basis. We may modify, suspend, restrict, or discontinue any part of the Service for operational, security, legal, billing, abuse-prevention, infrastructure, or product reasons.
- Uptime is not guaranteed unless a separate written agreement says otherwise.
- Maintenance, outages, latency, failed requests, degraded performance, or feature changes may occur.
- We may update routes, response formats, models, quotas, feature availability, and documentation over time.
12. AI Outputs, Source References, and Disclaimers
AI outputs may be inaccurate, incomplete, outdated, offensive, biased, or misleading. Source references, citations, or links may be provided when available, but they do not guarantee accuracy, completeness, or suitability.
- You are responsible for verifying outputs before relying on them.
- You are responsible for testing outputs before using them in production systems or customer-facing workflows.
- Do not rely on the Service for legal, medical, financial, tax, safety-critical, emergency, or other professional advice.
- You are responsible for how you display, distribute, store, and act on outputs in your own product.
13. Data Retention, Security, and Logs
We process and store data to operate the Service, including account data, API key metadata, request logs, billing records, usage records, operational telemetry, memory content, knowledge content, workflow data, scheduler data, connector configuration, and business endpoint inputs where applicable.
- Retention periods may vary depending on data type, feature, legal requirements, billing needs, security needs, and operational needs.
- We may retain limited information as needed for security, abuse prevention, compliance, billing, dispute resolution, and support.
- We may remove, restrict, or preserve content or accounts that violate these Terms or create risk to Lyren, customers, users, or third parties.
- You should not submit secrets or sensitive regulated data unless you have appropriate safeguards and legal authority.
14. Suspension and Termination
You may stop using the Service at any time. We may suspend, limit, or terminate access if:
- you violate these Terms;
- your account is unpaid, past due, disputed, or suspected of fraud;
- your API keys are exposed, compromised, or misused;
- your usage creates risk, harm, abuse, excessive load, legal concern, or security concern;
- we are required to do so by law, payment provider, infrastructure provider, or security process.
Termination may result in loss of access to the Service, API keys, account features, stored content, or customer data, subject to applicable retention and deletion rules.
15. Limitation of Liability
To the maximum extent permitted by law, Lyren API and EASEFY LLC are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or any loss of profits, revenue, data, business opportunities, goodwill, customer relationships, production availability, or expected savings arising from your use of the Service.
To the maximum extent permitted by law, our total liability for any claim related to the Service will not exceed the amount you paid to Lyren API for the Service during the three months before the event giving rise to the claim, unless a different limit is required by applicable law.
16. Indemnity
To the maximum extent permitted by law, you agree to defend, indemnify, and hold harmless EASEFY LLC, Lyren API, and their owners, employees, contractors, service providers, and affiliates from claims, damages, liabilities, losses, and expenses arising from your use of the Service, Customer Content, end-user data, API integrations, violation of these Terms, or violation of laws or third-party rights.
17. Changes to These Terms
We may update these Terms from time to time. When we make changes, we may update the “Last updated” date above. Continued use of the Service after changes become effective means you accept the updated Terms.
18. Contact
Questions about these Terms: lyrenapi@gmail.com
Frequently Asked Questions
What do these Terms of Service cover?
These Terms govern use of Lyren API, including developer accounts, API keys, chat, tools, memory, knowledge base, workflows, scheduler jobs, calendar-ready flows, connectors, business insights, billing, acceptable use, AI outputs, limits, security, liability, and termination.
Is Lyren API the same as Lyren Chat?
No. Lyren API is the public developer API. Lyren Chat, Meet, Agent, and internal code tools are separate product features and are not part of these public developer API terms unless specifically offered through Lyren API.
What features may be included in Lyren API?
Lyren API may include Chat, Tools, Memory, Knowledge Base, Workflows, Scheduler jobs, Calendar-ready flows where enabled, Connectors, Business insights, API key management, dashboard access, and billing features.
Am I responsible for my account and API keys?
Yes. You are responsible for keeping your account credentials and API keys secure and for all activity under your account, API keys, users, systems, or integrations.
Can I share my API key publicly?
No. API keys should not be shared publicly, embedded in frontend code, committed to public repositories, or exposed in screenshots. Exposed keys should be rotated immediately.
What kinds of use are not allowed?
You may not bypass security controls, upload malware, abuse the Service, commit fraud, violate rights, disrupt infrastructure, or use Lyren API for unlawful activity.
Do I keep ownership of my content?
Yes. You retain ownership of prompts, uploaded files, memory items, workflow definitions, scheduler payloads, connector configurations, business inputs, and other submitted data, while granting Lyren permission to process them as needed to provide the Service.
Are scheduler jobs, reminders, and calendar-ready flows guaranteed?
No. Scheduler jobs, reminders, webhook calls, follow-ups, and calendar-ready flows may be delayed, blocked, throttled, duplicated, fail, or be unavailable because of third-party systems, network conditions, operational limits, or feature availability.
What happens if I do not pay for a paid plan?
Failure to pay may result in suspension, downgrade, limitation, or termination of access to Lyren API.
Can Lyren change or discontinue parts of the Service?
Yes. Lyren may modify, suspend, restrict, or discontinue parts of the Service for operational, security, legal, billing, abuse-prevention, infrastructure, or product reasons.
Can I rely on AI outputs without checking them?
No. AI outputs and source references when available may be inaccurate, incomplete, outdated, offensive, biased, or misleading. You are responsible for verifying outputs before relying on them.