# Eversign — API Agent Score

> Score: 59/100 (Grade: D) | Domain: eversign.com | Rubric: 1.0.0 | Checked: July 29, 2026

Eversign scored 59/100 (D), classified "not-ai-ready".

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

## Summary

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

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 67/100 (C)
- Agent Discovery: 74/100 (B)
- Agent Understanding: 50/100 (D)
- Agent Usability: 53/100 (D)

## Check Results

### API Design

- [warn] Schema coverage & depth — 20/40 (50%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 58%.
- [pass] Example coverage — Code samples in 3 language(s) across docs (top: php, shell, javascript); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 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://app.eversign.com/api/signup; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 3 language(s) across docs (top: php, shell, javascript); 2/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [warn] Description completeness — 9/34 operations lack a description. Investigated: sdk 74%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 773 days ago. Investigated: sdk 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/10 pages return markdown). Investigated: docs 75%.
- [warn] Registry & SDK presence — No MCP server, tool manifest, or list-tools capability is discoverable (server entrypoint: absent, tool manifest: unknown, list-tools: unknown). Investigated: sdk 67%, docs 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt exists but contains no parseable links. Investigated: docs 60%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (315 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/10 tested). Investigated: docs 75%.
- [warn] Docs structured data — JSON-LD on 5/20 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 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] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [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.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Eversign's API program shows meaningful strength in discoverability and schema quality, but partners and their AI agents face real friction in three areas that matter most: the API contract lacks the security clarity and error semantics agents need to build safely, there is no runnable entry point to accelerate a partner's first successful call, and the program is missing the structured agent context — changelog, idempotency documentation, and machine-readable instructions — that modern integrations depend on. Prioritizing error semantics, runnable onboarding, and agent-facing documentation will do the most to move partners from evaluation to production.