Legalesign

Legalesign provides AI-ready electronic signature software and agreement infrastructure, including comprehensive APIs, MCP-connected documentation, embeddable Components, real-time events and document workflow tools. It enables businesses to automate signing processes, embed signing components, and manage agreements securely at scale.

Legalesign is profiled on the APIs.io network. Tagged areas include Company, E-Signature, Automation, and Document Management.

The Legalesign catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Legalesign’s developer surface includes authentication, support, signup flow, pricing, engineering blog, getting-started guide, documentation, and 20 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

44.1/100 developing ▲ 8.7 Agent 22/100 agent aware Heartbeat 55/100 slowing Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessPaid

0 APIs

Company E-Signature Automation Document Management

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 44.1/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 9.3 / 17

Access Clarity 12.7 / 17

Operational Transparency 3.4 / 11

Contract Governance 0.0 / 10

Discoverability 3.9 / 9

Regulatory Posture 2.1 / 15

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/legalesign/"><img src="https://apis.io/badge/legalesign/card.svg" alt="Legalesign on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link Ask about this →

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points Ask about this →
Contract Governance scores 0.0 — up to +12.0 composite points Ask about this →
Operational Transparency scores 31.0 — up to +9.0 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/legalesign/apis.yml: open an issue on github.com/api-evangelist/legalesign to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Legalesign API pricing

Prices published by Legalesign, read 2026-10-20 from legalesign.com/pricing/.

Plan	Price
Pay As You Go	£1.50 per sent-document
Solo Basic	£10/month (ex VAT)
Solo Pro	£25/month (ex VAT)
Team	£15/user/month (ex VAT)
5+ users & Enterprise	Flexible pricing and Enterprise features.

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Legalesign Plans Pricing

5 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Legalesign Rate Limits

0 limits

RATE LIMITS

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Legalesign

9 quoted statements, read from Legalesign's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Legalesign

23 quoted statements, read from Legalesign's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Legalesign

6 quoted statements, read from Legalesign's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Legalesign

2 quoted statements, read from Legalesign's own page on 2026-11-09.

AI PREFS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Legalesign Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Legalesign Authentication

1 scheme

SECURITY

Legalesign Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

SignUp

SignUp

GettingStarted

GettingStarted

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AIPreferences

AIPreferences

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Webhooks

Webhooks

Conventions

Conventions

Build 3

SDKs, sample code, and the tooling you integrate with

SDKs

SDKs

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Roadmap

Roadmap

Commercial 5

Pricing, plans, and the legal terms of use

Plans

TermsOfService

PrivacyPolicy

Pricing

UsageTerms

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 4

Properties that don't map to a standard resource type

Hosts

Vendors

DataProcessing

Eligibility

Source (apis.yml)

aid: legalesign
name: Legalesign
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  probe_state: none
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://legalesign.com/og_image.jpg
description: Legalesign provides AI-ready electronic signature software and agreement infrastructure, including comprehensive
  APIs, MCP-connected documentation, embeddable Components, real-time events and document workflow tools. It enables businesses
  to automate signing processes, embed signing components, and manage agreements securely at scale.
url: https://raw.githubusercontent.com/api-evangelist/legalesign/refs/heads/main/apis.yml
x-type: company
x-source: harvest:g2-catalog
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-20 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-20'
modified: '2026-10-20'
tags:
- Company
- E-Signature
- Automation
- Document Management
tags_raw:
- Company
- eSignature
- API
- Automation
- Document Management
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/legalesign-plans-pricing.yml
- type: Webhooks
  url: asyncapi/legalesign-webhooks.yml
- type: Conventions
  url: conventions/legalesign-conventions.yml
- type: Authentication
  url: authentication/legalesign-authentication.yml
- type: LLMsTxt
  url: llms/legalesign-llms.txt
- type: Hosts
  url: hosts/legalesign-hosts.yml
- type: Vendors
  url: vendors/legalesign-vendors.yml
- type: SDKs
  url: packages/legalesign-packages.yml
- type: Packages
  url: packages/legalesign-packages.yml
- type: TermsOfService
  url: https://legalesign.com/opn/terms/
- type: Support
  url: https://support.legalesign.com/
- type: StatusPage
  url: https://status.legalesign.com/
- type: SignUp
  url: https://legalesign.com/articles/app1/account-information/sign-up-for-a-plan-or-change-a-plan/
- type: Roadmap
  url: https://legalesign.com/roadmap/
- type: PrivacyPolicy
  url: https://legalesign.com/opn/privacy/
- type: Pricing
  url: https://legalesign.com/pricing
- type: GitHubOrganization
  url: https://github.com/legalesign
- type: Blog
  url: https://legalesign.com/blog/
- type: GettingStarted
  url: https://docs.legalesign.com/tags/getting-started
- type: Documentation
  url: https://apidocs.legalesign.com/
- type: APIReference
  url: https://docs.legalesign.com/rest-api/tutorial/quickstart
- type: DomainSecurity
  url: security/legalesign-domain-security.yml
- type: Website
  url: https://legalesign.com/
- type: UsageTerms
  url: terms/legalesign-terms-of-service.yml
- type: DataProcessing
  url: privacy/legalesign-privacy-policy.yml
- type: Eligibility
  url: eligibility/legalesign-eligibility.yml
- type: AIPreferences
  url: ai-preferences/legalesign-ai-preferences.yml
apis: []
x-coverage:
  state: none
  reason: no-developer-program
  method: derived
  generated: '2026-10-20'
  generator: derive-coverage.py (pre-flight evidence)
  detail: the company publishes no developer documentation host and no machine-readable contract on its own domain
  evidence:
  - url: https://legalesign.com/
    status: 200
x-enrichment:
  date: '2026-10-20'
  status: enriched
  artifacts_added: 15
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

Legalesign API — frequently asked questions

How do I authenticate with the Legalesign API?

Legalesign uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Legalesign Authentication.

How much does the Legalesign API cost?

Legalesign publishes its prices; its Pay As You Go plan is £1.50 per sent-document as of 2026-10-20. APIs.io lists 5 pricing plans for Legalesign, with each plan's price, limits and inclusions under Pricing on this page.

Is the Legalesign API ready for AI agents?

Legalesign has a Kin Score of 44.1 out of 100 (developing) and an Agent Readiness score of 22.3 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/legalesign"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/legalesign/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/legalesign/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.