# Chronogolf — API Agent Score

> Score: 53/100 (Grade: D) | Domain: chronogolf.com | Rubric: 1.0.0 | Checked: August 25, 2026

Chronogolf scored 53/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 70/100 (B)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 51/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples appear on 1 of 1 sampled docs pages across 1 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt found at /.well-known/security.txt or /security.txt, so there's no machine-readable security contact for agents or researchers. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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] Self-service developer portal — Self-service signup available at https://www.chronogolf.com/register?returnUrl=https%3A%2F%2Fwww.chronogolf.com%2F, but no free tier or sandbox is documented, so an agent may hit a paywall before the first call. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples appear on 1 of 1 sampled docs pages across 1 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [warn] Changelog published — Newest official SDK activity 336 days ago — drifting from the contract. Investigated: sdk 50%.
- [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%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/partner-api_chronogolf, 22 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://partner-api.docs.chronogolf.com/llms.txt, https://partner-api.docs.chronogolf.com/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 57%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 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.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [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] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Chronogolf's partner API program shows solid fundamentals in versioning and docs reachability, but partners and their AI agents face three compounding barriers: there is no machine-readable front door for agent discovery (no llms.txt, no structured metadata, no AGENTS.md), no runnable starting point for a first successful call, and no security contact for responsible disclosure. Prioritizing agent discoverability and a runnable onboarding path will unlock self-serve partner activation; the security hygiene gaps should close in parallel to meet enterprise partner requirements.