# Ktemia — API Agent Score

> Score: 86/100 (Grade: A) | Domain: ktemia.com | Rubric: 1.0.0 | Checked: November 14, 2026

Ktemia scored 86/100 (A), classified "ai-ready".

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

## Summary

- Overall: 86/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 100/100 (A+)
- Agent Discovery: 86/100 (A)
- Agent Understanding: 92/100 (A+)
- Agent Usability: 70/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — The request body of POST /flights/search, POST /hotels/search, POST /cars/search has a structured shape (more than 5 top-level fields, or a nested object / array-of-objects field), which is harder for an agent to fill correctly. Investigated: spec 83%.
- [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%, wellknown 100%.
- [pass] Example coverage — 86% of parameters and responses (88 of 102) include example values, grounding an agent in real payload shapes. Investigated: spec 100%, docs 100%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://app.ktemia.com/ (client-rendered, so its contents couldn't be classified); free tier or sandbox is documented in pricing/docs. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://www.ktemia.com/docs/getting-started/ includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples appear on 2 of 19 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations and parameters carry substantive descriptions (14 of 14 ops, 29 of 29 params), the main semantic cue an agent relies on. Investigated: spec 100%.
- [pass] Changelog published — changelog is documented on the docs site at https://www.ktemia.com/docs/changelog/, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/ktemia_api, 258 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/22 pages return markdown). Investigated: docs 75%.
- [warn] 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 72%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 6 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations (14 of 14) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 6 of 22 pages have substantive content differences between markdown and HTML (avg 12% missing). Investigated: docs 82%.
- [pass] Agent instructions file (AGENTS.md) — Agent instructions file (AGENTS.md) found at https://ktemia.com/AGENTS.md. Investigated: wellknown 100%.
- [pass] Docs structured data — Machine-readable JSON-LD Article markup on 18 of 19 assessed pages (95%), with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 11% (threshold 35% for full credit).

### Agent Usability

- [pass] Idempotency documented — 100% of mutating operations (3 of 3) document idempotency, so an agent's retries won't create duplicates. Investigated: spec 100%, docs 100%.
- [pass] Rate-limit signaling — Documents 3 distinct rate-limit response headers, so an agent can back off before getting throttled. Investigated: spec 100%, docs 100%.
- [fail] Sandbox separation — None of the 1 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Ktemia's API program performs strongly across contract quality, documentation discoverability, and agent understanding — partners and their agents can find and read the API surface with confidence. The two areas that need immediate attention are safe integration and runnable truth: there is no sandbox or test environment, forcing every partner interaction — including AI agent-driven ones — directly into production, and there is no publicly executable collection agents can use to verify integration patterns without guesswork. Closing these two gaps will meaningfully lower partner integration risk and compress the time from first API call to a working, production-ready workflow.
