--- title: "AWS Marketplace AgentCore Integration Checklist" url: https://www.suger.io/resources/blog/aws-marketplace-agentcore-preflight-checklist/ canonical: https://www.suger.io/resources/blog/aws-marketplace-agentcore-preflight-checklist/ type: Blog description: "A preflight checklist for AWS Marketplace AgentCore integration: the MCP or OpenAPI path, AWS's published spec requirements, fulfillment and testing." --- # AWS Marketplace AgentCore Integration Checklist > Canonical HTML version: https://www.suger.io/resources/blog/aws-marketplace-agentcore-preflight-checklist/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. AWS Marketplace AgentCore Integration: An API and MCP Preflight Checklist # AWS Marketplace AgentCore Integration: An API and MCP Preflight Checklist Buyers can add your AWS Marketplace API or MCP server to their Amazon Bedrock AgentCore gateway, if the listing meets requirements AWS spreads across two guides. Here they are side by side, with Suger's own pre-checks kept apart. [![Stacy Wu](/authors/stacy-wu.jpg)](/resources/blog/author/stacy-wu/) [Stacy Wu](/resources/blog/author/stacy-wu/) Sep 29, 2026 ![AWS Marketplace AgentCore Integration: An API and MCP Preflight Checklist](/images/blog/aws-marketplace-agentcore-preflight-checklist/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-marketplace-agentcore-preflight-checklist%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-marketplace-agentcore-preflight-checklist%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-marketplace-agentcore-preflight-checklist%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-marketplace-agentcore-preflight-checklist%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Marketplaces. "Summarize with Perplexity") Table of Contents - [What is AWS Marketplace AgentCore integration?](#what-is-aws-marketplace-agentcore-integration) - [The preflight checklist at a glance](#the-preflight-checklist-at-a-glance) - [Which path does your product take?](#which-path-does-your-product-take) - [What does AWS require of an MCP server?](#what-does-aws-require-of-an-mcp-server) - [What does AWS require of an OpenAPI specification?](#what-does-aws-require-of-an-openapi-specification) - [Which fulfillment option should an AgentCore-ready listing use?](#which-fulfillment-option-should-an-agentcore-ready-listing-use) - [How do you test and enable the integration?](#how-do-you-test-and-enable-the-integration) - [What does Suger check before AWS sees the spec?](#what-does-suger-check-before-aws-sees-the-spec) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _AWS Marketplace AgentCore integration is an opt-in on an API-based AI agent or tool listing that lets buyers add your product to their Amazon Bedrock AgentCore gateway, where it becomes tools their agents can call. An MCP server that supports two-legged OAuth needs only its endpoint; every other agent or tool needs an OpenAPI specification that meets AWS’s published compatibility requirements._ * * * Globex sells a search API on AWS Marketplace, and the platform team at Acme, one of its buyers, wants to call it from agents they run on Amazon Bedrock AgentCore. AWS supports that as an option on the listing: turn on the AgentCore integration, and Acme can add Globex’s API to its own gateway, where each operation becomes a tool. The requirements are split between the AWS Marketplace Seller Guide and the Amazon Bedrock AgentCore Developer Guide. The first covers the listing; the second covers what the Gateway itself supports. They mostly agree, and each lists something the other doesn’t. This checklist puts them side by side and keeps Suger’s own pre-checks in a separate section, so AWS’s rules and ours never blur. For the category, the deployment options and pricing, start with [selling AI agents on AWS Marketplace](/resources/blog/ai-agents-on-aws-marketplace/). ## What is AWS Marketplace AgentCore integration? **AWS Marketplace AgentCore integration is** an optional setting on a SaaS API-based AI agent or tool listing that offers buyers your product as a target for Amazon Bedrock AgentCore Gateway. **AgentCore Gateway is** AWS’s managed service for converting APIs, Lambda functions and existing services into MCP-compatible tools that agents reach through a gateway endpoint, with inbound and outbound authentication handled by the service. When AWS announced AI agents and tools in AWS Marketplace on July 16, 2025, it named adding tools to AgentCore Gateway among the ways buyers can deploy what they buy. You can switch the integration on in the listing wizard’s fulfillment step, or later with an Update fulfillment options change request. AWS asks you to test your MCP server or OpenAPI specification with AgentCore Gateway before you enable it. ## The preflight checklist at a glance Seven checks, each expanded below: 1. **Choose your path.** An MCP server with two-legged OAuth supplies its endpoint; every other agent or tool supplies an OpenAPI specification. 2. **MCP server.** Two-legged OAuth in one of AWS’s two configurations, tool capabilities, protocol version 2025-06-18 or 2025-03-26, and an encoded URL. 3. **OpenAPI specification.** Version 3.0 or 3.1, an `operationId` on every operation, an `https` server URL, and none of the features either AWS guide lists as unsupported. 4. **Content types.** `application/json` wherever you can; AWS’s two guides disagree about the rest. 5. **Fulfillment.** Quick Launch or redirect, chosen knowing it’s fixed once you publish. A dynamic endpoint requires Quick Launch. 6. **Test.** Create a gateway, attach your product as a target, list its tools and call one. 7. **Enable.** In the listing wizard, or with a change request that moves from Under review to Succeeded. ## Which path does your product take? An MCP server that supports two-legged OAuth takes the MCP path and needs no OpenAPI specification. Every other agent or tool takes the OpenAPI path, including an MCP server that authenticates with API keys; AWS’s AgentCore page and its listing guide divide it the same way. **Two-legged OAuth is** machine-to-machine authentication with the OAuth client credentials grant: the gateway gets a token with a client ID and secret, and no user signs in. Your product Path What AWS uses for the integration An MCP server that supports two-legged OAuth MCP server The MCP endpoint from your listing. No OpenAPI specification An MCP server that authenticates with API keys OpenAPI An OpenAPI specification you upload Any other API-based agent or tool OpenAPI An OpenAPI specification you upload On the OpenAPI path, incoming MCP requests are translated into HTTP requests to your API. The Gateway derives the tools exposed to a buyer’s agents from the operations in your specification. ## What does AWS require of an MCP server? Four things, all on the Marketplace seller guide’s AgentCore page: two-legged OAuth, tool capabilities, a supported protocol version and an encoded URL. Requirement What AWS publishes Authentication Two-legged OAuth, with either a client ID, client secret and discovery URL, or a client ID, client secret, issuer, authorization endpoint and token endpoint Capabilities The server must have tool capabilities. The developer guide adds that prompts and resources are optional, and synced automatically when the server advertises them Protocol version 2025-06-18 or 2025-03-26 URL Encoded. The Gateway invokes the server at the URL you provide The protocol row is where the two guides part. The developer guide lists two newer versions, 2025-11-25 and 2026-07-28, among those AgentCore Gateway supports, and says a gateway’s supported versions are fixed when it’s created unless the account is enabled for MCP version updates. The Marketplace page names only the older two, so make sure your server works on at least one of them. Tell buyers using DEFAULT listing mode to run `SynchronizeGatewayTargets` after your tools, prompts or resources change. ## What does AWS require of an OpenAPI specification? OpenAPI 3.0 or 3.1, an `operationId` on every operation, no semantic errors, an `https` server URL, and none of the features AWS lists as unsupported. Both guides publish a feature table; where they differ, this table shows which one said what. Check AWS Marketplace seller guide AgentCore developer guide Version 3.0 and 3.1. Version 2 is not supported 3.0 and 3.1. Swagger 2.0 is not supported `operationId` On all operations On every operation you want exposed as a tool; it becomes the tool name Semantic errors None None Server URL A valid secure (https) endpoint URL; a basic URL or one with placeholders A valid URL of the actual endpoint. Avoid placeholders that allow arbitrary domain or host substitution Schema composition `oneOf` and `anyOf` not supported `oneOf`, `anyOf` and `allOf` not supported Media types `application/json`, `application/xml`, `multipart/form-data` and `x-www-form-urlencoded`. No custom or binary types The same four in its feature table, but “Only application/json content type is fully supported” Parameters Simple path and basic query parameters (string, number, boolean). No complex path serialization, complex query arrays, or header or cookie serialization No path parameter serializers, and no query, header or cookie parameter serializers Validation Basic field validation. No regex pattern or min/max value validation Not listed Security No security schemes at spec level (OAuth 2.0, API key or HTTP Basic), and no multiple security schemes No security schemes at spec level; authentication is configured in the gateway’s outbound authorization Callbacks and webhooks Not listed Callback operations and webhook definitions not supported Links Not listed Links between operations not supported Names Not listed Names that break a downstream model’s ToolSpec constraints make tool calls fail Meet every row in both columns. `allOf`, callbacks, webhooks and links appear only in the developer guide, and the validation limits only on the Marketplace page, so a spec written to one guide alone can miss the other. ### The operationId becomes the tool name AgentCore Gateway uses each `operationId` as the tool name in the MCP interface, prefixed with the name of the target it came through: `${target_name}___${tool_name}`. If Acme adds Globex’s API as a target named GlobexSearch, Globex’s `searchContent` operation reaches Acme’s agents as `GlobexSearch___searchContent`. The names also have to suit whatever model the buyer runs. The developer guide warns that names not compliant with a downstream model’s ToolSpec make the data plane fail, and gives over-long property names and unsupported characters as the common errors. Keep operation IDs and property names short, descriptive and plain. ### The server URL: https, and placeholders only inside your own domain The Marketplace page asks for “a valid secure (https) endpoint URL in the server attribute” and accepts placeholders. The developer guide explains the risk: patterns such as `https://{yourDomain}/` or `https://{host}/api/` let a value substitute an arbitrary host, which AWS warns can be exploited for server-side request forgery or to exfiltrate credentials. Use a fully qualified static URL where you can. Where a placeholder is necessary, confine it to a subdomain of a domain you control, restrict it with an `enum`, and validate the value in your API too. ### Media types: where AWS’s two guides disagree The Marketplace seller guide lists `application/xml`, `multipart/form-data` and `x-www-form-urlencoded` as supported alongside `application/json`. The AgentCore developer guide lists the same four in its feature table, yet its key considerations say “Only application/json content type is fully supported.” Both are current AWS pages, so take the narrower reading: give every operation you want an agent to call a JSON request and response. If one must take XML or a form, test it through your own gateway before you enable the integration, and describe it in your usage instructions. ### A worked example: one spec, checked against both guides An illustrative example with a fictional seller. Globex’s first spec for its search API turns up five findings: In Globex’s spec Where AWS states the rule Change `"swagger": "2.0"` Both guides: OpenAPI 3.0 or 3.1 Convert it to OpenAPI 3.0 or 3.1 Server URL `http://api.globex.example/v1` Marketplace page: an https URL Serve and declare `https://api.globex.example/v1` A top-level `security` requirement Both guides: no security schemes at spec level Remove it; buyers configure authentication in their gateway A `callbacks` object on the export operation Developer guide only Remove it The export operation responds only in `application/xml` Developer guide: only JSON is fully supported Add a JSON response, or test the XML one in a gateway first ## Which fulfillment option should an AgentCore-ready listing use? Decide before you publish: AWS says “You cannot change the fulfillment method after you publish the product.” Quick Launch, which AWS labels recommended, delivers credentials into the buyer’s AWS account; redirect sends buyers to your website for API keys or OAuth tokens. A dynamic endpoint requires Quick Launch. Quick Launch Redirect to your website How the buyer gets credentials You deliver API keys or OAuth credentials with the AWS Marketplace Deployment API’s `PutDeploymentParameter`, which stores them in the buyer’s AWS Secrets Manager The buyer signs up on your website and gets API keys or OAuth tokens there Dynamic endpoint Supported Not available For OAuth, AWS’s example Quick Launch payload carries a client ID, a client secret and a discovery URL, the same three values as the first OAuth configuration the MCP path accepts. AWS’s API product guidelines also expect buyers to be able to rotate or invalidate keys, and keys to be invalidated when a buyer unsubscribes. ### Dynamic endpoints **A dynamic endpoint is** an endpoint URL with `{paramName}` placeholders that resolve to a buyer-specific URL after subscription, such as `https://{tenantId}.apps.example.com/v1/mcp`. AWS allows up to five parameters per endpoint, matched one-for-one with placeholders. A name starts with a letter, uses only letters, digits and underscores, and is at most 64 characters; an optional default value, used until a buyer-specific value arrives, is at most 256. Delivery has a fixed order. When the buyer reaches your registration page, call `ResolveCustomer` first, because you need the buyer’s account ID and product code from its response; [how the ResolveCustomer handshake breaks](/resources/blog/marketplace-provisioning-failures/) covers what goes wrong there. Then provision the buyer, call `PutDeploymentParameter` with the endpoint parameter values, and call it again, separately, with the credentials; AWS says not to combine them. The buyer’s fulfillment page then shows the resolved URL. AWS recommends an `expirationDate` of `9999-12-31T23:59:59Z` for stable parameters such as tenant IDs and Regions, never for credentials, and a default value for any parameter you add to a public listing after launch. One gap before you combine dynamic endpoints with AgentCore. For an MCP server, AWS’s AgentCore page says the Gateway invokes the endpoint you provide in the listing, and neither it nor the listing guide says how a dynamic endpoint’s placeholders resolve for a buyer’s gateway. If your endpoint is dynamic, confirm that with AWS before you enable the integration. ## How do you test and enable the integration? Test in a gateway of your own, then switch the integration on from AWS Partner Central. AWS’s test sequence has three tasks: 1. **Create a gateway.** 2. **Attach your product as a target**, with a credential provider for the authentication your buyers will use. OAuth and API key providers are configured in AgentCore Identity, in the same account and Region as the gateway. 3. **Test the gateway.** List its tools, check that every operation you expect appears under its prefixed name, and call at least one. Then enable it. On an existing product, AWS’s steps are: 1. Sign in to AWS Partner Central and open the AI agents and tools page. 2. On the AI agents and tools products tab, select the product. 3. From the Request changes list, choose Update fulfillment options. 4. Choose Enable tool for Amazon Bedrock AgentCore integration. 5. Upload your OpenAPI specification. An MCP server with two-legged OAuth needs only its MCP endpoint. 6. Choose Submit. The request shows as Under review on the Requests tab and changes to Succeeded when processing completes. On a new listing, the same option sits in the wizard’s fulfillment step. ## What does Suger check before AWS sees the spec? Suger checks an AI API product’s OpenAPI file against AgentCore Gateway’s OpenAPI rules when you create the product, and again when you save an edit to its info or pricing or publish it; saving a draft doesn’t run the check. An incompatible file is refused in Suger, with each problem named, rather than failing later in AWS. This section describes Suger’s behaviour, not AWS’s. The check sits in the AI API Product section of Suger’s AWS Marketplace product form, where you set the endpoint URL, authorization method, type, usage instructions and protocols, then choose OpenAPI under API Specification and upload the file. Most of its rules restate AWS’s, from the OpenAPI version and unique operation IDs to the unsupported keywords, media types and parameter styles. Three differ from AWS’s published pages: Suger’s pre-check Compared with AWS’s pages The file must be JSON; YAML is refused Suger’s own rule, not a requirement on AWS’s Marketplace integration page The file must be 1 MB or smaller Suger’s own rule, not a requirement on AWS’s Marketplace integration page Each server URL may use http or https Looser than AWS. The Marketplace page asks for https, so use https even though Suger accepts http The documented check doesn’t cover everything AWS publishes. Its list leaves out the Marketplace page’s validation limits (regex patterns and min/max values) and the developer guide’s ToolSpec naming constraints, and it doesn’t enforce the JSON-first guidance on media types. It reads the OpenAPI file, so it says nothing about an MCP server’s OAuth configuration or protocol version. A spec that passes in Suger still needs the gateway test. [Suger’s AI API product fields and pre-check rules](https://doc.suger.io/aws-marketplace/list-product/#ai-api-products) has the full list. ## Frequently asked questions ### Do I need an OpenAPI spec for AWS Marketplace AgentCore integration? Not if you list an MCP server that supports two-legged OAuth: AWS uses the MCP endpoint from your listing. Every other API-based agent or tool, including an MCP server that authenticates with API keys, needs an OpenAPI specification. ### Which OpenAPI versions does AgentCore Gateway support? OpenAPI 3.0 and 3.1. The AWS Marketplace seller guide and the AgentCore developer guide both say version 2, Swagger 2.0, isn’t supported, so convert an older file before you test or upload it. ### Why does every operation need an operationId? AgentCore Gateway uses the operationId as the tool’s name in the MCP interface, prefixed with the name of the buyer’s gateway target. AWS asks for one on every operation, and names a downstream model can’t accept make tool calls fail. ### Does AgentCore Gateway support XML or form request bodies? AWS’s pages differ. The Marketplace seller guide lists application/xml, multipart/form-data and x-www-form-urlencoded as supported, but the AgentCore developer guide says only application/json is fully supported. Use JSON wherever you can, and test any other content type in your own gateway first. ### Can I change the fulfillment method after publishing an API-based AI listing? No. AWS says you can’t change the fulfillment method after you publish the product. Quick Launch is also the only option for a dynamic endpoint with buyer-specific placeholders, so make the choice before you publish. ### What does Suger check before an AI API spec reaches AWS? Suger checks the OpenAPI file against AgentCore Gateway’s rules when you create the product, save an edit to its info or pricing, or publish it. It also refuses YAML and files over 1 MB, which are Suger’s own limits, not rules on AWS’s Marketplace integration page. ## Takeaways - AgentCore integration is an opt-in on an API-based AI listing: an MCP server on two-legged OAuth supplies its endpoint, and everything else an OpenAPI specification. - AWS publishes the requirements in two guides that each list something the other doesn’t. Meet both. - Design for `application/json`; AWS’s guides disagree on XML and form bodies. - The fulfillment method is fixed once you publish, and a dynamic endpoint needs Quick Launch. - Test in your own gateway, then enable the integration and watch the request reach Succeeded. - Suger’s pre-check catches spec problems before AWS sees them. Its JSON-only and 1 MB rules are Suger’s own, and it accepts http where AWS asks for https. Suger’s AI API product form carries the endpoint, authorization method, type, usage instructions and OpenAPI specification for an AWS listing, and checks the spec before it reaches AWS. See how Suger lists, meters and fulfills [AI agents and MCP servers on cloud marketplaces](/solutions/ai-marketplace-distribution/). ## Sources Primary sources for the platform rules cited above. Last verified September 29, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS Marketplace Seller Guide: Amazon Bedrock AgentCore Gateway](https://docs.aws.amazon.com/marketplace/latest/userguide/bedrock-agentcore-gateway.html) — What the Gateway does; the two integration paths, an MCP server with two-legged OAuth or an OpenAPI specification for all other agents or tools; the MCP server requirements (the two OAuth configurations, tool capabilities, protocol versions 2025-06-18 and 2025-03-26, an encoded URL); the OpenAPI requirements and the supported and unsupported feature table; the three test tasks; the Update fulfillment options steps and the Under review and Succeeded statuses - [AWS Marketplace Seller Guide: Listing SaaS API-based AI agent products](https://docs.aws.amazon.com/marketplace/latest/userguide/listing-saas-ai-agents.html) — Quick Launch (recommended) and redirect fulfillment, and that the method can't change after the product is published; static and dynamic endpoints, dynamic endpoints requiring Quick Launch, up to 5 parameters and their name and default-value limits; the optional AgentCore integration step in the listing wizard, with no OpenAPI spec for a two-legged OAuth MCP server and a spec for any other product or an MCP server on API keys - [AWS Marketplace Seller Guide: Integrating API-based AI agent products](https://docs.aws.amazon.com/marketplace/latest/userguide/integrating-api-ai-agents-tools.html) — The key-management guideline; Quick Launch credentials stored in the buyer's AWS Secrets Manager with PutDeploymentParameter, and the OAuth payload with a client ID, client secret and discovery URL; the dynamic-endpoint onboarding order, ResolveCustomer first and separate calls for parameters and credentials; the expirationDate and default-value best practices - [Amazon Bedrock AgentCore Developer Guide: OpenAPI schema targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-schema-openapi.html) — The operationId as the MCP tool name; OpenAPI 3.0 and 3.1, not Swagger 2.0; only application/json fully supported, beside a feature table listing four media types; oneOf, anyOf and allOf, parameter serializers, spec-level security schemes, callbacks, webhooks and links between operations not supported; ToolSpec naming failures; the server URL placeholder guidance; OAuth and API key credential providers configured in AgentCore Identity in the gateway's account and Region - [Amazon Bedrock AgentCore Developer Guide: MCP servers targets](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-MCPservers.html) — Tool capabilities required, prompts and resources optional; the Gateway's supported protocol versions 2026-07-28, 2025-11-25, 2025-06-18 and 2025-03-26, fixed at gateway creation unless the account is enabled for MCP version updates; SynchronizeGatewayTargets after tools, prompts or resources change on a target in DEFAULT listing mode; two-legged OAuth as the client credentials grant - [Amazon Bedrock AgentCore Developer Guide: Understand how AgentCore Gateway tools are named](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-tool-naming.html) — Tool names visible through MCP follow the pattern of the target name, three underscores, then the tool name - [Amazon Bedrock AgentCore Developer Guide: Use an AgentCore gateway](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-using.html) — The MCP operations a gateway supports, including tools/list and tools/call, used here as the test step - [AWS What's New: Introducing AI agents and tools in AWS Marketplace](https://aws.amazon.com/about-aws/whats-new/2025/07/ai-agents-tools-aws-marketplace/) — Posted July 16, 2025: the category announcement, naming AgentCore Runtime and adding tools to AgentCore Gateway among the paths buyers can take to deploy what they buy - [Suger docs: List Product, AI API Products](https://doc.suger.io/aws-marketplace/list-product/#ai-api-products) — Suger behaviour: the AI API Product fields; the OpenAPI pre-check on create, on saving an edit to info or pricing, and on publish, but not on saving a draft; its rules, including JSON only, 1 MB or smaller, http or https server URLs and unique operationIds ## Keep reading - [AWSAWS Marketplace Future-Dated Agreements: Renew EarlySep 28, 2026](/resources/blog/aws-marketplace-future-dated-agreements/) - [AWSAWS Marketplace Concurrent Agreements: Opt In or Relist?Sep 24, 2026](/resources/blog/aws-marketplace-concurrent-agreements-opt-in-or-relist/) - [AWSAWS Marketplace Private Offer Errors: Why a Buyer Can't AcceptSep 19, 2026](/resources/blog/buyer-cannot-accept-aws-private-offer/) - [AWSWhat the Deployed on AWS Badge Proves, and What It Doesn'tSep 19, 2026](/resources/blog/deployed-on-aws-badge/) [Browse every post on the Suger Blog](/resources/blog/) ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.