rippling.com agentic web readiness

B Manifest validity: 100% (1/1 valid, 0 errors, 3 warnings) · Surface score 30 (coverage 20 + breadth 0 + conformance 10). 2 standards observed across 2 of 9 steps; 1 manifest present (+ robots.txt), 0 errors, 3 warnings. Checked 2026-10-25 11:10:56 UTC via www.rippling.com. This grades the agent-facing files published at rippling.com, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/rippling.com.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

What an agent can call

• llms.txt: Rippling (rippling.com), 62 links
• robots.txt AI policy: no AI crawler tokens named; unlisted crawlers allowed on public paths (subpaths disallowed under User-agent: *)

Standards observed

• llms.txt https://rippling.com/llms.txt
• Content Signals Policy https://rippling.com/robots.txt

Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "rippling.com"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for rippling.com

   # Rippling for agents
   
   Rippling and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://rippling.com/llms.txt
   - API description: https://rippling.com/openapi.json
   - Discovery catalog: https://rippling.com/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://rippling.com/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@rippling.com
   

3. api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description (conditional spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "api-catalog-rfc9727", "domain": "rippling.com"}))

Agent pre-flight & practical readiness

Preferred mode: llms_txt. GET /llms.txt and follow the links it names. That index is the page list an agent should read.

Fetch: GET https://rippling.com/llms.txt GET /llms.txt and follow its links.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 53427, HTML-to-llms.txt token ratio 22.963×, JSON-LD Product, AggregateRating, Organization, PostalAddress, Country.

AI crawler posture: open_to_all · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 22/30, capabilities 4/35, conformance 10/15, total 56/100, grade B.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules