# Rippling — API Agent Score

> Score: 68/100 (Grade: C) | Domain: rippling.com | Rubric: 1.0.0 | Checked: July 24, 2026

Rippling scored 68/100 (C), classified "partially-ready".

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

## Summary

- Overall: 68/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 70/100 (B)
- Agent Discovery: 61/100 (C)
- Agent Understanding: 68/100 (C)
- Agent Usability: 79/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 626/627 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [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 1 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] Self-service developer portal — Self-service signup at https://www.rippling.com/get-started; no free tier or sandbox language detected. Investigated: docs 100%.
- [warn] Description completeness — 276/313 operations carry a description. Investigated: sdk 88%.
- [warn] Quickstart present — Quickstart page reachable (12 variants scanned starting at https://rippling.stoplight.io/docs/rippling-api/a310f900b0f84-api-reference/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_rippling, 1451 snippets). Investigated: docs 100%, sdk 75%, cli 50%.
- [warn] Docs reachable, not hard auth-gated — 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [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://rippling.stoplight.io/docs/rippling-api/a310f900b0f84-api-reference/llms.txt, https://rippling.stoplight.io/llms.txt, https://rippling.stoplight.io/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "APIError" with 41 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 1 of 1 pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content. Investigated: docs 57%.
- [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%.
- [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

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Pagination documented & consistent — 94/97 list method(s) return an auto-paginating iterable. Investigated: sdk 97%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.

## Executive Summary

Rippling's API program shows strength in operational reliability and general developer experience, but faces meaningful gaps in two areas that directly affect partner and agent success: API design completeness (missing security hygiene and example coverage) and agent discoverability/understanding (no llms.txt, no AGENTS.md, no structured data for docs). Left unaddressed, these gaps mean partners' AI agents cannot reliably find, parse, or trust Rippling's API surface — slowing integrations and increasing support burden. The highest-priority fixes are making the API contract agent-ready (security, examples, runnable context) and building out the agent discovery layer (llms.txt, AGENTS.md, structured metadata) so partners can go from discovery to first working call without a sales conversation.