# NICE inContact — API Agent Score

> Score: 55/100 (Grade: D) | Domain: niceincontact.com | Rubric: 1.0.0 | Checked: November 11, 2026

NICE inContact scored 55/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 81/100 (A)
- Developer Experience: 64/100 (C)
- Agent Discovery: 71/100 (B)
- Agent Understanding: 44/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "v1" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://developer.niceincontact.com/Error/NotFound?aspxerrorpath=/authentication, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Schema coverage & depth — Only 50% of the 2 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 50%.
- [fail] Example coverage — Only 0% of parameters and responses (0 of 4) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://www.nice.com/contact-us, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Changelog published — changelog is documented on the docs site at https://developer.niceincontact.com/Error/NotFound?aspxerrorpath=/changelog, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://developer.niceincontact.com/Error/NotFound?aspxerrorpath=/quickstart (12 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Description completeness — Only 50% of operations and parameters have descriptions (2 of 2 ops, 0 of 1 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/developer_niceincontact, 11280 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — 31 of 31 pages return 200 for non-existent URLs (soft 404). Investigated: docs 60%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.niceincontact.com/llms.txt, https://developer.niceincontact.com/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap has 36 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/31 tested). Investigated: docs 76%.
- [fail] 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 0%, docs 0%.
- [fail] Operation purpose clarity — Only 0% of operations (0 of 2) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 0%.
- [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%.
- [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%.
- [fail] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 0% (threshold 35% for full credit).

### Agent Usability

- [fail] Idempotency documented — Only 0% of mutating operations (0 of 2) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 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%.
- [fail] Sandbox separation — None of the 0 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.
- [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] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Niceincontact's API program shows strength in documentation discoverability and basic schema design, but partners and their AI agents face serious blockers in three areas: the spec is nearly invisible to agents (no operation clarity, no error handling, no structured data, no agent instruction files), mutating operations carry real risk in production (no sandbox, no idempotency guidance, no rate-limit signals), and the developer onboarding experience lacks examples or code samples to get partners to their first working call. Prioritize making the API contract legible and safe for agents first, then close the runnable-experience gap so partners can self-serve from day one.