# Meltwater — API Agent Score

> Score: 58/100 (Grade: D) | Domain: meltwater.com | Rubric: 1.0.0 | Checked: July 29, 2026

Meltwater scored 58/100 (D), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/meltwater)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 58/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 76/100 (B)
- Agent Discovery: 85/100 (A)
- Agent Understanding: 52/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — security.txt valid at https://meltwater.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [pass] Example coverage — Code samples present on 1/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 0%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://developer.meltwater.com/guides/getting-started/overview/ (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 1/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 15 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (meltwater/aws-configuration-fetcher, 45 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap present (162 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 71%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 20 sampled pages — likely a CSR-only docs site. Investigated: docs 0%.
- [fail] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 0% (threshold 35% for full credit).
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Meltwater's API program shows solid discoverability fundamentals but is being held back by two critical gaps that directly affect partner and agent success: the API contract lacks the schema depth agents need to build against confidently, and the broader documentation layer is missing the machine-readable context, structured data, and consistent descriptions that allow AI agents to parse and act on your APIs reliably. Fixing schema coverage and agent-facing documentation should be the immediate priority, followed by making the API executable so partners reach a working integration in minutes rather than days.