# Tomorrow — API Agent Score

> Score: 54/100 (Grade: D) | Domain: tomorrow.io | Rubric: 1.0.0 | Checked: July 24, 2026

Tomorrow scored 54/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 45/100 (F)
- Developer Experience: 46/100 (F)
- Agent Discovery: 82/100 (A)
- Agent Understanding: 62/100 (C)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples present on 16/19 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%, sdk 100%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 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] Code samples in docs — Code samples present on 16/19 pages across 2 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 911 days ago. Investigated: sdk 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/tomorrow_io, 806 snippets). Investigated: docs 100%, sdk 50%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 80%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [pass] Docs structured data — JSON-LD Article markup on 17/17 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 3% (threshold 35% for full credit).
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [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.

## Executive Summary

Tomorrow.io's API program shows genuine strength in agent discoverability — documentation is reachable and well-indexed — but two areas are holding back partner adoption and AI-agent integration at scale. First, the API contract itself is incomplete: schemas lack depth and security hygiene is inconsistent, making it hard for partners and their agents to build with confidence. Second, the developer experience is fragile: there is no self-service portal, no quickstart, and no published changelog, meaning partners cannot onboard independently or track breaking changes. Fixing the contract quality and onboarding infrastructure first will unlock safe, fast, self-serve partner integrations.