FORGEBYName your market

The AWS programme reference

Nothing here without its source.

What the AWS partner programme surfaces actually are, in the words of AWS’s own documentation. Every entry names the page it was read at and the day somebody opened that page. An entry with no primary source is not written softer or hedged into shape. It is not written.

15

Entries, every one with a citation

5

Distinct AWS pages behind them

3

Publishers, all of them AWS

Every page cited below was read on 16 August 2026. That date is the shelf life of this file: AWS changes its own documentation, and a citation with no date cannot tell you whether it has moved since.

Why the dates are the product

This is a reference, so the only thing that makes it worth more than a search is whether you can check it in one click. Three rules, all of them enforced in code rather than by good intentions.

Read at the primary source

Every value comes from aws.amazon.com or docs.aws.amazon.com. A page that summarises AWS is not AWS. The check is a host allowlist and an entry that fails it is refused, not footnoted.

Dated at the moment of reading

A programme rule with no date is a rule you cannot age. Each citation carries the day the page was opened, so you know exactly how much trust the entry has earned by the time you read it.

Absent beats estimated

No threshold, cap, rate or amount appears here unless the cited page states it. Where AWS gives one sentence, the entry stops at one sentence and says so.

The reason to be this careful is the company this page keeps. In this category the same small set of outcome figures moves from vendor site to vendor site, each seller presenting it as their own measured result, and following any of them back tends to end at somebody else’s study or at nothing at all. None of those figures is on this page. Not because they flatter a competitor, but because not one of them traces to a page anybody here opened.

15 entries, every one of them cited

Partner Central agents MCP Server

AWS Partner Central API Reference

A fully managed, AWS-hosted server that exposes the Partner Central agents to any MCP-compatible client. It speaks JSON-RPC 2.0 over HTTPS, authenticates with SigV4, and streams responses over Server-Sent Events. It holds multi-turn sessions, accepts file attachments for document analysis, and carries a built-in approval workflow that requires the caller's explicit consent before any write operation executes.

Who it is forAn AWS partner who wants their own tools to talk to Partner Central instead of a person clicking through the console.

What it does not say

  • AWS states that all write operations require explicit human approval before execution.
  • AWS states that data is isolated to the logged-in partner's own opportunities and that every AI-generated insight carries a session id for traceability.
  • AWS documents a Sandbox catalog as an isolated test environment that does not touch production data.
  • AWS states that generated content carries disclosure labels and is governed by the AWS Responsible AI Policy.

Endpoint, signing and the smallest IAM grant

AWS Partner Central API Reference

The server is reached at https://partnercentral-agents-mcp.us-east-1.api.aws/mcp . Requests are signed with AWS Signature Version 4 using service name partnercentral-agents-mcp in us-east-1. The documented minimum permission for protocol access is the single IAM action partnercentral:UseSession, which can be narrowed further with the aws:IsMcpServiceAction condition key. Permission to actually do anything in Partner Central is granted separately, action by action.

Who it is forWhoever writes the IAM policy. This is the difference between a client that connects and a client that gets refused at the door.

What it does not say

  • AWS lists us-east-1 access and TLS 1.2 or later in the client among the prerequisites.
  • AWS states that sessions expire 48 hours after creation and should not be relied on for storage.
  • AWS states that uploaded files go to an ephemeral bucket and that credentials and secrets must never be uploaded.
  • AWS's own guidance is to run production identities on the read-only policy and grant write actions only where a person needs them.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/mcp-getting-started.htmlAWS Partner Central API Reference · read 16 August 2026

Funding guidance extended to all AWS funding programmes

AWS What's New

AWS published on 20 July 2026 that the agents' funding guidance expanded from four funding programmes to all AWS Partner funding programmes, naming the Strategic Collaboration Agreement (SCA) and the AWS Growth Initiative (AGI) as the additions. AWS describes the answers as documentation-backed and covering eligibility requirements, application processes and programme details.

Who it is forA partner deciding whether to ask AWS's own agent about a funding programme rather than reading the programme guide end to end.

What it does not say

  • The announcement names SCA and AGI as the additions. It does not enumerate the four programmes that were covered before, and this file does not guess at them.
  • No eligibility threshold, cap, rate or amount is stated in the announcement, and none is asserted here.
  • AWS describes this as guidance. Guidance is not an approval and not a commitment of funds.

Partner Central Benefits API

AWS Partner Central API Reference

AWS documents a Benefits service providing APIs for managing partner benefits, applications and allocations within the AWS Partner Network.

Who it is forAnyone who assumed a funding application is only ever a form in a portal. There is an API surface behind it.

What it does not say

  • One sentence is the whole of what this page says about the service. No operations are enumerated on it, so none are enumerated here.
  • No benefit amount, cap or rate appears on the page, and none is asserted here.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/welcome.htmlAWS Partner Central API Reference · read 16 August 2026

Partner Central Account API

AWS Partner Central API Reference

AWS documents an Account service providing APIs for managing partner accounts, connections and profiles within the AWS Partner Network: creating and managing a partner profile, establishing connections with other partners, and maintaining account information.

Who it is forWhoever owns the partner profile and keeps discovering it is out of date.

What it does not say

  • The page describes the service in two sentences and lists no operations. Nothing more specific is asserted here.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/welcome.htmlAWS Partner Central API Reference · read 16 August 2026

Partner Central Channel API

AWS Partner Central API Reference

AWS documents a Channel service for managing partner relationships, handshakes and program management accounts.

Who it is forDistribution and reseller structures, where the relationship itself is the object being managed.

What it does not say

  • One sentence is all the page gives: no operations, no shape, no eligibility. This entry deliberately stops where the page stops.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/welcome.htmlAWS Partner Central API Reference · read 16 August 2026

Partner Central Revenue Measurement API

AWS Partner Central API Reference

AWS documents a Revenue Measurement service for creating, managing and tracking revenue attributions and their allocations against deal entities such as offers and opportunities.

Who it is forAnyone whose revenue attribution is currently a spreadsheet reconciled by hand at quarter end.

What it does not say

  • The page describes the service in one sentence. No attribution rule, percentage or window is stated on it, and none is asserted here.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/welcome.htmlAWS Partner Central API Reference · read 16 August 2026

Capability: pipeline insights

AWS Partner Central API Reference

Conversational intelligence over a partner's own pipeline: at-risk opportunities, stage progression, and closed-lost analysis. AWS's documented examples include asking which opportunities need attention this week, how many close next month, and the top reasons deals were lost over the last six months.

Who it is forThe person who currently answers those three questions by exporting a report.

What it does not say

  • AWS states data is isolated to the logged-in partner's own opportunities. It reads what that partner already has, and nothing else.
  • This is a read capability. It surfaces analysis; it does not itself change a record.

Capability: opportunity creation

AWS Partner Central API Reference

Creates an opportunity from a natural language description or an uploaded document. AWS documents that it extracts customer name, project scope, expected close date and other required fields, enriches customer details from publicly available web data, validates the draft against AWS readiness requirements, and creates the record through the Partner Central Selling API after the person approves.

Who it is forAnyone whose meeting notes currently become a multi-step form at the end of a long day.

What it does not say

  • AWS documents PDF, DOCX, XLSX and TXT as document inputs for this capability.
  • The record is created only after approval. Approval is a human act in the partner's own seat, and no automated step can stand in for it.
  • Validation against AWS readiness requirements is AWS's check, not a guarantee that a submitted opportunity is accepted.

Capability: funding recommendation

AWS Partner Central API Reference

Evaluates an opportunity against available AWS funding programmes using the opportunity's own details and each programme's eligibility criteria. Where it finds a match, AWS documents that it shows the programme name, its description and its detailed reasoning, and that it can then estimate a funding amount, create an auto-populated fund request draft, or explain the programme conversationally.

Who it is forA partner who does not know which funding programme a given piece of work fits, which is most partners, most of the time.

What it does not say

  • AWS states that Strategic Collaboration Agreement budget availability is surfaced when relevant and that all actions respect IAM permissions.
  • The amount is an estimate produced by the agent. No figure, cap or rate is stated in the documentation, and none is asserted here.
  • A fund request draft is a draft. The approval workflow still stands between it and a submission.

Capability: customer profile creation

AWS Partner Central API Reference

Generates a company profile from publicly available information, covering industry classification, business model, geographic presence, company size, market focus and recent business developments. AWS documents that these profiles are labelled "Generated with publicly available data and AWS AI insights."

Who it is forThe half hour before a first meeting that currently goes on reading a website.

What it does not say

  • AWS's own label says publicly available data. A profile is a reading of public sources, not a verified record.
  • The documentation states no coverage rate for any country or company size, and none is asserted here.

Capability: solution recommendation

AWS Partner Central API Reference

Cross-references a partner's registered solutions against an opportunity's requirements and returns the solution name, its description, and whether it is already attached to that opportunity.

Who it is forPartners with more registered solutions than any one seller can hold in their head.

What it does not say

  • It matches against solutions already registered. Nothing here registers one.
  • No ranking method or score is described on the page, and none is asserted here.

Capability: the partner onboarding agent

AWS Partner Central API Reference

AWS documents an onboarding agent that scans a company website to extract and populate a partner profile, manages profile visibility, the alliance lead contact, training certification email domains and account connection invitations; gives step-by-step guidance for AWS Marketplace seller registration including the tax form appropriate to country and entity type, banking and disbursement setup by region, and the compliance steps (KYC, bank account verification, secondary user verification); and assesses PRM readiness, including retrieving the product code used for revenue tagging and verifying that subsidiary seller accounts are linked for consolidated revenue attribution.

Who it is forNew sellers, and established ones who have never been sure whether their subsidiary accounts are linked correctly.

What it does not say

  • Guidance, in AWS's own word. It walks a person through a process; it does not complete a registration on their behalf.
  • The documented compliance steps are named but their thresholds are not. No threshold is asserted here.
  • Profile changes are write operations and therefore fall under the same explicit human approval requirement.

AI-assisted product listing

AWS Marketplace Seller Guide

A capability in AWS Partner Assistant that drafts an AWS Marketplace listing from a product website URL, an uploaded document or a typed description; scores the strength of an existing listing against AWS Marketplace standards; and returns field-level recommendations to improve quality and buyer discoverability before publishing. A brand voice or style guide can be uploaded and is used as a guardrail on the wording it generates.

Who it is forA seller with a listing to write, or an existing listing that buyers are not finding.

What it does not say

  • AWS states it publishes nothing: the seller reviews the content, copies it into the listing page, and chooses when to publish.
  • AWS states that listings created or updated this way go through the same AWS Marketplace product review as listings written by hand.
  • AWS documents access as requiring the AWSPartnerCentralFullAccess permission.
  • AWS documents upload limits of 3 files per message and 5 files per listing, 4.5 MB per document and 3.75 MB per image, and states that PowerPoint is not supported and should be converted to PDF.
  • AWS states uploaded files are stored in a seller-scoped location, are not used to train models, and are not shared with other sellers.
  • The same capabilities are documented as reachable programmatically through the Partner Central agents MCP Server.

Session traceability and the Sandbox catalog

AWS Partner Central API Reference

Every AI-generated insight is returned with a session id, and the session can be read back with the documented getSession tool. AWS also documents a Sandbox catalog: an isolated environment for testing workflows before touching production partner data.

Who it is forAnyone who has to evidence what an agent actually did, rather than repeat what it said it did.

What it does not say

  • AWS states sessions expire 48 hours after creation. Evidence that has to outlive that window has to be captured, not left in the session.
  • The Sandbox catalog is a separate catalog value on the call, not a separate endpoint.
Read athttps://docs.aws.amazon.com/partner-central/latest/APIReference/mcp-getting-started.htmlAWS Partner Central API Reference · read 16 August 2026