Head to head · Ad reporting · October 2026 research run

Microsoft Advertising API vs X Ads API

Microsoft Advertising API scores 60.3 (C) on agent readiness against X Ads API's 57.3 (C), and leads in 5 of 7 scored categories. X Ads API leads on reliability. Both do ad reporting.

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

Which one, for what

Microsoft Advertising API C

Good for Agents that manage or report on Microsoft Advertising accounts, including Google Ads imports.

Ahead on

  • Schema & documentation, 79 against 64
  • Security & auth, 60 against 48
  • Payments & pricing, 30 against 20

Watch for

Call-rate limits carry no numbers. The docs describe a 60-second sliding window, and call the Bulk and Reporting limits internal and subject to change

X Ads API C

Good for An agent that manages or reports on X campaigns for an advertiser with an approved developer app, especially through the MCP server, where scopes separate reads from writes and writes start paused.

Ahead on

  • Reliability, 75 against 60

Watch for

No OpenAPI file covers the Ads API. The published file (version 2.170, 178 paths) describes api.x.com only

Score by category

CategoryWeight this runMicrosoft Advertising APIX Ads APIEdge
Reliability16%206075X Ads API +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27964Microsoft Advertising API +15
Agent ergonomics13%16.26362Microsoft Advertising API +1
Security & auth14%17.56048Microsoft Advertising API +12
Payments & pricing10%12.53020Microsoft Advertising API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86163X Ads API +2
Transparency & trust7%8.86462Microsoft Advertising API +2
Negative events≤1500
Total60.3 · C57.3 · C

Facts side by side

FactMicrosoft Advertising APIX Ads API
KindHTTP APIHTTP API
VendorMicrosoftX Corp.
Hosted endpointhttps://campaign.api.bingads.microsoft.com/CampaignManagement/v13https://ads-api.x.com/mcp
TransportsHTTPHTTP
AuthOAuthOAuth
PricingFreeFree
x402nono
LicenceProprietary service. The .NET, Java, Python and PHP SDKs are MITProprietary service under the X Developer Agreement and its incorporated Developer Policy
Tools exposed7none
Read-only variant documentedyesyes
llms.txtnoyes
Last release2026-09-292026-09-17
Terms last updatedcouldn't be read2026-04-27
Privacy policy last updated2026-09-01couldn't be read
Customer content may train modelsyesnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readyes
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity128 stars, 19k PyPI/wknone

Verdicts

Microsoft Advertising API

Version 13 covers campaigns, budgets, audiences, ads and reports over REST with JSON, with a sandbox that needs no payment method and four official SDKs. Call-rate limits are unpublished, no public OpenAPI file or idempotency key was found, and one OAuth scope covers every operation. The SOAP interface retires on 31 January 2027.

X Ads API

Rate limits are published per endpoint type, a sandbox host never serves ads, and the X Ads MCP server has separate read and write scopes and creates campaigns paused. The REST API needs OAuth 1.0a signing and an approved app, no OpenAPI file covers it, and the official Python and Ruby SDKs were last released in May 2022.

Before you call either

Microsoft Advertising API

  1. Build and test against the sandbox hosts (*.api.sandbox.bingads.microsoft.com) with developer token BBD37VB98. Sandbox and production credentials are separate
  2. Send Authorization: Bearer <token>, DeveloperToken, CustomerId and CustomerAccountId on REST calls. Use the account ID, never the eight-character account number
  3. Create campaigns with Status set to Paused, then read them back before activating. No validate-only mode was found
  4. On error 117 (CallRateExceeded) wait 60 seconds. On Bulk error 4204 wait up to 15 minutes
  5. Read PartialErrors on every add, update and delete. A call can succeed for some items and fail for others

X Ads API

  1. Build against https://ads-api-sandbox.x.com/12/ first. Create a test account with POST accounts and a funding instrument there before touching a live account
  2. On HTTP 429 wait until the time in x-rate-limit-reset. On 503 wait for retry-after. The docs say apps that ignore these can be throttled or lose access without notice
  3. Read the account-level limit from x-account-rate-limit-* when present and use x-rate-limit-* only when it is absent
  4. For a read-only MCP session request ads.read offline.access only. Without offline.access the token expires in about two hours with no refresh
  5. Page with count (1 to 1,000, default 200) and cursor until next_cursor is null. Analytics endpoints page by time range instead, and with_total_count cannot be combined with cursor

Questions

Which is better for AI agents, Microsoft Advertising API or X Ads API?

Microsoft Advertising API scores 60.3 (C) on agent readiness against X Ads API's 57.3 (C), and leads in 5 of 7 scored categories. X Ads API leads on reliability.

Do Microsoft Advertising API and X Ads API need an API key?

Both use an OAuth sign-in.

Can an agent call Microsoft Advertising API and X Ads API without installing anything?

Yes. Microsoft Advertising API has a hosted endpoint at https://campaign.api.bingads.microsoft.com/CampaignManagement/v13 and X Ads API at https://ads-api.x.com/mcp.

Other comparisons with Microsoft Advertising API or X 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.