Api Gateway
API Gateway pattern for routing. Use for microservices entry.
Install
$ agentstack add skill-g1joshi-agent-skills-api-gateway ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-g1joshi-agent-skills-api-gateway) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
API Gateway
An API Gateway sits between clients (Mobile, Web) and services. It acts as a reverse proxy, accepting all API calls, aggregating the various services required to fulfill them, and returning the appropriate result.
When to Use
- Microservices: Essential to hide the complexity of backend services (Service Discovery).
- Cross-Cutting Concerns: Centralizing Authentication, SSL Termination, Rate Limiting, and Logging.
- Protocol Translation: Converting HTTP (Client) to gRPC (Internal).
Core Functionality
Routing
GET /users -> User Service GET /orders -> Order Service
Aggregation (BFF - Backend for Frontend)
Combining results. One request to Gateway -> Calls User Service + Order Service -> Returns combined JSON.
Offloading
- Auth: Validating JWT tokens at the edge.
- Cache: Serving static or cached responses.
Common Patterns
Backend for Frontend (BFF)
Creating specific gateways for different clients (e.g., one for Mobile with small payloads, one for Web with rich payloads).
Best Practices
Do:
- Use mature tools: Kong, Traefik, AWS API Gateway, Nginx.
- Implement Rate Limiting to prevent DoS.
- Use Correlation IDs for tracing requests across services.
Don't:
- Don't put business logic in the Gateway (It's not a service).
- Don't let it become a Single Point of Failure (High Availability is key).
Troubleshooting
| Error | Cause | Solution | | :-------------------- | :------------------------------------ | :------------------------------------------------ | | 502 Bad Gateway | Upstream service down or unreachable. | Check internal service health and firewall rules. | | 504 Gateway Timeout | Upstream taking too long. | Optimize service or increase timeout (carefully). |
References
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: G1Joshi
- Source: G1Joshi/Agent-Skills
- License: MIT
- Homepage: https://skills.sh/g1joshi/agent-skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.