Eversigneversign.com

ScoredJul 29, 2026, 08:02 PM

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.

API DesignA clean, typed, well-governed API contract agents can reason about1 pass1 warn1 fail61C

Signal	Points	Findings	Rationale
Schema coverage & depthvia sdk	14.6/25	20/40 (50%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 58%.	Typed, complete request/response schemas are what make agent function-calling possible.
Example coveragevia docs	10/10	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%.	Examples carry shape semantics schemas under-specify — for humans and agents alike.
Security & governance hygienevia wellknown	0/15	No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.	No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
Machine-readable, versioned contract	—/25	No surface produced evidence for this capability in this run.	A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
Auth declared & discoverable	—/25	No surface produced evidence for this capability in this run.	Agents can only authenticate when auth is declared, scoped, and discoverable.

Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples2 pass1 warn2 fail67C

Signal	Points	Findings	Rationale
Self-service developer portalvia docs	29/29	Self-service signup at https://app.eversign.com/api/signup; free tier / sandbox documented. Investigated: docs 100%.	Self-serve key/account creation is the fast first call for partners, with no sales gate.
Code samples in docsvia docs	18/18	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%.	Multi-language samples shorten time-to-first-call.
Description completenessvia sdk	11/15	9/34 operations lack a description. Investigated: sdk 74%.	Complete descriptions are the context humans and agents need to use endpoints.
Quickstart presentvia docs	0/25	No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.	A quickstart is the fastest path from landing page to first successful call.
Changelog publishedvia sdk	0/13	Official SDKs stale: newest activity 773 days ago. Investigated: sdk 0%.	A published changelog lets partners track changes without surprise.

Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs0 pass4 warn0 fail74B

Signal	Points	Findings	Rationale
Docs reachable, not hard auth-gatedvia docs	22.5/30	Server ignores Accept: text/markdown header (0/10 pages return markdown). Investigated: docs 75%.	Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
Registry & SDK presencevia sdk	18.7/28	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%.	Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
llms.txt present, valid & comprehensivevia docs	18/30	llms.txt exists but contains no parseable links. Investigated: docs 60%, sdk 0%.	A valid, comprehensive llms.txt is the machine-readable entry point for agents.
Crawlable / AEOvia wellknown	9/12	Sitemap present (315 entries) but carries no lastmod values. Investigated: wellknown 75%.	Bots allowed plus a fresh sitemap make docs findable by agent crawlers.

Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs0 pass2 warn2 fail50D

Signal	Points	Findings	Rationale
Agent-navigable, token-efficient docsvia docs	16.5/22	No pages support .md URLs (0/10 tested). Investigated: docs 75%.	Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
Docs structured datavia docs	4/8	JSON-LD on 5/20 assessed pages, but coverage is sparse or dateModified is missing. Investigated: docs 50%.	Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
Machine-readable errors (RFC 9457)via sdk	0/28	No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.	RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
Agent instructions file (AGENTS.md)via wellknown	0/10	No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.	An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
Operation purpose clarity	—/25	No surface produced evidence for this capability in this run.	Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
Description consistency across surfaces	—/7	Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.	Every surface tells the same story about what the product is.

Agent UsabilityAgents have the context to use your APIs reliably, not just find them1 pass0 warn2 fail53D

Signal	Points	Findings	Rationale
Sandbox separationvia sdk	20/20	Sandbox environments are exposed (sandbox). Investigated: sdk 100%.	An isolated environment lets agents exercise destructive operations safely.
Idempotency documentedvia sdk	0/27	No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.	Documented idempotency lets agents retry safely.
Runnable collection with test scriptsvia platform	0/9	No public Postman workspace discovered for the org. Investigated: platform 0%.	A public, maintained collection with assertions is runnable truth agents validate against.
Rate-limit signaling	—/22	No surface produced evidence for this capability in this run.	Machine-readable rate-limit headers let agents throttle adaptively.
Pagination documented & consistent	—/22	No surface produced evidence for this capability in this run.	Consistent, documented pagination lets agents traverse collections.

Want to improve your results?