New release: 0.3.0 for Rhea: Latent Loom – self hosted LLM service

Rhea Embeddable Client
descriptionStandard

This update 0.3.0 introduces bi-directional function calling (client and server-side) tool calling:

  • Additions to schemas.
  • Refinements to endpoint: /v1/responses
    • Adds parameters for tool/function calling.
    • Tool calling supported on client and server side.
Continue reading

Unweaving the cloud: Local LLMs and Private RAG with Rhea: Latent Loom

Rhea: Latent Loom part of the Rhea Generative Framework
descriptionStandard

Data privacy and mounting cloud costs are driving a shift toward localised AI. Enterprises want the power of Large Language Models (LLMs), but they cannot afford to send sensitive files over public networks.

Here’s where the Rhea: Latent Loom project comes in to play, a self-hosted LLM service designed to keep your data local, secure, and instantly searchable.

Continue reading

New release: 0.2.5 for Rhea: Latent Loom – self hosted LLM service

Rhea Embeddable Client
descriptionStandard

Following on our release for the Rhea: Latent Loom project this update 0.2.5 introduces:

  • Merges ingestion endpoints in to a single endpoint.
  • Additions to schemas.
  • New endpoint: /v1/rag/synthetic for generating synthetic questions used during knowledge ingestion.
  • Refinements to: /v1/search allowing vector distance threshold customisations.
Continue reading

New release Rhea: Latent Loom – self hosted LLM service

Rhea Embeddable Client
descriptionStandard

Announcing the Rhea: Latent Loom project a locally hosted LLM services that can be ran independently or with the Rhea Generative Framework. This post introduces the Rhea: Latent Loom API specification in OpenAPI (3.0.1) format. A Swagger UI Bundle is used to explore the API.

Rhea: Latent Loom can serve as drop-in replacement for AI cloud providers. Request responses are compatible with Chat Completion and Responses object types.

Continue reading

Rhea Generative Client – Terms & Conditions

descriptionStandard

Disclaimer

The software provided in this project is offered ‘AS IS‘ without any representations or warranties, express or implied. The Developer makes no claims or promises about the quality, accuracy, reliability, or any other characteristic of this software. To the maximum extent permitted by applicable law, the Developer explicitly disclaims all warranties, whether expressed, implied, or statutory, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. The Developer does not warrant that the software will meet your requirements, operate without interruption, achieve any intended result, be compatible or work with any other software, systems, or services, or be secure, accurate, complete, free of harmful code, or error-free. You assume all risks associated with the use of this software.

Commercial Exception

The disclaimer above applies to the free, publicly available version of this software. For clients with a paid commercial agreement, different terms and conditions may apply as specified in their individual contracts. If you have a paid agreement with us, please refer to that agreement for details on warranties, support, and other terms that may supersede or modify the above disclaimer

Source code license

Rhea Generative Client has been released under a Apache License 2.0

Preview: AI powered live chat agents using the Rhea Generative Framework + Embeddable client

Rhea Embeddable Client
descriptionStandard

We are proud to announce our AI powered live chat agents. Using the Rhea Generative Framework with our Rhea Embeddable module, you can embed AI powered live chat services directly on your website.

Continue reading

Beyond Customer Support: Discover the Potential of Rhea’s Enquiry Handling Use Cases

descriptionStandard

Rhea has a wide variety of applications and understanding the many use cases can be a challenge. We have prepared a selection of examples and use cases that highlight how Rhea’s functionality could be utilised; keep in mind that the scenarios themselves are conceptual.

Continue reading