Time Tracking
Providers using this tag (84)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 4 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 19 Usable, with meaningful gaps to close
Thin 32 Limited public surface area
Emerging 19 Early or largely undocumented
Minimal 5 Almost no public developer surface
APIs with this tag (29)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 6 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 6 Limited public surface area
Emerging 4 Early or largely undocumented
Companies reaching this through an API (13)
These companies publish an API, specification or operation carrying “Time Tracking” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 82 providers in the APIs.io catalog tagged Time Tracking, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 32.7 | 18.6 | +14.1 | 82 |
| Developer Ergonomics | 34.6 | 24.5 | +10.1 | 82 |
| Access Clarity | 39.6 | 30 | +9.6 | 82 |
| Discoverability | 65.3 | 59.1 | +6.2 | 82 |
| Operational Transparency | 19.4 | 13.2 | +6.2 | 82 |
| Contract Governance | 14.1 | 9.7 | +4.4 | 82 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 22% | 18% | +4 |
| MCP server (first-party) | 22% | 16% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 23% | 13% | +10 |
| Security | 98% | 99% | -1 |
| Arazzo workflows | 5% | 1% | +4 |
| Governance rules | 63% | 36% | +27 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Clickup 72.6
- 2 Intuit 70.8
- 3 Rocketlane 68.6
- 4 Connecteam 68.4
- 5 Timely (Memory AS) 66.3
- 6 HourSquare 61.7
- 7 Mavenlink 58.1
- 8 LeanLaw 57.4
- 9 WakaTime 55.6
- 10 Teambridge 53.7
- 1 Mavenlink 61.7
- 2 Clockodo 58.8
- 3 Clickup 57
- 4 TimeCamp 50.5
- 5 COR 48.8
- 6 Factorial 48.5
- 7 LeanLaw 47.7
- 8 vigotime-com 47.7
- 9 Connecteam 46.7
- 10 Nova Lima 46.4
Coverage caveat. 60 of 82 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 14 November 2026, across 41591 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.