Formality website screenshot

Formality

Formality is a Paris-based AI platform for end-to-end asset and contract intelligence, aimed at businesses that need to centralize, understand, and track their legal, administrative, and asset-related documents. The product covers the full contract lifecycle: AI-assisted creation and collaborative negotiation, electronic signature, then post-signature data extraction, deadline and obligation alerts, and natural-language analysis of the resulting document estate. Its AI is trained on corporate legal documents, works across multiple languages, and runs inside a secure perimeter with full auditability and no use of customer data for model training. Formality integrates with tools including Google Drive, SharePoint, DocuWare, Docusign, Universign, Yousign, HubSpot, Salesforce, Outlook, Teams, Slack, and Gmail, and runs on compliant hosting with ISO 27001 and SOC 2 Type II certifications and GDPR compliance. It was founded in 2023 and is backed by Partech, Serena, and Bpifrance.

Formality publishes 1 API on the APIs.io network. Tagged areas include Company, Ai Ml, Legal, Contract Management, and Document-Management.

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

Formality’s developer surface includes documentation, API reference, getting-started guide, support, authentication, and 25 more developer resources.

40.4/100 developing ▬ flat Agent 38/100 agent ready Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
1 APIs
CompanyAi MlLegalContract ManagementDocument-ManagementAsset IntelligenceComplianceSoftware-as-a-Service

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 40.4/100 · developing
Contract Quality 11.3 / 25
Developer Ergonomics 9.0 / 20
Access Clarity 6.6 / 20
Operational Transparency 3.8 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 38/100 · agent ready
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 8 / 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 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/formality: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Formality API

The Formality REST API exposes the workspace contract repository so external tools and AI agents can retrieve documents and the AI-extracted metadata layer. Every path is namesp...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Formality Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

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

Security Posture 4

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

Formality Authentication

http · 2 schemes

SECURITY

Formality Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Formality Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Formality Trust Center

SOC 2 Type II, ISO 27001, GDPR

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 7

Authentication, authorization, and security posture

Scroll for all 7

Operate 4

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: formality
name: Formality
description: 'Formality is a Paris-based AI platform for end-to-end asset and contract intelligence, aimed at businesses that
  need to centralize, understand, and track their legal, administrative, and asset-related documents. The product covers the
  full contract lifecycle: AI-assisted creation and collaborative negotiation, electronic signature, then post-signature data
  extraction, deadline and obligation alerts, and natural-language analysis of the resulting document estate. Its AI is trained
  on corporate legal documents, works across multiple languages, and runs inside a secure perimeter with full auditability
  and no use of customer data for model training. Formality integrates with tools including Google Drive, SharePoint, DocuWare,
  Docusign, Universign, Yousign, HubSpot, Salesforce, Outlook, Teams, Slack, and Gmail, and runs on compliant hosting with
  ISO 27001 and SOC 2 Type II certifications and GDPR compliance. It was founded in 2023 and is backed by Partech, Serena,
  and Bpifrance.'
url: https://raw.githubusercontent.com/api-evangelist/formality/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: contact-sales
  onboarding: sales-gate
  trial: false
  try_now: false
  public: false
  label: Customer-only API
  confidence: medium
  source:
  - https://help.formality.com/integrations/api
  - https://www.formality.com/en/index.html
  generated: '2026-08-17'
  method: searched
  note: 'A documented REST API exists but is reachable only from inside a provisioned Formality workspace: tokens are minted
    in Personal Settings, the Swagger UI requires login, and the marketing site''s only call to action is "Let''s talk". Billing
    is on document volume with no published price list.'
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-17'
image: https://framerusercontent.com/images/hEwKjnYt6aQ2PnIpW5a9LjGDmG4.svg
tags:
- Company
- Ai Ml
- Legal
- Contract Management
- Document-Management
- Asset Intelligence
- Compliance
- Software-as-a-Service
tags_raw:
- Company
- Ai/Ml
- Legal
- Contract Management
- Document Management
- Asset Intelligence
- Compliance
- SaaS
apis:
- aid: formality-api
  name: Formality API
  description: 'The Formality REST API exposes the workspace contract repository so external tools and AI agents can retrieve
    documents and the AI-extracted metadata layer. Every path is namespaced to a workspace — /api/v1/{workspaceId}/ — and
    the documented resources cover agreements and agreement fields, with the help centre describing coverage of agreements,
    counterparties and related entities. Access uses a two-step bearer flow: an administrator mints a long-lived personal
    Refresh Token in Personal Settings > Formality API, then exchanges it at GET /api/v1/token for a 5-minute access token
    used as Authorization: Bearer on subsequent calls. A Swagger UI is published at /-/api-doc-swagger but is reachable only
    after authenticating.'
  humanURL: https://help.formality.com/integrations/api
  baseURL: https://app.eu1.formality.com/api/v1/{workspaceId}
  tags:
  - Contract Management
  - Documents
  - Legal
  - Agreements
  properties:
  - type: APIReference
    url: https://help.formality.com/integrations/api
  - type: Authentication
    url: authentication/formality-authentication.yml
  - type: ErrorCatalog
    url: errors/formality-problem-types.yml
  - type: Conventions
    url: conventions/formality-conventions.yml
  - type: DataModel
    url: data-model/formality-data-model.yml
  - type: Webhooks
    url: asyncapi/formality-webhooks.yml
  x-base-url-note: The help centre publishes the base as https://app.formality.com/api/v1/{workspaceId}/, but app.formality.com
    does not resolve in DNS (2026-08-17). The live regional application hosts named on Formality's own status page are app.eu1.formality.com
    (EU/Ireland) and app.fr1.formality.com (France/Scaleway); both answer /api/v1/... with HTTP 401 rather than 404, so the
    EU host is recorded here and the documented generic host is flagged as a provider-side documentation defect.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.formality.com/
- type: PrivacyPolicy
  url: https://www.formality.com/en/privacy-policy.html
- type: CookiePolicy
  url: https://www.formality.com/en/cookie-policy.html
- type: LegalNotice
  url: https://www.formality.com/en/legal-notice.html
- type: StatusPage
  url: https://status.formality.com/
- type: Compliance
  url: https://www.formality.com/en/index.html#security
- type: TrustCenter
  url: security/formality-trust-center.yml
- type: Documentation
  url: https://help.formality.com/
- type: HelpCenter
  url: https://help.formality.com/
- type: APIReference
  url: https://help.formality.com/integrations/api
- type: GettingStarted
  url: https://help.formality.com/start/first-steps
- type: Support
  url: https://help.formality.com/faq/feedback
- type: Login
  url: https://auth.eu1.formality.com/
- type: LinkedIn
  url: https://www.linkedin.com/company/formality-group/
- type: LLMsTxt
  url: llms/formality-llms.txt
- type: WellKnown
  url: well-known/formality-well-known.yml
- type: SecurityTxt
  url: well-known/formality-security.txt
- type: Security
  url: https://www.formality.com/.well-known/security.txt
- type: VulnerabilityDisclosure
  url: security/formality-vulnerability-disclosure.yml
- type: Authentication
  url: authentication/formality-authentication.yml
- type: Conventions
  url: conventions/formality-conventions.yml
- type: ErrorCatalog
  url: errors/formality-problem-types.yml
- type: DataModel
  url: data-model/formality-data-model.yml
- type: Webhooks
  url: asyncapi/formality-webhooks.yml
- type: Conformance
  url: conformance/formality-conformance.yml
- type: Packages
  url: packages/formality-packages.yml
- type: Plans
  url: plans/formality-plans-pricing.yml
- type: RateLimits
  url: rate-limits/formality-rate-limits.yml
- type: Integrations
  url: https://help.formality.com/setup-permissions/integrations-hub
- type: Lifecycle
  url: lifecycle/formality-lifecycle.yml
- type: DomainSecurity
  url: security/formality-domain-security.yml
x-idempotency-note: 'No type:Idempotency pointer is emitted. conventions/formality-conventions.yml records idempotency as
  not supported and not documented: only GET operations are published and no idempotency key, write operation or retry-safety
  rule appears anywhere in Formality''s documentation. This is a checked absence, not an oversight.'
x-mcp-note: No type:MCPServer pointer is emitted even though Formality's homepage advertises "Secure connection via API/MCP"
  and "+ 130 contract tools for your AI agents". Six candidate endpoints were probed and none is an MCP server (see mcp/formality-mcp.yml).
  The marketing claim has no public artifact behind it.
x-enrichment:
  date: '2026-08-17'
  status: enriched
  artifacts_added: 13
  pass: local-v1
  note: Round 2 overturned round 1's "no public REST API" finding. A documented Formality REST API (v1, bearer token exchange,
    workspace-scoped) was found via the GitBook help centre's own llms.txt index, and three dead apis.yml pointers were repaired.