# TikTok — API Agent Score

> Score: 70/100 (Grade: B) | Domain: tiktok.com | Rubric: 1.0.0 | Checked: November 13, 2026

TikTok scored 70/100 (B), classified "partially-ready".

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

## Summary

- Overall: 70/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 89/100 (A)
- Developer Experience: 74/100 (B)
- Agent Discovery: 82/100 (A)
- Agent Understanding: 68/100 (C)
- Agent Usability: 47/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — The MCP server at https://tiktok.api.trendsapi.ai/mcp accepts unauthenticated requests, so an agent knows it needs no credentials. Investigated: mcp 100%, spec 0%, docs 0%.
- [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%.
- [warn] Schema coverage & depth — Only 0% of the 307 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 75%, sdk 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 50%.
- [pass] Example coverage — Only 0% of parameters and responses (0 of 4) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup available at https://www.tiktok.com/signup, with a free tier or sandbox documented — an agent can onboard without contacting sales. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://developers.tiktok.com/docs/en/welcome includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Description completeness — Only 10% of operations and parameters have descriptions (61 of 307 ops, 0 of 701 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 0%.
- [fail] Code samples in docs — No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (rioanandaputra-bot/tiktok-docs, 3324 snippets). Investigated: docs 100%, sdk 50%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.tiktok.com/llms.txt, https://developers.tiktok.com/docs/llms.txt). Investigated: docs 50%, sdk 0%.
- [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%.

### Agent Understanding

- [pass] Operation purpose clarity — 94% of operations (290 of 307) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%, sdk 63%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 1 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [fail] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: spec 0%, docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 50%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 152) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

TikTok's API program shows strong foundations in contract quality and agent discoverability, but two areas create real friction for partners and their AI agents: operational reliability and error semantics. With zero mutating operations documenting idempotency or rate-limit behavior, and no error responses defined anywhere in the spec, any agent-driven integration risks duplicate writes, silent throttling, and unhandled failures. Fixing operational reliability and error handling first will unlock safe, automated partner integrations; completing onboarding with code samples and a changelog will close the remaining gaps in partner self-sufficiency.