FinePrint API · for platforms

The API for corporate legal actions.

An agent can’t decide that a legally significant action occurred. Your product can call an endpoint that makes one real.

Idempotent calls · signed webhooks · every action returns an auditable trace.

Illustrative call. Northwind Robotics is the fictional sample company used across this site.

What an endpoint is

An endpoint completes the action — not just the paperwork.

One endpoint is one recurring corporate action, executed end to end. Call it with the facts your product already has.

The same 41 endpoints the AI-Counsel runs — no second system, no lighter version for platforms.

The five things that make a corporate action legally real are the five things nobody wants to build.

Browse the endpoint library →
DocumentsDrafted from this company’s own record and charter, not a template you have to keep current.
ApprovalsA grant is not valid until the board authorizes it. The endpoint drafts the consent, routes it, and waits — the grant dates from the last signature.
SignaturesSigning order, counterparts, binding. You get an event when everything is bound, with signer identities and the document hash.
FilingsForm D after a first sale, the annual report, the 83(b) inside its 30-day window — filed, with the receipt kept as evidence.
Record updatesCap table, minute book, people and timeline are written as part of the same action.

Platform calls

Five calls your product is missing today.

Your product already knows a legally significant thing happened. It just can’t do anything about it.

01
Banks & neobanksPOST /v1/endpoints/incorporate

Form the company at account opening — charter, EIN, initial consent, founder stock with vesting — so the account belongs to a real entity on day one.

02
Payroll platformsPOST /v1/endpoints/hire-employee

Run the hire payroll assumes already happened: offer letter, invention assignment, the state notices this role requires, and the option grant.

03
Cap-table toolsPOST /v1/endpoints/issue-safe

Issue the SAFE instead of recording one that happened elsewhere — authorization, documents, signatures, cap-table write, Form D.

04
Accelerators & studiosPOST /v1/endpoints/incorporate × 40

Form the whole batch on one morning, with the same clean records — and catch missing 83(b) elections inside the 30-day window.

05
Vertical SaaSPOST /v1/endpoints/create-nda

Your workflow ends in an agreement: the NDA before the files move, the contract before the job starts — drafted from your customer’s own positions.

Traces & webhooks

Every legal action emits an auditable event.

Legal work finishes on its own schedule — a signature on Thursday, a filing overnight. So every run is a sequence of events, not one response.

GET /v1/events?run=run_2f8c41x-fineprint-signature: v1=9c2e…
09:37:04  approval.completed      consent_9d21 · 3/3 signed
09:37:22  document.drafted        safe_post_money · 3 docs
09:38:10  signature.completed     bound · sha256 4f1c…8ab0
09:38:41  record.updated          ownership · +1 instrument
09:38:42  filing.scheduled        Form D · 15d of first sale
09:38:42  obligation.created      pro_rata · 409a_refresh
09:38:43  legal.action.completed  run_2f8c41 · trace kept

Illustrative event stream for the fictional sample company.

Signed, so you can trust itEvery delivery carries an x-fineprint-signature computed over a per-endpoint secret you rotate without downtime. Verify the signature, not the source address.
Idempotent, so retries are safeCalls take an idempotency key — a retry after a timeout resumes the run instead of closing a second SAFE. Events deliver at least once.
Replayable, so your state rebuildsEvery event carries the company id and the run id. Replaying the stream reconstructs your view without an extra call.
Auditable, for as long as the company existsThe trace is the record: every step, every approval, every hash — still readable years later, when diligence asks why the cap table says what it says.

The agentic argument

An agent can't decide that a legally significant action occurred.

Agents will create businesses, hire contractors and raise capital. Software intent still needs a legal act behind it.

That infrastructure needs:

identityauthorityapprovalsdocumentssignaturescorporate recordsjurisdictional rulescomplianceaudit trailshuman escalation
The call returns a level, with reasonsEvery call comes back Green, Yellow or Red, scored from observable signals — completeness of facts, jurisdiction, novelty, exposure. Your code branches on the level.
The boundary moves. You inherit it.What needs a lawyer today may be routine next year. As reviewed work accumulates, the line between Green and Yellow moves.

FinePrint is that infrastructure — agents call the same endpoints.

Sandbox & access

Test the escalation path before you ship the happy one.

Legal actions are not reversible the way a test charge is, so the sandbox is not a stub.

Sandbox companies

Real workflows, no registry.

Real documents, real approval routing, real webhooks. Nothing touches a registry — but ask sandbox for a Yellow and you get one.

Test filings

File without consequences.

Run the annual report, the 83(b) and the Form D end to end, with the same receipts and events live sends.

Full traces

Every sandbox run is auditable too.

Sandbox runs return the same trace live runs do, replayable from /v1/events. Keys are scoped per environment.

Getting access

The API is in private access. Tell us what you would call, how often, and which jurisdictions your customers are in.

API access is part of Scale, from $1,000/mo; platform volume is priced directly.

The legal department every startup should have.

Find your gaps before someone else does.

Four minutes. Free. You keep the report either way.