canonical: https://jentic.com/apis/amazon.com/amazon # Amazon Chime The Amazon Chime API runs communications and meeting infrastructure: online meetings, attendees, chat channels, and voice connectors for SIP telephony. It covers account and user administration, real-time messaging channels, and phone-number management across a broad operation set. Requests authenticate with AWS Signature Version 4 (SigV4). ## For AI agents Create and manage Amazon Chime meetings, attendees, messaging channels, and voice connectors for communications workflows. ## Scope Does not handle email delivery, general AWS compute, or contact-center routing - use for Chime meetings, messaging, and voice connectors only. ## Capabilities - Create meetings and add attendees for real-time audio and video - Manage messaging channels, memberships, and channel moderation - Provision and configure voice connectors for SIP telephony - Administer Chime accounts, users, and user settings - Manage phone numbers and assign them to users or voice connectors ## Use cases ### On-demand meeting creation An application that embeds audio and video needs to spin up meetings on demand and admit participants. The Amazon Chime API creates a meeting and issues attendee credentials so clients can join, then tears the meeting down when it ends. Example prompt: Create a meeting, add two attendees, and return their join tokens for the client SDK ### Team messaging channels A collaboration product needs persistent chat channels with membership control. The messaging operations create channels, add and remove members, and moderate messages so a backend can run team conversations. Example prompt: Create a messaging channel, add three members, and post a welcome message ### SIP voice connector provisioning A telephony integration needs inbound and outbound calling over SIP. The voice connector operations provision a connector, attach phone numbers, and configure origination and termination so calls can flow. Example prompt: Provision a voice connector, attach a phone number, and configure termination settings ### AI agent communications setup An AI agent orchestrating a support flow can create meetings and messaging channels without hand-signing AWS requests. Through Jentic the agent discovers Chime operations by intent and calls them with credentials injected at run time. Example prompt: Search Jentic for 'create a Chime meeting', load the schema, and start a meeting with two attendees ## Key resources - **Meetings** — Create meetings, manage attendees, and run real-time media sessions - **Messaging channels** — Create channels, manage memberships, and moderate messages - **Voice connectors** — Provision SIP connectors and configure origination and termination - **Accounts and users** — Administer Chime accounts, users, and their settings - **Phone numbers** — Order phone numbers and assign them to users or voice connectors ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 51 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 97 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 35 / 100 - Agent Usability: 47 / 100 - Security: 50 / 100 - AI Discoverability: 66 / 100 - **View full report:** https://jentic.com/apis/amazon.com/amazon/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Amazon Chime API by hand means computing AWS Signature Version 4 on every request and shaping the meeting, channel, and voice-connector payloads yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it. - **Permission scoping:** The Amazon Chime API addresses accounts, meetings, and channels by id in the URL path, so you can limit the agent to the operations it needs, such as creating a meeting or listing attendees. You credit the agent only with the operations you allow, so deleting an account stays out unless you add it. - **Credential handling:** Your your AWS credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a Chime meeting' or 'add an attendee', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the AWS reference. ## Related APIs - **Zoom Meetings API** — Hosted video meetings with scheduling and recording - **Twilio Video API** — Programmable video rooms with fine-grained media control - **SendGrid Mail API** — Transactional email to accompany meeting invites and notifications ## FAQ ### What authentication does the Amazon Chime API use? The Amazon Chime API authenticates requests with AWS Signature Version 4 (SigV4), signing each call with your AWS access key and secret. Through Jentic those credentials are stored encrypted in your own instance and the signature is applied at run time. ### Is there a the Amazon Chime API MCP server? You don't need an MCP server to give your agent the Amazon Chime API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec. ### Can the Amazon Chime API handle both meetings and chat? Yes. It covers real-time meetings with attendees, persistent messaging channels with membership control, and voice connectors for SIP telephony, alongside account and phone-number administration. ### Can I limit what my agent is allowed to do with the Amazon Chime API? Yes. Because you run Jentic One yourself, your own rules decide which the Amazon Chime API operations and credentials the agent may use. You grant only the operations it needs, such as creating a meeting, so deleting an account stays off limits unless you add it. The choice of what the agent may call is yours. ### How do I connect my agent to the Amazon Chime API through Jentic? Search Jentic by intent such as 'create a Chime meeting' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.