api-gateway

Design and configure API gateways for routing, authentication, and traffic management.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill api-gateway-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-gateway
Source: https://github.com/mahg-es/araya/tree/main/skills/api-gateway
Command: npx skills add https://github.com/mahg-es/araya --skill api-gateway-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clients calling microservices directly leads to tight coupling, security sprawl, and complex client logic. An API gateway consolidates authentication, rate limiting, routing, and transformation at the edge — clients call one endpoint; the gateway handles the rest.

Core Features & Use Cases

  • Edge gateway for central authentication, rate limiting, routing, and request/response transformation
  • Backend-for-frontend (BFF) pattern: one gateway per client type (web, mobile, API)
  • Health checks, monitoring, and circuit breakers for backend services
  • CORS, request validation, and request logging to improve security and observability
  • Use case: frontend apps needing access to multiple microservices through a single entry point with consistent security and response composition

Quick Start

Configure and deploy an edge API gateway to route to services, enforce authentication, and apply rate limits for frontend clients.

Frequently Asked Questions about api-gateway

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an API gateway and when do I need one for microservices?

An API gateway centralizes routing, authentication, and traffic management at the edge. You need one when clients call multiple microservices directly, causing tight coupling, security sprawl, and complex client logic.

How do I configure JWT-based authentication for microservices routing?

Configure JWT-based authentication by applying per-route policies at the gateway edge. The gateway intercepts requests, validates tokens centrally, and routes traffic to backend services without requiring individual services to handle auth.

Can I enforce rate limiting and CORS policies for frontend clients?

Yes, you can enforce rate limiting and CORS policies for frontend clients. The gateway applies per-route cross-cutting concerns, including request validation and edge security, across all backend services from a single entry point.

Does the Backend-for-Frontend pattern work with per-route health checks and monitoring?

The Backend-for-Frontend pattern supports per-route health checks, monitoring, and circuit breakers. You configure one gateway per client type, such as web or mobile, to manage backend service resilience and coordinated observability.

What's the best way to decouple frontend apps from multiple backend services?

The best way to decouple frontend apps from multiple backend services is deploying an edge gateway. It provides a single entry point for consistent security, request/response transformation, and response composition across all microservices.

Why does calling microservices directly lead to security sprawl?

Calling microservices directly leads to security sprawl because each service must independently manage authentication and routing. An edge gateway consolidates these cross-cutting concerns, centralizing security and reducing duplicated client logic.