AWS · Cloud service
Amazon API Gateway with OrchestrAI
Catalog exported 2026-09-02
Build API Gateway REST and HTTP APIs from chat: resources, methods, integrations, deployments, and stages.
OrchestrAI exposes 6 API Gateway operations: 6 create or modify resources and run only after you confirm the plan.
What teams use it for
Teams use OrchestrAI to wire up a REST API in a single conversation: add a resource path, put a method on it, attach a Lambda or HTTP integration, and publish a deployment to a stage. For HTTP APIs it creates the API itself and its stages. All six operations are medium risk, which means they create new resources and can be reversed. There are no describe, list, or delete operations for API Gateway yet, so reviewing existing APIs or removing one still happens in the console.
Every API Gateway operation, with its risk level
| Operation | What it does | Risk | Step-level approval |
|---|---|---|---|
Create API Gateway REST Deployment |
Publish an API Gateway REST API deployment to a stage | Creates resources | No |
Create API Gateway REST Integration |
Create an integration on an API Gateway REST API method | Creates resources | No |
Create API Gateway REST Method |
Create a method on an API Gateway REST API resource | Creates resources | No |
Create API Gateway REST Resource |
Create a resource path in an API Gateway REST API | Creates resources | No |
Create API Gateway v2 HTTP API |
Create an API Gateway v2 HTTP API | Creates resources | No |
Create API Gateway v2 Stage |
Create a deployment stage for API Gateway v2 | Creates resources | No |
Risk tiers come from the catalog: low is read-only or low-impact, medium creates resources and is reversible, high modifies existing resources, destructive may lose data. Every plan that creates or changes resources is shown with its cost estimate and waits for your confirmation. Operations marked with a step-level approval pause again on their own step. Destructive operations require a typed risk phrase.
Prompts that work
- Add a /orders resource to the checkout-api REST API in us-east-1 with a POST method integrated to the process-orders Lambda
- Create an HTTP API named webhooks-api and give it a prod stage with auto-deploy turned on
- Publish the current configuration of the billing REST API to the v2 stage
Before anything runs
Every mutation shows its plan, cost estimate, and blast radius, then waits for your confirmation. Destructive operations require a typed risk phrase. Credentials are minted per run through OIDC federation and discarded afterward; nothing you create here is invisible later, because every resource lands in the desired-state ledger where drift is detected and can be converged. Details on the security page.
Frequently asked questions
- Can OrchestrAI deploy an API Gateway REST API to a stage?
- Yes, the create_deployment operation publishes the current REST API configuration to the stage you name. It is a medium-risk create, so the plan is shown before it runs.
- Does OrchestrAI support API Gateway HTTP APIs as well as REST APIs?
- Both are covered. REST APIs get resource, method, integration, and deployment operations, while HTTP APIs (API Gateway v2) get create_api and create_stage. Custom domain names and authorizers are not included.
- Which API Gateway operations need an extra approval step?
- None of the API Gateway operations currently carries a step-level approval gate; they are read-only or run after plan confirmation like any other change.
Other AWS services
Related integrations
Try it on your own account
Connect your cloud read-only and see your resources, drift, and costs before anything runs. $5 minimum to start. Unused credits refunded in your first 14 days.
Unused credits refunded in your first 14 days.