# Loops — API Agent Score

> Score: 56/100 (Grade: D) | Domain: loops.so | Rubric: 1.0.0 | Checked: July 24, 2026

Loops scored 56/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

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

## Check Results

### API Design

- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [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 20 sampled docs pages. Investigated: docs 0%, sdk 0%.
- [skip] Machine-readable, versioned contract — 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] Quickstart present — Quickstart at https://loops.so/docs/quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt directive found in HTML of 48 of 49 sampled pages (1 missing); 1 failed to fetch. Investigated: docs 94%.
- [pass] Registry & SDK presence — Indexed on Context7 (llmstxt/loops_so_llms-full_txt, 7182 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap present (232 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 1 of 50 sampled pages have content starting past 50% (worst 107%). Investigated: docs 72%.
- [pass] Agent instructions file (AGENTS.md) — Agent instructions file found at https://loops.so/agents.md. Investigated: wellknown 100%.
- [pass] Docs structured data — JSON-LD Article markup on 18/18 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (docs, sdk) is 4% (threshold 35% for full credit).
- [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.

### 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

Loops has a strong foundation in agent discoverability and documentation clarity, but the partner program is being held back by critical gaps in the API contract itself and the absence of a runnable, self-serve onboarding experience. Schemas lack the depth and examples agents need to generate correct integrations, security hygiene is incomplete, and partners have no executable environment to validate against — creating friction that slows or blocks real integrations. Fixing the contract quality and standing up a self-serve, runnable front door should be the immediate priority.