CAPI FAQs

Question 1

How does CAPI handle service discovery and routing?

Accepted Answer

CAPI automatically discovers services registered in HashiCorp Consul. It then dynamically creates routes, enabling intelligent load balancing, failover, and policy application without requiring a traditional database.

Question 2

Does CAPI support gRPC services?

Accepted Answer

Yes, CAPI includes an experimental gRPC Gateway which acts as a transparent HTTP/2 reverse proxy for gRPC services, supporting header-based routing.

Question 3

What security features are integrated into CAPI?

Accepted Answer

CAPI offers robust integrated security, including OAuth2/OIDC token validation for multi-provider support and fine-grained authorization using OPA (Open Policy Agent).

Question 4

What is CAPI and what is its primary purpose?

Accepted Answer

CAPI is a lightweight API Gateway and load balancer powered by Apache Camel. Its primary purpose is to provide dynamic routing, automated service discovery through HashiCorp Consul, and apply security, throttling, and observability policies to your APIs.

Question 5

Can CAPI bridge existing REST APIs for use with LLM agents?

Accepted Answer

Yes, CAPI features an experimental MCP Gateway that can turn any existing REST API into an LLM tool. It handles the translation, allowing LLM agents to discover and invoke your REST services without requiring backend code changes.

CAPI

CAPI

主な機能

ユースケース

主な機能

ユースケース