Guardian Open Platform vs NYT Developer APIs: full comparison for 2026
Quick verdict
Guardian Open Platform (3.8/5) edges ahead of NYT Developer APIs (3.5/5) overall. Guardian Open Platform is the better choice for Students, researchers and non-commercial apps. NYT Developer APIs is the stronger option for historians and students researching Times coverage. The right pick depends on your budget, how much history you need and whether you need full text.
Guardian Open Platform vs NYT Developer APIs: head-to-head summary
| Criterion | Guardian Open Platform | NYT Developer APIs |
|---|---|---|
| Founded | 1821 | 1851 |
| HQ | London, UK | New York, USA |
| Team size | 1,000+ (Guardian Media Group) | 5,000+ |
| Rating | 3.8 / 5 | 3.5 / 5 |
| Primary differentiator | Free full article text with editorial tags from a major publisher | Searchable metadata for the full Times archive since 1851 |
| Pricing model | Free developer key; commercial licence on request | Free developer keys |
| Entry price | Free | Free |
| Formats & SDKs | REST API, JSON | REST API, JSON |
| Typical uses | Research & academia, News & content apps, AI & LLM apps | Research & academia, News & content apps |
Guardian Open Platform vs NYT Developer APIs: overview
Guardian Open Platform
The Guardian's Open Platform gives developers the same content API that runs the Guardian's own sites, with full article bodies, tags and sections going back to 1999. A free developer key is commonly reported at about 5,000 calls a day and 12 calls a second, and it is meant for non-commercial projects. Commercial use needs a separate agreement with Guardian News & Media. Clean, consistent tagging has made it a favourite for teaching and research, though you only ever get one publisher.
NYT Developer APIs
The New York Times, founded in 1851, offers free developer APIs that include Article Search, Archive, Top Stories, Most Popular and Books. Article Search and Archive reach back to 1851 but return headlines, abstracts, keywords and links, while full text stays behind the paywall. Commonly cited limits are 4,000 requests a day and 10 a minute, under terms aimed at non-commercial use. The Times sued OpenAI and Microsoft over AI training in December 2023, so using its content in AI systems without a licence is a bad idea.
Features: Guardian Open Platform vs NYT Developer APIs
| Capability | Guardian Open Platform | NYT Developer APIs |
|---|---|---|
| Full article text | ✓ | ✗ |
| Historical archive | ✓ | ✓ |
| NLP enrichment | ✗ | ✗ |
| Story/event clustering | ✗ | ✗ |
| Licensed publisher content | ✗ | ✗ |
| Streaming or webhooks | ✗ | ✗ |
| Free access | ✓ | ✓ |
Formats and SDKs: Guardian Open Platform vs NYT Developer APIs
| Format / SDK | Guardian Open Platform | NYT Developer APIs |
|---|---|---|
| REST API | ✓ | ✓ |
| Python SDK | N/A | N/A |
| Node.js SDK | N/A | N/A |
| Webhooks | N/A | N/A |
| WebSocket | N/A | N/A |
| MCP server | N/A | N/A |
| S3/bulk delivery | N/A | N/A |
| BigQuery | N/A | N/A |
Pricing comparison: Guardian Open Platform vs NYT Developer APIs
| Criterion | Guardian Open Platform | NYT Developer APIs |
|---|---|---|
| Entry price | Free | Free |
| Pricing model | Free developer key; commercial licence on request | Free developer keys |
| Access models | Free tier, Enterprise contract | Free tier |
| Price transparency | Public price | Public price |
| Price tier | Free | Free |
Who each API suits: Guardian Open Platform vs NYT Developer APIs
| Dimension | Guardian Open Platform | NYT Developer APIs |
|---|---|---|
| Buyer type | Individuals to enterprise | Individuals to enterprise |
| Typical uses | Research & academia, News & content apps, AI & LLM apps | Research & academia, News & content apps |
| Example use cases | Teaching data journalism or NLP with real articles. Research on UK and international coverage over time. | Historical research on how a topic was covered. Teaching API basics with a well-known source. |
| How you get access | Free tier | Free tier |
Guardian Open Platform vs NYT Developer APIs: pros and cons
| Guardian Open Platform | |
|---|---|
| + | Full article bodies at no cost, which is unusual for a major newspaper |
| + | Consistent tags and sections make filtering easy |
| + | An archive going back to 1999 |
| + | A stable, well-documented API that the Guardian uses itself |
| - | Single publisher, so coverage reflects one editorial line |
| - | Commercial use requires negotiating a licence |
| NYT Developer APIs | |
|---|---|
| + | Archive metadata back to 1851, unmatched for historical research |
| + | Free keys with clear, published rate limits |
| + | Top Stories and Most Popular endpoints make quick demos |
| - | No full article text |
| - | Non-commercial terms and an active legal stance against unlicensed AI use |
| - | Single publisher |
Who should choose Guardian Open Platform?
A typical fit: teaching data journalism or NLP with real articles.
Free full article text with editorial tags from a major publisher. Paid access starts at Free. Typical uses: Research & academia, News & content apps, AI & LLM apps.
Who should choose NYT Developer APIs?
A typical fit: historical research on how a topic was covered.
Searchable metadata for the full Times archive since 1851. Paid access starts at Free. Typical uses: Research & academia, News & content apps.
Decision matrix: Guardian Open Platform vs NYT Developer APIs
| Your situation | Recommended choice |
|---|---|
| You want to start free before paying | Both |
| Your budget is at the lower end | Guardian Open Platform |
| You need full article text in the response | Guardian Open Platform |
| You need years of historical news | Both |
| You need licensed premium or wire content | Neither; look at Factiva, AP or LexisNexis |
| You are wiring news into an LLM agent | Both work through plain REST calls |
Use case fit: Guardian Open Platform vs NYT Developer APIs
| Use case | Guardian Open Platform fit | NYT Developer APIs fit | Winner |
|---|---|---|---|
| Research & academia | Strong | Strong | Both equally |
| News & content apps | Strong | Strong | Both equally |
| AI & LLM apps | Strong | Limited | Guardian Open Platform |
Verdict: Guardian Open Platform vs NYT Developer APIs
Guardian Open Platform (3.8/5) is the stronger overall choice as a news data source. Free full article text with editorial tags from a major publisher.
NYT Developer APIs (3.5/5) is worth a look if you need teaching API basics with a well-known source. If your situation matches that, NYT Developer APIs is a competitive option.
Related comparisons
Guardian Open Platform vs NYT Developer APIs FAQ
Is Guardian Open Platform better than NYT Developer APIs?
Guardian Open Platform (3.8/5) scores higher overall, but "better" depends on your use case. Guardian Open Platform's strongest advantage: full article bodies at no cost, which is unusual for a major newspaper. NYT Developer APIs's strongest advantage: archive metadata back to 1851, unmatched for historical research.
How do Guardian Open Platform and NYT Developer APIs differ in pricing?
Guardian Open Platform: free developer key; commercial licence on request, with paid access from Free. NYT Developer APIs: free developer keys, with paid access from Free. Both offer some free access for testing.
Which is better for enterprise: Guardian Open Platform or NYT Developer APIs?
Guardian Open Platform sells enterprise contracts with negotiated volume and SLA terms. Neither carries licensed publisher content, so check copyright terms before republishing anything.
What are the main differences between Guardian Open Platform and NYT Developer APIs?
What sets Guardian Open Platform apart: free full article text with editorial tags from a major publisher. What sets NYT Developer APIs apart: searchable metadata for the full Times archive since 1851. They also differ on entry price (Free vs Free) and typical uses (Research & academia, News & content apps vs Research & academia, News & content apps).
Verify all details directly with each API before making a decision.