# Tapclicks — API Agent Score

> Score: 55/100 (Grade: D) | Domain: tapclicks.com | Rubric: 1.0.0 | Checked: July 30, 2026

Tapclicks scored 55/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 93/100 (A+)
- Developer Experience: 58/100 (D)
- Agent Discovery: 49/100 (F)
- Agent Understanding: 58/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="2.6.27") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: docs 100%, spec 50%, wellknown 0%.
- [warn] Schema coverage & depth — 86% of operations have documented schemas (target 95%+). Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 86% example coverage across params + responses. Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.tapclicks.com/password-protected?page=82; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 97% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — No changelog URL or mention found in spec metadata. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [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 discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.tapclicks.com/llms.txt, https://developers.tapclicks.com/docs/llms.txt). Investigated: docs 0%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 5 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 71%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 5% (threshold 35% for full credit).
- [fail] Operation purpose clarity — 0% of operations are agent-inferable. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 2 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — No sandbox/test server declared across 1 server entries; no test-key prefixes documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Tapclicks has a strong API design foundation, but the partner program is held back by two critical gaps: agents and partners cannot reliably discover or understand the APIs without human hand-holding, and the operational signals agents need to run real workflows — rate-limit headers, pagination contracts, idempotency guarantees, sandbox separation, and runnable examples — are entirely absent. Prioritizing machine-readable discoverability and operational reliability will unblock both self-serve partner onboarding and AI-agent integration at scale.