Developing a Spring AI Enhanced Restaurant Booking System Employing an API-first Approach

Created By

pacphia year ago

This multi-module project hosts a client code-generated from an OpenAPI derivative of the ResOs API combined with a Spring AI implementation. It also includes an MCP server, MCP client configuration for use with Claude and a standalone ReactJS powered chatbot UI.

# java

# openapi

Overview Content Tools Comments

Overview

What is Spring AI ResOs?

Spring AI ResOs is a multi-module project that enhances restaurant booking systems using an API-first approach, integrating a client generated from an OpenAPI derivative of the ResOs API with a Spring AI implementation.

How to use Spring AI ResOs?

To use Spring AI ResOs, clone the repository from GitHub, build the project using Maven, and run the backend server. You can then interact with the system through a ReactJS powered chatbot UI or integrate it with various LLM providers.

Key features of Spring AI ResOs?

API-first design for restaurant booking
Integration with multiple LLM providers
Standalone chatbot UI for user interaction
Support for various configurations and dependencies

Use cases of Spring AI ResOs?

Conversing with a chatbot to search for restaurants and make reservations.
Integrating with LLM providers for enhanced user interaction.
Building custom applications that leverage the ResOs API for restaurant management.

FAQ from Spring AI ResOs?

Can I use Spring AI ResOs without an API key?

Yes, but an API key is required if you intend to register as a restaurateur or access certain features.

Is there a specific Java version required?

Yes, Java SDK 21 or better is required to run the project.

How can I contribute to the project?

You can contribute by forking the repository, making changes, and submitting a pull request.

Project Info

Created At

a year ago

Updated At

a year ago

Author Name

pacphi

Star

Language

Java

License

Apache-2.0 license

Recommend Servers

View All

Concordance

@matharrismma

Language models generate; Concordance verifies. The verify tool checks a claim deterministically (no model in the loop) and returns HOLDS / BROKEN / INCOMPLETE with the worked reasoning and a sealed receipt (content_hash + cite_url) that re-fetches byte-identical or not at all. Also: ranked search over an ~11k-record library, seal_fetch to re-verify any receipt, redact to strip PII before text travels, and a sealed connection graph. Runs sovereign/offline too (stdlib-first Python). A public false-positive benchmark covers every domain: the engine has never sealed a falsehood. 38 tools live; remote endpoint at https://narrowhighway.com/mcp.

10 days ago