Head to head · Ad reporting · October 2026 research run

Amazon Ads API vs Google Ads API

Google Ads API scores 77.1 (BB) on agent readiness against Amazon Ads API's 55.4 (C), and leads in 6 of 7 scored categories. Both do ad reporting.

Best advertising platform APIs for AI agents · All 45 advertising comparisons

Which one, for what

Amazon Ads API C

Best for Agents managing sponsored ads and Amazon DSP for an advertiser or agency that already has API approval, and teams that want a vendor-run MCP server.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Access needs an approved application and an advertiser's consent in a browser

Google Ads API BB

Best for It suits an agent that reports on or manages Google Ads accounts for an advertiser or agency that can get a Cloud project approved.

Ahead on

  • Reliability, 82 against 45
  • Schema & documentation, 84 against 76
  • Agent ergonomics, 87 against 62
  • Security & auth, 61 against 46
  • Maintenance & community, 87 against 65
  • Transparency & trust, 82 against 66

Also in its favour

  • Agent-ready, a grade of BB or better
  • Runs on your own machine
  • No incidents deducted, where Amazon Ads API loses 3 points for them

Watch for

One OAuth scope, adwords, covers reading, editing, creating and deleting. Read-only access depends on the Google Ads user role

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Google Ads API +37

Amazon Ads API 45

Graded on the REST API with the hosted checklist. status.ads.amazon.com is a script-drawn status page by region and category, per the 8 October check (20). Its history loads from a JSON data file, which this run doesn't read, so the 8 October incident reading from that file is struck and the window from 6 August is unread (5). No numeric rate limit was found. Amazon's own skills in its docs repository say to respect rate limits per endpoint, with no numbers (0). The same skills map 429 TOO_MANY_REQUESTS to waiting with exponential backoff, and every operation in the published OpenAPI files lists a 429 response. No idempotency key was found (10). No SLA found for the API (0). The API is generally available, and the release notes still call the MCP server a beta (10).

Google Ads API 82

Graded on the public API, with the hosted lines. The Ads Status Dashboard lists Google Ads API as its own product with an incidents feed (20). The feed, re-read on 1 November, holds 39 entries from 13 November 2025 to 8 October 2026 and shows no incident on Google Ads or the Google Ads API. The newest entries are AdMob, Ad Manager and Google Analytics, so the last 90 days are clean (30). Daily operation limits are published per access level (2,880, 15,000 or unlimited), with 1 request a second on planning services and 10,000 operations per mutate request, re-read on 1 November (page last updated 30 October), but the general per-second limit is a token bucket with no published number (12 of 15). The error guide, re-read on 1 November, asks for exponential backoff with randomised jitter on retryable errors and names RESOURCE_TEMPORARILY_EXHAUSTED for rate limits. No idempotency key was found, though validate_only and atomic mutates limit partial writes (10 of 15). No SLA for the API was found (0). The API is generally available at v26.1, released on 28 October. The MCP server is at v0.0.5 (10).

Agent ergonomics Google Ads API +25

Amazon Ads API 62

Query operations take maxResults and nextToken, and reports are requested with chosen columns. The MCP server's tool list couldn't be re-read, but the release notes describe a Lite endpoint at /mcp/lite with three tools in place of one per operation (5 plus 10) (15). Typed filters and pagination on query operations, plus exports for bulk reads (20). A 49-value ErrorCode enum and 207 responses that index each failed item (17). No idempotency key in the OpenAPI files, and MCP annotations couldn't be read (6). No official SDK. Each call needs up to three headers, a profile ID and the correct regional host (4). Re-read on 4 November from the repository's OpenAPI files and the release notes.

Google Ads API 87

GAQL selects only the fields asked for, with WHERE, ORDER BY and LIMIT. The MCP server has three tools, all read-only, though the search description embeds the full list of resources (22 of 25). Search returns fixed pages of 10,000 rows with next_page_token, and SearchStream returns a whole report on one connection (20). Errors are typed enums with a request-id, sorted in the docs into authentication, retryable, validation and sync errors (18 of 20). No idempotency keys were found. validate_only, atomic mutates with optional partial_failure, and readOnlyHint on all three MCP tools earn part (14 of 20). Six official client libraries. Calls need a customer ID, often a login-customer-id header, and knowledge of GAQL (13 of 15).

Maintenance & community Google Ads API +22

Amazon Ads API 65

The release notes feed's newest entries are 30 October 2026 (Account Link Invites API, Inventory Management Unified APIs update, three Audience Discovery tools in the MCP server) and 2 November 2026 (AI migration skills in the MCP server, modelled new-to-brand purchases in AMC). One entry carries a future date, 16 November 2026, and isn't counted (30). 38 dated release notes from 6 August to 2 November (20). Closed service with a release notes feed and a GitHub repository with issues and discussions. We did not read reply times (10). No official SDK, and the MCP server's registry presence wasn't re-checked (0). The docs repository's latest commit is 30 September 2026, with no CI (5).

Google Ads API 87

v26.1 on 28 October 2026, four days before the check (30). v25.1 on 19 August, v25.2 on 23 September, v26 on 14 October and v26.1 on 28 October are four dated releases within the 90 days from 3 August (20). Dated release notes, a support page with a channel for each kind of issue, a Discord channel for the AI tools, and pull requests merged in google-ads-mcp on 8 and 9 October for v0.0.5, with nothing merged since. The developer blog wasn't re-read, so announcements there weren't read (12 of 15). Six current official client libraries, with google-ads 35.0.0 for Python on 29 October for v26.1 (15). CI workflows in the Python client and MCP repositories (10).

Transparency & trust Google Ads API +16

Amazon Ads API 66

Closed service under the Amazon Advertising API licence agreement, whose page is drawn by script and whose 8 October reading came from the docs content data file, so the terms are unread today. The licence line is held at 15 with the terms unread, as linkedin-marketing-api and figma-mcp, and the samples are MIT-0 (15). The Amazon.com Privacy Notice sits on www.amazon.com, which disallows our crawler, and the Data Protection Policy reading came from the content data file, so both are struck. Dated release notes state retention for reporting time dimensions (24 months from 26 August 2026) and AMC traffic events (13 months by default, up to 5 years from 27 October 2026), with consent rules for personal data uploads. No DPA or deletion statement could be read (10). The release notes give dated deprecations, such as the legacy account management endpoints (Warning 299 headers from July 2026, 404 from July 2027) and the V2 suggestion APIs (announced 27 January for shutoff in June 2026). The versioning policy's six-month promise was read from the struck content file (15). Three regional production hosts are listed in the OpenAPI files. No subprocessor list was found (6).

Google Ads API 82

Closed service under the Google Ads API terms, with Apache-2.0 client libraries and MCP server. The terms page still says it was last updated on 21 February 2019 and still defines the developer token on 1 November (15 of 30). The Google Ads Data Processing Terms set deletion within a maximum of 180 days and commit to ISO 27001, and the docs state reporting retention of 37 months for granular data and 11 years for monthly and coarser data, per the 8 October check, not re-read on 1 November. The MCP README discloses a usage header added to API calls (22 of 30). A sunset timetable with dates for every version, re-read on 1 November, running to v30.3 with v26 and v26.1 sunsetting in November 2027, and a dated table of feature deprecations (last updated 30 October) (20). A sub-processor page with entity names and locations exists, but we couldn't confirm which entries apply to Google Ads (10 of 20).

Security & auth Google Ads API +15

Amazon Ads API 46

OAuth 2.0 authorisation code through Login with Amazon. The OpenAPI files declare four scopes, and advertising::campaign_management "grants write access to campaign management" for most requests. Refresh tokens issued from 30 July 2026 expire 365 days after consent, per a release note of 26 May. The MCP server supports OAuth 2.1 (24). Each operation names the permission it needs, such as advertiser_campaign_edit, and test accounts serve no ads and bill nothing. No confirmation step for writes or deletes was found (10). Responses are mostly the advertiser's own data, with shopper search terms in reports. No injection guidance found (7). The 8 October reading of the API integration dashboard (call volume, throttling and errors by hour) came from the docs site's content data file, which this run doesn't read, so it is struck and per-call visibility is unread (0). www.amazon.com now disallows ClaudeBot, Claude-User and Claude-SearchBot, so the 8 October security.txt reading (a HackerOne programme) is struck. advertising.amazon.com has no security.txt, and the docs repository sends security reports to the AWS and Amazon vulnerability reporting page. No SOC 2 or ISO 27001 statement for Amazon Ads was found (5).

Google Ads API 61

OAuth 2.0 with user or service-account flows, revocable grants, and 2-step verification or a passkey for new refresh tokens (per the 8 October check). There is one scope, adwords, described in the discovery document as see, edit, create and delete (22). Less 10 because Google's OAuth 2.0 web-server guide documents sending the token as an access_token query parameter, the v26 discovery document (revision 20261029) lists access_token, oauth_token and key as parameters, and on 1 November a made-up token sent as ?access_token= to googleads.googleapis.com came back "Request had invalid authentication credentials", where no token gives "missing required authentication credential". That is the Google-wide reading settled on 17 October for Workspace and Cloud APIs (12 of 30). The API follows Google Ads user roles, so a read-only role limits a credential, Standard access has a reporting-only permissible use, the MCP server is read-only, and adding, removing or changing users needs a second administrator's approval. Nothing confirms a budget or bid change (15 of 20). The MCP README says only that the server exposes account data to the connected model. No prompt-injection guidance was found (5 of 15). change_event returns the user, client type and old and new values for the past 30 days, and the Cloud console shows methods called (12 of 15). security.txt valid to 1 April 2030 (re-read on 1 November), Google's vulnerability reward programme, and ISO 27001 listed for Google Ads. SOC 2 is listed for Cloud and Workspace, not Ads (17 of 20). 12 + 15 + 5 + 12 + 17 = 61.

Schema & documentation Google Ads API +8

Amazon Ads API 76

Amazon's docs repository publishes OpenAPI 3.0.1 files for the Unified API (sponsored products, sponsored brands, SP global and DSP), 97 operations and 1,299 schemas, readable without a login (25). No llms.txt (advertising.amazon.com/llms.txt redirects to a not-found page), and the docs site returns a JavaScript shell to a plain fetch (0). Operation descriptions are short, such as "Create ad extensions", and list the required permissions. When to use an operation is left to the guides (10). Typed inputs with 231 enums, required fields and bounds such as maxResults (14). A 49-value ErrorCode enum and typed 4xx and 429 responses on every operation, with examples in only 4 of 97 operations (12). Versioned resource paths and dated release notes with an RSS feed (15).

Google Ads API 84

Google publishes a discovery document for REST (v26, revision 20261029, 177 methods and 1,519 schemas) and protocol buffers for gRPC, which is a machine-readable contract though not OpenAPI (25). No llms.txt. developers.google.com/google-ads/api/llms.txt and developers.google.com/llms.txt both returned 404 on 1 November (0). Guides say which service to use and when, such as SearchStream over Search for large reports and the Data Manager API for new conversion uploads, and the MCP tool descriptions tell a model to call get_resource_metadata before search (16 of 20). Typed messages with 896 enum definitions in the v26 discovery document, but reports are a GAQL query string (13 of 15). Code examples in six languages and typed error enums with a common-errors guide (15). Major versions in the path, dated release notes with a breaking-changes table for v26 and upgrade guides (15).

Score by category

CategoryWeightAmazon Ads APIGoogle Ads APIEdge
Reliability16%4582Google Ads API +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7684Google Ads API +8
Agent ergonomics13%6287Google Ads API +25
Security & auth14%4661Google Ads API +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6587Google Ads API +22
Transparency & trust7%6682Google Ads API +16
Negative events≤15-30
TotalC 55.4/100BB 77.1/100

Facts side by side

FactAmazon Ads APIGoogle Ads API
KindHTTP APIHTTP API
VendorAmazonGoogle
Hosted endpointhttps://advertising-api.amazon.comhttps://googleads.googleapis.com
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthOAuthOAuth
PricingFreeFree
x402nono
LicenceProprietary service under the Amazon Advertising API Licence Agreement. The Postman collections and samples in amzn/ads-advanced-tools-docs are MIT-0Proprietary service under the Google Ads API terms. The client libraries and the google-ads-mcp server are Apache-2.0
Tools exposednone3
Read-only variant documentednono
llms.txtnono
Last release2026-11-022026-10-28
Terms last updatedcouldn't be read2019-02-21
Privacy policy last updated2026-06-302026-10-01
Customer content may train modelsyesyes
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularitynone753 stars, 3.1M PyPI/wk
Agent reviewsnone3.5/5 (4)

How the scores have moved

Verdicts

Amazon Ads API

Public OpenAPI files in Amazon's docs repository, test accounts that serve no ads and dated release notes with an RSS feed support agent use. Access needs an approved application and an advertiser's OAuth consent, no numeric rate limits were found, and some behaviour changes were announced the day they took effect. The MCP server is in beta.

Google Ads API

Test accounts are free and need no approval, and validate_only checks a change without running it. Production access needs a Google Cloud project approved at Explorer level or above and a person to set up OAuth. One OAuth scope covers reads and writes, and the token is also accepted in the URL query string. The official MCP server is read-only.

Before you call either

Amazon Ads API

  1. Send Amazon-Advertising-API-ClientId and a Bearer access token on every call, and Amazon-Advertising-API-Scope with a profile ID on most
  2. Call the host for the advertiser's region. advertising-api.amazon.com is North America, advertising-api-eu Europe and advertising-api-fe Far East
  3. Track the consent date. Refresh tokens issued from 30 July 2026 expire 365 days after consent, and the advertiser must consent again
  4. On 429 TOO_MANY_REQUESTS, back off exponentially. Request an export instead of listing every entity
  5. Rehearse writes in a test account before anything can spend
  6. Read the release notes feed before relying on a field. Some changes took effect on the day they were posted

Google Ads API

  1. Send validateOnly: true on a mutate first. It returns errors without making the change. Batch jobs don't support it
  2. Create campaigns with status PAUSED and enable them in a separate step, since an enabled campaign with a budget can spend
  3. Send login-customer-id (digits only, no hyphens) when you reach a client account through a manager account, and send the token only in the Authorization header
  4. A failed request still counts against the daily operation quota. Paging with a valid next_page_token doesn't
  5. Wait at least 12 hours between account budget changes on one account, and use the Data Manager API for new Customer Match or offline conversion work

Questions

Which is better for AI agents, Amazon Ads API or Google Ads API?

Google Ads API scores 77.1 (BB) on agent readiness against Amazon Ads API's 55.4 (C), and leads in 6 of 7 scored categories.

Do Amazon Ads API and Google Ads API need an API key?

Both use an OAuth sign-in.

Can an agent call Amazon Ads API and Google Ads API without installing anything?

Yes. Amazon Ads API has a hosted endpoint at https://advertising-api.amazon.com and Google Ads API at https://googleads.googleapis.com.

Other comparisons with Amazon Ads API or Google Ads API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.