Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Headnote website screenshot

Headnote

Headnote is a legal payments and accounts-receivable platform built specifically for law firms. Founded in 2016 by attorney Sarah Schaaf, it lets firms accept trust-compliant credit card and eCheck (ACH) payments via shareable payment links and a hosted client payment portal, then automates collections, AR tracking, and client NPS/satisfaction reporting. Headnote is designed to be 100% compliant with IOLTA rules, the ABA Model Rules of Professional Conduct, and lawyer trust/operating account requirements across all 50 states, and integrates with existing billing and practice-management software by attaching a Headnote payment link to invoices. Card and bank data are tokenized with Stripe and Plaid and the platform runs on AWS with PCI-compliant, encrypted-at-rest-and-in-transit infrastructure. Headnote was acquired by ASG LegalTech (an Alpine Investors platform, alongside PracticePanther, Bill4Time, and MerusCase) in 2020. It was surfaced in the API Evangelist network as a portfolio company of Uncork Capital. Headnote does not publish a public developer API, OpenAPI, or developer portal; this profile is an identity record.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Headnote the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Headnote scores 19.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 19.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Payments 6.2 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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

How we profile Headnote

Each block below is one kind of artifact we hold for Headnote. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Headnote Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for Headnote — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/headnote · machine-readable index on apis.io