AWS Elemental MediaLive
cloud:amazonaws-medialive · github.com/mermade/aws2openapi ↗
API for AWS Elemental MediaLive
About the AWS Elemental MediaLive API
AWS Elemental MediaLive API on Apizie: 62 endpoints (Accept an incoming input device transfer. The ownership of the device will transfer to your AWS account., Starts delete of resources., Starts existing resources, Stops running resources, …) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://zieapi.vercel.app/v1/cloud:amazonaws-medialive/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.
| Project key | cloud:amazonaws-medialive |
|---|---|
| Status | Your key |
| Endpoints | 62 |
| Category | Cloud |
| Source | github.com/mermade/aws2openapi |
| Base URL | https://zieapi.vercel.app/v1/cloud:amazonaws-medialive/{endpoint} |
| For AI tools | OpenAPI spec · Markdown (what is this?) |
AWS Elemental MediaLive API FAQ
How do I call the AWS Elemental MediaLive API?
Create a free Apizie key, then send POST https://zieapi.vercel.app/v1/cloud:amazonaws-medialive/accept-input-device-transfer with the header x-api-key. Every endpoint returns { project, data, timestamp }.
Is the AWS Elemental MediaLive API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. AWS Elemental MediaLive itself also needs your own key from amazonaws.com.
Can AI agents use the AWS Elemental MediaLive API?
Yes. Add the Apizie MCP server (https://zieapi.vercel.app/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key cloud:amazonaws-medialive.
What is the status of the AWS Elemental MediaLive API?
Needs your own provider key (bring your own key)