Amazon Amplify
AWS Amplify is a set of tools and services for building secure, scalable full-stack applications powered by AWS. It provides frontend and mobile developers with a complete workflow for building, deploying, and hosting cloud-powered applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Amazon Amplify the way a machine reads it — 53 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Amazon Amplify scores 56.9/100 (developing), with a separate agent-readiness read of 60/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Amazon Amplify
Each block below is one kind of artifact we hold for Amazon Amplify. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Amazon Amplify Apps API
The Apps API from Amazon Amplify — 4 operation(s) for apps.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
amazon-amplify-mcp.yml
MCP SERVERFeatures 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
App Management
Create, update, and delete Amplify apps connected to Git repositories with automated build and deployment settings.
Branch Management
Manage feature branches and environments with independent build configurations, environment variables, and preview URLs.
Deployment Automation
Trigger and monitor deployments across branches with build history, logs, and status tracking.
Domain Association
Associate custom domains with Amplify apps and manage SSL certificates and subdomain routing configurations.
Backend Environment Management
Manage AWS backend environments linked to Amplify applications for full-stack cloud resource provisioning.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Amazon Amplify Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Amazon Amplify API Rules
SPECTRALAmazon Amplify API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
App
JSON SCHEMABranch
JSON SCHEMACreateAppRequest
JSON SCHEMACreateAppResult
JSON SCHEMACreateBranchRequest
JSON SCHEMACreateDomainAssociationRequest
JSON SCHEMAGetAppResult
JSON SCHEMAListAppsResult
JSON SCHEMAProductionBranch
JSON SCHEMAUpdateAppRequest
JSON SCHEMAScroll within the panel for all 10 ·
JSON Structure 10
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Amazon Amplify App Structure
JSON STRUCTUREAmazon Amplify Branch Structure
JSON STRUCTUREAmazon Amplify Createapprequest Structure
JSON STRUCTUREAmazon Amplify Createappresult Structure
JSON STRUCTUREAmazon Amplify Createbranchrequest Structure
JSON STRUCTUREAmazon Amplify Createdomainassociationrequest Structure
JSON STRUCTUREAmazon Amplify Getappresult Structure
JSON STRUCTUREAmazon Amplify Listappsresult Structure
JSON STRUCTUREAmazon Amplify Productionbranch Structure
JSON STRUCTUREAmazon Amplify Updateapprequest Structure
JSON STRUCTUREScroll within the panel for all 10 ·
Examples 10
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Amazon Amplify App Example
EXAMPLEScroll within the panel for all 10 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
CI/CD Pipeline Automation
Automate build and deployment workflows for frontend apps by programmatically managing Amplify apps and branch deployments.
Multi-Environment Management
Manage development, staging, and production environments as separate branches with independent configurations.
Infrastructure as Code
Provision and configure Amplify hosting environments as part of infrastructure-as-code pipelines using the REST API.
Developer Portal Integration
Integrate Amplify app management into internal developer portals for self-service application deployment and hosting.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
AWS CodeCommit
Connect Amplify apps to AWS CodeCommit repositories for source code hosting and automated deployments.
GitHub
Link Amplify deployments to GitHub repositories with automatic builds triggered on pull requests and branch merges.
AWS CloudFront
Amplify hosting uses CloudFront for global CDN distribution of static assets and dynamic content.
AWS Route 53
Configure custom domains for Amplify apps using Route 53 DNS management and SSL certificate provisioning.
Resources
Every other property we hold for Amazon Amplify — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/amazon-amplify · machine-readable index on apis.io