Electronic Signature
Electronic SignaturesElectronic Signature
Providers using this tag (35)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 11 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 5 Early or largely undocumented
APIs with this tag (3)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Developing 3 Usable, with meaningful gaps to close
Companies reaching this through an API (2)
These companies publish an API, specification or operation carrying “Electronic Signature” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 34 providers in the APIs.io catalog tagged Electronic Signature, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 40.1 | 17.6 | +22.5 | 34 |
| Access Clarity | 47.7 | 26.5 | +21.2 | 34 |
| Operational Transparency | 29.7 | 13.7 | +16 | 34 |
| Developer Ergonomics | 36.4 | 23.2 | +13.2 | 34 |
| Discoverability | 64.2 | 58.1 | +6.1 | 34 |
| Contract Governance | 10 | 6.3 | +3.7 | 34 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 26% | 14% | +12 |
| MCP server (first-party) | 24% | 12% | +12 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 29% | 11% | +18 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 29% | 14% | +15 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Docusign 69.8
- 2 SignSealShip Partner API 66.5
- 3 JuriSign 65.3
- 4 GetAccept 63.8
- 5 Dropbox Sign (HelloSign) 59.6
- 6 GoNitro 56.8
- 7 Nitro Software 56
- 8 YouSign 52.8
- 9 DocuSeal 51.9
- 10 Agree.com 51.5
- 1 Agree.com 45.4
- 2 Dropbox Sign (HelloSign) 44.8
- 3 SignSealShip Partner API 43.7
- 4 DocuSeal 37.3
- 5 BoldSign 35.9
- 6 SignNow 35.9
- 7 Nitro Software 35.7
- 8 Docusign 34.9
- 9 JuriSign 34.6
- 10 Zoho Writer 34.5
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.