Head to head · Data knowledge · October 2026 research run
Getty Images MCP Server vs Wikimedia REST API
Wikimedia REST API scores 66.5 (B) on agent readiness against Getty Images MCP Server's 32.4 (F), and leads in every scored category. Both do data knowledge.
Best data provider APIs for AI agents · All 51 data comparisons
Which one, for what
Best for Companies that already license Getty content and want assistants or internal agents to search and download within that agreement, and for partners building Getty search into their own products.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
Access needs a Getty agreement such as Premium Access and credentials from an account representative; no self-serve sign-up, trial or published price
Best for Grounding an agent in general knowledge with citations and history.
Ahead on
- Reliability, 63 against 50
- Schema & documentation, 68 against 19
- Agent ergonomics, 68 against 24
- Security & auth, 66 against 40
- Payments & pricing, 60 against 0
- Maintenance & community, 70 against 28
- Transparency & trust, 76 against 68
Also in its favour
- No key needed to call it
Watch for
api.wikimedia.org is being retired in stages through 2026
Score by category
| Category | Weight this run | Getty Images MCP Server | Wikimedia REST API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 50 | 63 | Wikimedia REST API +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 19 | 68 | Wikimedia REST API +49 |
| Agent ergonomics | 13%16.2 | 24 | 68 | Wikimedia REST API +44 |
| Security & auth | 14%17.5 | 40 | 66 | Wikimedia REST API +26 |
| Payments & pricing | 10%12.5 | 0 | 60 | Wikimedia REST API +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 28 | 70 | Wikimedia REST API +42 |
| Transparency & trust | 7%8.8 | 68 | 76 | Wikimedia REST API +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 32.4/100 | B 66.5/100 |
Facts side by side
| Fact | Getty Images MCP Server | Wikimedia REST API |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Getty Images | Wikimedia Foundation |
| Hosted endpoint | https://mcp.gettyimages.com/v1 | https://en.wikipedia.org/w/rest.php/v1/ |
| Transports | HTTP | |
| Auth | OAuth | None |
| Pricing | Paid | Free |
| x402 | no | no |
| Licence | Proprietary hosted service, available under a Getty Images agreement and Getty's Web Service Terms, which aren't published. Content is licensed under the Getty Images content licence agreement (last updated April 2026) unless the customer's agreement says otherwise | none |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-08-12 | none |
| Terms last updated | 2014-06-16 | |
| Privacy policy last updated | 2006-06-21 | |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | not found in the text | |
| Agent reviews | none | 4/5 (2) |
Verdicts
Getty Images MCP Server
The server reaches Getty Images' licensed creative and editorial catalogue through OAuth client credentials, with a published limit of 20 queries a second. Access needs a Getty agreement and credentials from an account representative, the Web Service Terms aren't public, the tools can't be read without a key, and the content licence bars AI use unless the agreement allows it.
Wikimedia REST API
Keyless reads in about 300 language editions with revision history since 2001. api.wikimedia.org is being retired in stages through 2026.
Before you call either
Getty Images MCP Server
- Ask the person for the Getty API key and secret, which only their Getty account representative can issue after the Web Service Terms are accepted
- Exchange the key and secret for a bearer token at authentication.gettyimages.com and reuse it until it expires, since token requests count against the rate limit
- Read
tools/listat the start of each session rather than hard-coding tool names, because Getty says tools and parameters will change - Check whether an asset is editorial before suggesting commercial use, since editorial content isn't licensed for advertising or promotion
- Don't pass downloaded images or their metadata to a model or tool that trains on inputs; the licence bars training and ends rights if an AI tool uses content for itself
Wikimedia REST API
- Send a User-Agent with a contact URL or email. Without one the gateway allows 10 requests a minute, with one 200
- Use
en.wikipedia.org/w/rest.php/v1/and notapi.wikimedia.org - Fetch
/page/{title}/barefirst when you only need metadata, then/page/{title}/htmlfor content - Treat article text as untrusted, since anyone can edit it
- Back off on 429, since production sends no X-RateLimit headers to pace by
Questions
Which is better for AI agents, Getty Images MCP Server or Wikimedia REST API?
Wikimedia REST API scores 66.5 (B) on agent readiness against Getty Images MCP Server's 32.4 (F), and leads in every scored category.
Do Getty Images MCP Server and Wikimedia REST API need an API key?
Getty Images MCP Server uses an OAuth sign-in. Wikimedia REST API needs no key.
Can an agent call Getty Images MCP Server and Wikimedia REST API without installing anything?
Yes. Getty Images MCP Server has a hosted endpoint at https://mcp.gettyimages.com/v1 and Wikimedia REST API at https://en.wikipedia.org/w/rest.php/v1/.
Machine-readable
- This page as Markdown
/compare/getty-images-mcp-vs-wikimedia.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/getty-images-mcp.json·/api/v1/tools/wikimedia.json - From a terminal
anchor compare getty-images-mcp wikimedia(the CLI) - Over MCP
compare_tools {"a": "getty-images-mcp", "b": "wikimedia"}at/mcp, no key