Verify before you commit
Use this page to sanity-check Ky V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 27, 2026
Freshness
Updated 2026-03-27T05:48:07.867+00:00
Mar 27, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 8.3 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 8.1 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 8.2 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Ky provides a clean API over the native Fetch API with the practical additions teams actually need: automatic JSON parsing, retry with backoff, timeout, and request/response hooks. It is a lightweight Axios alternative for projects that want to stay close to native fetch. Confidence is docs-derived.
The API covers ky.get(), ky.post(), etc. with options for json (auto-serialize body + set Content-Type), retry (number or config object), timeout (ms), and hooks (beforeRequest, afterResponse, beforeRetry). TypeScript types are built in.
Ky is a local library with no platform auth. Auth is implemented via beforeRequest hooks (inject Authorization headers) or per-request headers. No external services.
Operationally, Ky is small (~2KB) and leverages native Fetch, making it suitable for edge environments and browser bundles where Axios would add overhead. Retry handling covers network errors and specified HTTP status codes.
Documentation is GitHub-README-level but sufficient for the focused API. Developer experience is good for teams that want the native fetch mental model with practical HTTP client features added on top.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
8.2 / 10.0
No alternatives captured yet.