# Trmlabs — API Agent Score

> Score: 51/100 (Grade: D) | Domain: trmlabs.com | Rubric: 1.0.0 | Checked: July 29, 2026

Trmlabs scored 51/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 44/100 (F)
- Agent Discovery: 80/100 (A)
- Agent Understanding: 74/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No detectable code samples across 15 sampled docs pages. Investigated: docs 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

- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://docs.trmlabs.com/login?redirect=%2Fquickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 15 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.trmlabs.com/llms.txt: No blockquote summary found. Investigated: docs 94%.
- [warn] Docs reachable, not hard auth-gated — 29 of 29 pages return 200 for non-existent URLs (soft 404). Investigated: docs 75%.
- [warn] Registry & SDK presence — Discovered SDKs in only 1 language(s); target ≥3. Investigated: sdk 50%, docs 0%, cli 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 4 of 29 pages have substantive content differences between markdown and HTML (avg 7% missing). Investigated: docs 89%.
- [pass] Docs structured data — JSON-LD Article markup on 5/5 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 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 discovered for the org. 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

TRM Labs' API program shows real strength in agent discovery — partners and agents can already find and reach your APIs without friction. However, two areas are holding back partner program growth: the API contract itself lacks security governance signals and realistic examples that partners and AI agents need to build confidently, and the onboarding experience has no self-service portal or in-context code samples to get partners to a first successful call without hand-holding. Prioritize hardening the API contract and standing up a self-service portal first, then layer in runnable collections and agent-specific context to fully unlock partner and AI agent productivity.