Ktemiaktemia.com

ScoredNov 14, 2026, 03:40 PM

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.

API DesignA clean, typed, well-governed API contract agents can reason about3 pass2 warn0 fail91A+
SignalPointsFindingsRationale
passAuth declared & discoverablevia spec25/25Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.Agents can only call an API when they can determine its auth posture — a declared scheme, or an explicit statement that none is required.
warnSchema coverage & depthvia spec20.8/25The 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%.
Fix: Flatten the request body, or document each field's shape with a worked example.
Typed, complete request/response schemas are what make agent function-calling possible.
warnMachine-readable, versioned contractvia spec18.8/25The 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%.
Fix: Pick a versioning scheme (URL path /v1/, Accept: application/vnd.x+json, or a version header) and apply it consistently.
A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
passSecurity & governance hygienevia spec15/15No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 100%.No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
passExample coveragevia spec10/1086% of parameters and responses (88 of 102) include example values, grounding an agent in real payload shapes. Investigated: spec 100%, docs 100%.Examples carry shape semantics schemas under-specify — for humans and agents alike.
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples5 pass0 warn0 fail100A+
SignalPointsFindingsRationale
passSelf-service developer portalvia docs29/29Signup 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%.A first call without a human in the loop — self-serve credentials, a free tier, or an API that needs none.
passQuickstart presentvia docs25/25Quickstart at https://www.ktemia.com/docs/getting-started/ includes a runnable first-call code sample. Investigated: docs 100%.A quickstart is the fastest path from landing page to first successful call.
passCode samples in docsvia docs18/18Code samples appear on 2 of 19 sampled docs pages across 2 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.Multi-language samples shorten time-to-first-call.
passDescription completenessvia spec15/15100% 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%.Complete descriptions are the context humans and agents need to use endpoints.
passChangelog publishedvia spec13/13changelog 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%.A published changelog lets partners track changes without surprise.
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs2 pass2 warn0 fail86A
SignalPointsFindingsRationale
passRegistry & SDK presencevia docs28/28Indexed on Context7 (websites/ktemia_api, 258 snippets). Investigated: docs 100%, sdk 0%, cli 0%.Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
warnDocs reachable, not hard auth-gatedvia docs22.5/30Server ignores Accept: text/markdown header (0/22 pages return markdown). Investigated: docs 75%.Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
warnllms.txt present, valid & comprehensivevia docs21.6/30No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 72%.
Fix: Publish a concatenated, agent-readable copy of your documentation at /llms-full.txt on your docs site.
A valid, comprehensive llms.txt is the machine-readable entry point for agents.
passCrawlable / AEOvia wellknown12/12robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs4 pass2 warn0 fail92A+
SignalPointsFindingsRationale
passMachine-readable errors (RFC 9457)via docs28/28Documents 6 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
passOperation purpose clarityvia spec25/25100% 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%.Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
warnAgent-navigable, token-efficient docsvia docs17.9/226 of 22 pages have substantive content differences between markdown and HTML (avg 12% missing). Investigated: docs 82%.Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
passAgent instructions file (AGENTS.md)via wellknown10/10Agent instructions file (AGENTS.md) found at https://ktemia.com/AGENTS.md. Investigated: wellknown 100%.An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
passDocs structured datavia docs8/8Machine-readable JSON-LD Article markup on 18 of 19 assessed pages (95%), with dateModified present. Investigated: docs 100%.Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
warnDescription consistency across surfaces2.3/7Mean pairwise description similarity across 2 surfaces (spec, docs) is 11% (threshold 35% for full credit).
Fix: Align the API description across spec, docs, and SDK so an agent reading any one surface gets the same story.
Every surface tells the same story about what the product is.
Agent UsabilityAgents have the context to use your APIs reliably, not just find them2 pass0 warn2 fail70B
SignalPointsFindingsRationale
passIdempotency documentedvia spec27/27100% of mutating operations (3 of 3) document idempotency, so an agent's retries won't create duplicates. Investigated: spec 100%, docs 100%.Documented idempotency lets agents retry safely.
passRate-limit signalingvia spec22/22Documents 3 distinct rate-limit response headers, so an agent can back off before getting throttled. Investigated: spec 100%, docs 100%.Machine-readable rate-limit headers let agents throttle adaptively.
failSandbox separationvia spec0/20None 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%.
Fix: Add a sandbox server in spec.servers[] with visually distinguishable test credentials.
An isolated environment lets agents exercise destructive operations safely.
failRunnable collection with test scriptsvia platform0/9No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
Fix: Publish at least one public Postman workspace and link it from your developer portal so agents can use Run-in-Postman.
A public, maintained collection with assertions is runnable truth agents validate against.
naPagination documented & consistent—/22No surface produced evidence for this capability in this run.Consistent, documented pagination lets agents traverse collections.
Resources Discovered

The public resources we found for Ktemia — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hintsContext7 (258)
APIs analyzed1 — Ktemia API
Want to improve your results?