LawPay

LawPay provides payment processing solutions tailored for legal professionals, offering secure, compliant, and IOLTA‑ready credit card, debit, and eCheck transactions. Founded in 2005, LawPay serves over 50,000 law firms, integrating with practice management software and supporting online billing, recurring payments, and mobile apps. The platform emphasizes data security, fraud protection, and seamless client experiences, helping attorneys focus on their practice rather than payment logistics.

LawPay is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Payments, LegalTech, FinTech, and SaaS.

The LawPay catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

36.9/100 thin Agent 13/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 APIs

Company PaymentsLegalTechFinTechSaaS

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 36.9/100 · thin

Contract Quality 5.6 / 21

Developer Ergonomics 6.5 / 17

Access Clarity 11.2 / 17

Operational Transparency 1.2 / 11

Contract Governance 2.2 / 10

Discoverability 5.0 / 9

Regulatory Posture 2.6 / 15

Agent readiness — 13/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 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

Regulatory Posture applies to this provider. Its tags matched the Payments 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/lawpay/"><img src="https://apis.io/badge/lawpay/card.svg" alt="LawPay 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
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

12 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 26.3 — up to +18.4 composite points
Developer Ergonomics scores 38.1 — up to +12.4 composite points
Operational Transparency scores 10.5 — up to +11.6 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/lawpay/apis.yml: open an issue on github.com/api-evangelist/lawpay 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 →

APIs 2

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

LawPay API

LawPay provides payment processing APIs for legal professionals. Documentation is available at the LLM Info page.

LawPay API

LawPay API as documented publicly: 74 operations. Contract generated from the documentation by API Evangelist (2026-10-26); not the provider's own document.

Pricing Plans 1

Published pricing tiers and plan structures.

Lawpay Plans Pricing

1 plans

PLANS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Lawpay Context

99 classes · 173 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LawPay API Rules

11 rules · 9 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

DeleteInvoicesInvoiceidAttachmentsAttachmentidResponse

21 properties

JSON SCHEMA

GetBankAccountsBankaccountidSurchargeResponse

6 properties

JSON SCHEMA

GetInvoicesInvoiceidResponse

21 properties

JSON SCHEMA

PatchInvoicesInvoiceidResponse

22 properties

JSON SCHEMA

PostContactsContactidMakePaymentResponse

24 properties

JSON SCHEMA

PostMerchantApplicationsSignUpRequest

35 properties

JSON SCHEMA

Security Posture 1

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

Lawpay Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Login

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Access & Security 4

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: lawpay
name: LawPay
image: https://www.lawpay.com/asset-og-lawpay-default.webp
description: LawPay provides payment processing solutions tailored for legal professionals, offering secure, compliant, and
  IOLTA‑ready credit card, debit, and eCheck transactions. Founded in 2005, LawPay serves over 50,000 law firms, integrating
  with practice management software and supporting online billing, recurring payments, and mobile apps. The platform emphasizes
  data security, fraud protection, and seamless client experiences, helping attorneys focus on their practice rather than
  payment logistics.
url: https://raw.githubusercontent.com/api-evangelist/lawpay/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-26 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-26'
modified: '2026-10-26'
tags:
- Company
- Payments
- LegalTech
- FinTech
- SaaS
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/lawpay-plans-pricing.yml
- type: Spectral
  url: rules/lawpay-rules.yml
- type: JSONLD
  url: json-ld/lawpay-context.jsonld
- type: Vocabulary
  url: vocabulary/lawpay-vocabulary.yml
- type: DataModel
  url: data-model/lawpay-data-model.yml
- type: Conformance
  url: conformance/lawpay-conformance.yml
- type: LLMsTxt
  url: llms/lawpay-llms.txt
- type: SecurityTxt
  url: well-known/lawpay-supportcenter-security.txt
- type: SecurityTxt
  url: well-known/lawpay-help-security.txt
- type: WellKnown
  url: well-known/lawpay-well-known.yml
- type: Hosts
  url: hosts/lawpay-hosts.yml
- type: Vendors
  url: vendors/lawpay-vendors.yml
- type: Security
  url: https://www.lawpay.com/about/blog/category/security
- type: Newsroom
  url: https://www.lawpay.com/about/news/
- type: Login
  url: https://www.lawpay.com/login/
- type: DeveloperPortal
  url: https://portal.lawpay.com/
- type: GettingStarted
  url: https://help.lawpay.com/en/articles/10080776-8am-lawpay-quick-start-guide
- type: DomainSecurity
  url: security/lawpay-domain-security.yml
- type: Website
  url: https://www.lawpay.com/
- type: Blog
  url: https://www.lawpay.com/about/blog/
- type: Documentation
  url: https://www.lawpay.com/llm-info/
- type: Support
  url: https://www.lawpay.com/support/resources/
- type: Pricing
  url: https://www.lawpay.com/pricing/
- type: TermsOfService
  url: https://www.8am.com/terms-of-service/
- type: PrivacyPolicy
  url: https://www.8am.com/privacy-policy/
apis:
- name: LawPay API
  description: LawPay provides payment processing APIs for legal professionals. Documentation is available at the LLM Info
    page.
  humanURL: https://www.lawpay.com/llm-info/
  aid: lawpay:lawpay-api-2
- aid: lawpay:lawpay-api
  name: LawPay API
  description: 'LawPay API as documented publicly: 74 operations. Contract generated from the documentation by API Evangelist
    (2026-10-26); not

    the provider''s own document.'
  humanURL: https://developers.8am.com/reference/api
  baseURL: https://api.8am.com
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/lawpay-openapi-generated.yml
    x-provenance: generated
  - type: JSONSchema
    url: json-schema/lawpay-post-merchant-applications-sign-up-request-schema.json
  - type: JSONSchema
    url: json-schema/lawpay-post-contacts-contactid-make-payment-response-schema.json
  - type: JSONSchema
    url: json-schema/lawpay-patch-invoices-invoiceid-response-schema.json
  - type: JSONSchema
    url: json-schema/lawpay-delete-invoices-invoiceid-attachments-attachmentid-response-schema.json
  - type: JSONSchema
    url: json-schema/lawpay-get-invoices-invoiceid-response-schema.json
  - type: JSONSchema
    url: json-schema/lawpay-get-bank-accounts-bankaccountid-surcharge-response-schema.json
x-submission-probe: 200 2026-10-25
x-coverage:
  state: unreadable
  reason: js-rendered-docs
  detail: Documentation pages are rendered via JavaScript and no machine‑readable OpenAPI spec is publicly available.
  evidence:
  - url: https://www.lawpay.com/llm-info/
    status: 200
  checked: '2026-10-26'
x-enrichment:
  date: '2026-10-26'
  status: enriched
  artifacts_added: 24
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

LawPay API — frequently asked questions

Does LawPay have an API?

Yes. APIs.io lists 2 APIs from LawPay, including LawPay API and LawPay API.

Is there an OpenAPI specification for the LawPay API?

Yes. APIs.io indexes 1 OpenAPI specification for LawPay, each linked for download from this page.

How much does the LawPay API cost?

APIs.io lists 1 pricing plan for LawPay, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the LawPay API ready for AI agents?

LawPay has a Kin Score of 36.9 out of 100 (thin) and an Agent Readiness score of 12.9 (agent-aware), scored by API Evangelist on 2026-10-31.

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

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.