# Aprimo — API Agent Score

> Score: 79/100 (Grade: B) | Domain: aprimo.com | Rubric: 1.0.0 | Checked: November 3, 2026

Aprimo scored 79/100 (B), classified "partially-ready".

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

## Summary

- Overall: 79/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 97/100 (A+)
- Developer Experience: 67/100 (C)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 82/100 (A)
- Agent Usability: 74/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — 2/2 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 50%.
- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Machine-readable, versioned contract — The API sets a version ("v1") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 88%, docs 75%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 0%.
- [pass] Example coverage — Only 0% of parameters and responses (0 of 796) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, docs 100%, sdk 100%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://developers.aprimo.com/quickstart includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples appear on 1 of 20 sampled docs pages across 1 language(s), but broader multi-language coverage is missing. Investigated: docs 100%.
- [pass] Description completeness — Only 45% of operations and parameters have descriptions (338 of 376 ops, 0 of 671 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 100%.
- [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] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [warn] llms.txt present, valid & comprehensive — llms.txt covers 4/114 sitemap doc pages (4%); 110 missing — Missing: https://developers.aprimo.com/search, https://developers.aprimo.com/docs/agentic-orchestration/agentic-orchestration-intro, https://developers.aprimo.com/docs/agentic-orchestration/aprimo-mcp-server/, https://developers.aprimo.com/docs/agentic-orchestration/aprimo-mcp-server/tool-permission-map, https://developers.aprimo.com/docs/agentic-orchestration/aprimo-mcp-server/tools/activities (and 45 more). Investigated: docs 82%, sdk 0%.
- [warn] Registry & SDK presence — No official SDKs were found on npm, PyPI, or GitHub, so agents must call the API by hand. Investigated: sdk 67%, docs 0%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [warn] Crawlable / AEO — Sitemap has 114 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Operation purpose clarity — Read/write classification is partial: 3/3 classified (3 read, 0 write). Investigated: sdk 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 80%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 17% (threshold 35% for full credit).
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 3 assessed pages (3 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Pagination documented & consistent — Pagination parameters are present on the 11 list endpoint(s), so an agent can page through results. Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.

## Executive Summary

Aprimo's API program shows strong fundamentals in API design and agent understanding overall, but two areas are holding back partner success: developer experience and agent discoverability. Without a published changelog or self-service onboarding path, partners and their agents face unnecessary friction before writing a single line of integration code. Prioritize making the program self-serve and transparent — a clear change history and low-friction entry point will unlock partner momentum without requiring a sales conversation.