Trato

TRATO is an AI-powered Contract Lifecycle Management (CLM) and electronic signature platform used by more than 180,000 users to centralize, draft, approve, sign and track contracts. It offers template-based smart drafting, automated approval routing, real-time contract tracking, and secure e-signatures, with multi-jurisdiction legal expertise across Mexico, Spain and Germany and support for Mexican NOM-151 advanced electronic signatures. TRATO exposes a JWT-authenticated REST API (Contracts, Templates, Milestones) and webhook events for programmatic contract generation and integration with CRM, document management and payment systems. Founded in 2014 in Mexico City and backed by 500 Global.

Trato is listed with 5 APIs on the APIs.io network, including Contracts API, Custom Properties API, Participants API, and 2 more. Tagged areas include Company, Contract Management, Contract Lifecycle Management, E-Signature, and Legal Tech.

The Trato catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Trato’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, authentication, and 22 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.9/100 thin ▬ flat Agent 24/100 agent aware Front door AI 4/6 moderate Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

5 APIs 1 Agent Skills

Company Contract Management Contract Lifecycle Management E-Signature Legal Tech Document Management Workflow Automation Legal

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 38.9/100 · thin

Contract Quality 3.8 / 19

Developer Ergonomics 9.7 / 15

Access Clarity 4.9 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.6 / 9

Discoverability 5.9 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 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 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 0 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/trato/"><img src="https://apis.io/badge/trato/card.svg" alt="Trato 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 20.5 — up to +19.9 composite points
Access Clarity scores 32.9 — up to +13.4 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

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.

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/trato/apis.yml: open an issue on github.com/api-evangelist/trato 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 →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

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

Trato Contracts API

Create, configure, send, sign and manage contracts.

Trato Custom Properties API

Attach custom metadata properties to a contract.

Trato Participants API

Manage participants (signers) on a contract.

Trato Spectators API

Manage read-only observers of a contract.

Trato Templates API

List reusable contract templates.

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

TRATO Contract Contracts API

OPEN COLLECTION

TRATO Contract Contracts Custom Properties API

OPEN COLLECTION

TRATO Contract Contracts Participants API

OPEN COLLECTION

TRATO Contract Contracts Spectators API

OPEN COLLECTION

TRATO Contract Contracts Templates API

OPEN COLLECTION

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Create and send a TRATO contract for signature

AGENT SKILL

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Trato

SLA

Event Specifications 1

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

TRATO Webhooks

TRATO delivers contract and milestone lifecycle events to subscriber URLs as HTTP POST callbacks. Webhooks are configured in the user profile per event type. Each request carrie...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Trato API Rules

58 rules · 53 errors 3 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Trato Openapi Overlay

3 actions · update · trato-openapi.yml

DERIVED

Security Posture 2

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

Trato Authentication

http · 1 scheme

SECURITY

Trato Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

WellKnown

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Webhooks

Conventions

ErrorCatalog

DataModel

Lifecycle

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: trato
name: Trato
description: TRATO is an AI-powered Contract Lifecycle Management (CLM) and electronic signature platform used by more than
  180,000 users to centralize, draft, approve, sign and track contracts. It offers template-based smart drafting, automated
  approval routing, real-time contract tracking, and secure e-signatures, with multi-jurisdiction legal expertise across Mexico,
  Spain and Germany and support for Mexican NOM-151 advanced electronic signatures. TRATO exposes a JWT-authenticated REST
  API (Contracts, Templates, Milestones) and webhook events for programmatic contract generation and integration with CRM,
  document management and payment systems. Founded in 2014 in Mexico City and backed by 500 Global.
url: https://raw.githubusercontent.com/api-evangelist/trato/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Contract Management
- Contract Lifecycle Management
- E-Signature
- Legal Tech
- Document Management
- Workflow Automation
- Legal
tags_raw:
- Company
- Contract Management
- Contract Lifecycle Management
- Electronic Signature
- Legaltech
- Document Management
- Workflow Automation
- Legal
- Document-Management
- Workflow-Automation
image: https://trato.io
apis:
- aid: trato:trato-contracts-api
  name: Trato Contracts API
  description: Create, configure, send, sign and manage contracts.
  humanURL: https://developer.trato.io/
  baseURL: https://enterprise.api.trato.io
  tags:
  - Contracts
  properties:
  - type: OpenAPI
    url: openapi/trato-contracts-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/trato-webhooks-asyncapi.yml
  - type: Documentation
    url: https://developer.trato.io/
  - type: Authentication
    url: authentication/trato-authentication.yml
- aid: trato:trato-custom-properties-api
  name: Trato Custom Properties API
  description: Attach custom metadata properties to a contract.
  humanURL: https://developer.trato.io/
  baseURL: https://enterprise.api.trato.io
  tags:
  - Custom Properties
  properties:
  - type: OpenAPI
    url: openapi/trato-custom-properties-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/trato-webhooks-asyncapi.yml
  - type: Documentation
    url: https://developer.trato.io/
  - type: Authentication
    url: authentication/trato-authentication.yml
- aid: trato:trato-participants-api
  name: Trato Participants API
  description: Manage participants (signers) on a contract.
  humanURL: https://developer.trato.io/
  baseURL: https://enterprise.api.trato.io
  tags:
  - Participants
  properties:
  - type: OpenAPI
    url: openapi/trato-participants-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/trato-webhooks-asyncapi.yml
  - type: Documentation
    url: https://developer.trato.io/
  - type: Authentication
    url: authentication/trato-authentication.yml
- aid: trato:trato-spectators-api
  name: Trato Spectators API
  description: Manage read-only observers of a contract.
  humanURL: https://developer.trato.io/
  baseURL: https://enterprise.api.trato.io
  tags:
  - Spectators
  properties:
  - type: OpenAPI
    url: openapi/trato-spectators-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/trato-webhooks-asyncapi.yml
  - type: Documentation
    url: https://developer.trato.io/
  - type: Authentication
    url: authentication/trato-authentication.yml
- aid: trato:trato-templates-api
  name: Trato Templates API
  description: List reusable contract templates.
  humanURL: https://developer.trato.io/
  baseURL: https://enterprise.api.trato.io
  tags:
  - Templates
  properties:
  - type: OpenAPI
    url: openapi/trato-templates-api-openapi.yml
  - type: AsyncAPI
    url: asyncapi/trato-webhooks-asyncapi.yml
  - type: Documentation
    url: https://developer.trato.io/
  - type: Authentication
    url: authentication/trato-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://trato.io
- type: DeveloperPortal
  url: https://developer.trato.io/
- type: Documentation
  url: https://developer.trato.io/
- type: APIReference
  url: https://developer.trato.io/contracts
- type: GettingStarted
  url: https://developer.trato.io/
- type: Blog
  url: https://blog.trato.io
- type: StatusPage
  url: https://status.trato.io
- type: GitHubOrganization
  url: https://github.com/contratosapp
- type: Support
  url: https://trato.io/contact
- type: Pricing
  url: https://trato.io/#pricing
- type: Login
  url: https://clm.trato.io/login
- type: TermsOfService
  url: https://trato.io/terms-of-use
- type: PrivacyPolicy
  url: https://trato.io/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/tratolegaltech/
- type: Authentication
  url: authentication/trato-authentication.yml
- type: Webhooks
  url: asyncapi/trato-webhooks-asyncapi.yml
- type: AsyncAPI
  url: asyncapi/trato-webhooks-asyncapi.yml
- type: X-MCPServerCandidate
  url: mcp/trato-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: Sandbox
  url: sandbox/trato-sandbox.yml
- type: Conventions
  url: conventions/trato-conventions.yml
- type: ErrorCatalog
  url: errors/trato-problem-types.yml
- type: DataModel
  url: data-model/trato-data-model.yml
- type: Lifecycle
  url: lifecycle/trato-lifecycle.yml
- type: Conformance
  url: conformance/trato-conformance.yml
- type: DomainSecurity
  url: security/trato-domain-security.yml
- type: WellKnown
  url: well-known/trato-well-known.yml
- type: LLMsTxt
  url: llms/trato-llms.txt
- type: Overlay
  url: overlays/trato-openapi-overlay.yaml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 16
  pass: local-v1

Trato API — frequently asked questions

Does Trato have an API?

Yes. APIs.io lists 5 APIs from Trato, including Trato Contracts API, Trato Custom Properties API and Trato Participants API, and 2 more.

Is there an OpenAPI specification for the Trato API?

Yes. APIs.io indexes 5 OpenAPI specifications for Trato, each linked for download from this page.

How do I authenticate with the Trato API?

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

Is the Trato API ready for AI agents?

Trato has a Kin Score of 38.9 out of 100 (thin) and an Agent Readiness score of 23.9 (agent-aware), scored by API Evangelist on 2026-11-06.

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/trato"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/trato/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.