a6-recipe-graphql-proxy

Configure GraphQL proxying patterns with a6 CLI and Apache APISIX.

1|2|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/moonming/a6 --skill a6-recipe-graphql-proxy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a6-recipe-graphql-proxy
Source: https://github.com/moonming/a6/tree/main/skills/a6-recipe-graphql-proxy
Command: npx skills add https://github.com/moonming/a6 --skill a6-recipe-graphql-proxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the implementation of advanced GraphQL proxying patterns within Apache APISIX, enabling efficient routing, security, and transformation of GraphQL requests.

Core Features & Use Cases

  • Operation-Based Routing: Route queries and mutations to different backends based on GraphQL operation type or name.
  • Per-Operation Rate Limiting: Apply distinct rate limits to queries versus mutations.
  • REST-to-GraphQL Conversion: Use the degraphql plugin to expose GraphQL APIs through RESTful endpoints.
  • Use Case: Securely expose a GraphQL API, route specific operations to specialized services, and enforce granular access controls and rate limits for different GraphQL request types.

Quick Start

Use the a6-recipe-graphql-proxy skill to create routes for GraphQL queries and mutations.

Frequently Asked Questions about a6-recipe-graphql-proxy

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

FAQPage Schema
How do I route GraphQL queries and mutations to different backends using Apache APISIX?

GraphQL operation-based routing in Apache APISIX directs queries and mutations to different backends by matching the GraphQL operation type or name, allowing specialized services to handle specific request types.

Can I apply different rate limits to GraphQL queries versus mutations in APISIX?

Per-operation rate limiting in APISIX applies distinct rate limits to GraphQL queries versus mutations, enforcing granular access controls and preventing mutation flooding on exposed GraphQL APIs.

How does the degraphql plugin convert REST endpoints to GraphQL APIs in APISIX?

The degraphql plugin enables REST-to-GraphQL conversion by exposing GraphQL APIs through RESTful endpoints in Apache APISIX, allowing clients to interact with GraphQL backends using standard HTTP REST requests.

Does APISIX GraphQL proxying require a specific version or CLI tool to configure routes?

Apache APISIX GraphQL proxying patterns require APISIX version 3.0.0 or higher and the a6 CLI tool for route creation and configuration management of operation-based routing and security patterns.

What security patterns are available for protecting GraphQL APIs with Apache APISIX?

GraphQL API security patterns in Apache APISIX include operation-based routing, per-operation rate limiting for queries and mutations, and granular access controls to securely expose GraphQL endpoints to clients.

Why use a6 CLI recipes for GraphQL proxying instead of standard APISIX admin API configuration?

The a6 CLI provides specialized recipes for implementing GraphQL proxying patterns in APISIX, simplifying the creation of operation-based routing, rate limiting, and degraphql plugin configuration compared to manual admin API calls.