# Solcast — API Agent Score

> Score: 71/100 (Grade: B) | Domain: solcast.com.au | Rubric: 1.0.0 | Checked: October 1, 2026

Solcast scored 71/100 (B), classified "partially-ready".

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

## Summary

- Overall: 71/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 63/100 (C)
- Agent Understanding: 84/100 (A)
- Agent Usability: 52/100 (D)

## Check Results

### API Design

- [pass] Schema coverage & depth — 166/166 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 75%.
- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://docs.solcast.com.au/docs/authentication, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — The API sets a version ("1.0.0") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — Only 0% of parameters and responses (0 of 394) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://solcast.com/forecast-solar-irradiance-data (client-rendered, so its contents couldn't be classified); free tier or sandbox is documented in pricing/docs. Investigated: docs 100%.
- [pass] Description completeness — Only 45% of operations and parameters have descriptions (0 of 4 ops, 20 of 22 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 100%.
- [pass] Changelog published — changelog is documented on the docs site at https://docs.solcast.com.au/docs/changelog, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 3 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (bjreplay/ha-solcast-solar, 590 snippets). Investigated: docs 100%, sdk 92%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 17 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 0%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, spec 50%, sdk 50%.
- [pass] Operation purpose clarity — Read/write classification is partial: 8/8 classified (2 read, 6 write). Investigated: sdk 100%, spec 50%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 3 assessed pages (3 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 50%.
- [warn] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 25%, docs 25%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 19) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Pagination documented & consistent — The 6 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: spec 0%, docs 0%.

## Executive Summary

Solcast's API Design is a genuine strength — the machine-readable contract is clean and gives partners and their agents a solid foundation to build against. However, two areas are undermining partner self-serve success: agents and answer engines cannot discover or fully consume Solcast's documentation without scraping, and once partners do land, there is no guided path to a first working call — no quickstart, no code samples, and no safeguards against duplicate writes from agent retries. Prioritising discoverability and onboarding infrastructure first will unlock self-serve partner growth; closing the reliability gaps (idempotency, pagination) will make those integrations production-safe.