Sweet FAQs

Question 1

What types of API protocols can Sweet normalize?

Accepted Answer

Sweet specializes in normalizing requests from three main protocols: GraphQL, JSON-RPC 2.0, and Cap'n Proto. All these are transformed into the unified Model Context Protocol (MCP) for consistent processing.

Question 2

How does Sweet handle request routing and ensure high availability?

Accepted Answer

Sweet utilizes intelligent, load-based request routing. It processes requests locally when server load is low, and automatically forwards requests to the peer with the lowest load (based on `node_load1` metric) when overloaded, ensuring efficient distribution and scalability across a cluster.

Question 3

What security features are integrated into Sweet?

Accepted Answer

Sweet includes robust integrated security features such as JWT authentication (HS256 signing), built-in rate limiting (10 requests/min per endpoint), and automated TCP health checks every 10 seconds to ensure secure and reliable API operations.

Question 4

How do Sweet nodes discover each other in a cluster?

Accepted Answer

Sweet nodes leverage automated peer discovery through multiple industry-standard methods: primary DNS-based discovery using SRV records (with DoH), mDNS for local network zero-config discovery, and HTTP-based peer exchange for mesh formation. Nodes also verify build compatibility via Git-hash to ensure cluster integrity.

Question 5

What is Sweet and what is its primary function?

Accepted Answer

Sweet is a multi-protocol edge proxy designed to normalize diverse API requests. It converts incoming GraphQL queries, JSON-RPC 2.0 method calls, and Cap'n Proto binary messages into a standardized Model Context Protocol (MCP) format, streamlining API communication.

Sweet

Sweet

Key Features

Use Cases

Key Features

Use Cases