# Smarsh — API Agent Score

> Score: 47/100 (Grade: F) | Domain: smarsh.com | Rubric: 1.0.0 | Checked: October 2, 2026

Smarsh scored 47/100 (F), classified "not-ai-ready".

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

## Summary

- Overall: 47/100 (F)
- Classification: not-ai-ready

## Category Scores

- API Design: 40/100 (F)
- Developer Experience: 40/100 (F)
- Agent Discovery: 66/100 (C)
- Agent Understanding: 64/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Security & governance hygiene — No security.txt found at /.well-known/security.txt or /security.txt, so there's no machine-readable security contact for agents or researchers. Investigated: wellknown 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.
- [skip] Example coverage — No surface produced evidence for this capability in this run.

### Developer Experience

- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [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] Docs reachable, not hard auth-gated — Content negotiation partially supported: 0 correct type, 25 wrong type, 25 HTML only; 25 rate-limited (HTTP 429). Investigated: docs 88%.
- [warn] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 86%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 25 of 50 sampled pages have content starting past 50% (worst 102%). Investigated: docs 80%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. 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] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 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 found for the org, so there's no runnable collection an agent can execute against. 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

Smarsh's API program shows meaningful strengths in documentation crawlability and reachability, but two areas are holding back partner activation: partners and their AI agents have no self-service entry point — no signup path, no quickstart, and no runnable collection to make a first call — and the API surface is essentially invisible to the agent ecosystem, lacking the machine-readable files and registry presence that modern coding agents rely on. Fixing self-service onboarding and agent-readable infrastructure should be the immediate priority, as they directly block partner time-to-value and automated integration workflows.