The API for legal entities.
Form, run and close companies in six countries with one endpoint. Every corporate action, every entity type and every rule your systems need to act safely.
Overview
Every corporate action, in every jurisdiction, is the same call with a different type. You send the change you want. Entiva tells you what it needs, prices it up front, collects the people, documents and signatures the law requires, files it with the registry and returns the result.
https://api.entiva.com/v1, with sk_live_ keys.
https://sandbox.api.entiva.com/v1, with sk_test_ keys. Filings are simulated end to end.
ak_test_ and ak_live_ keys are bound to a mandate that limits what an AI agent may do and spend.
Send Entiva-Version: 2026-10-17. Breaking changes only ship in new dated versions.
Machine-readable
Your first request
Form a private company in Hong Kong. The response is an action that lists what is still needed.
Concepts
Actions
An action is one corporate change: a formation, a director appointment, an annual return, a share transfer or a winding up. Every action moves through the same states.
Requirements
While an action is requirements_pending, its requirements list what blocks it: a person to verify, a document to upload, a signature to collect, an approval or a government fee. Each requirement names the endpoint that clears it.
Quotes and fees
Every action carries a quote before you approve it. The Entiva fee is free for formation, included in the Run plan for routine changes, or fixed for larger work. Government fees are passed through at cost.
People and verification
Every director, secretary, shareholder, beneficial owner, controller and partner is a person. Each is verified once, to the level the role and jurisdiction require, and reused across every entity they touch.
Governance and approvals
An action's approvals come from three sources, resolved in order, each with its citation: what the law requires, what the entity's articles add, and what its shareholders' agreements reserve. The first two bind by law, the third by contract, and a contractual consent blocks the action until it is given or an owner waives it on the record.
Formation takes the entity's governance: share classes, signing authority, board rules, reserved matters and transfer restrictions. Entiva generates the articles, and a shareholders' agreement if you want one, from those choices, so the governance profile is confirmed from day one.
Upload the articles and any agreements. Entiva reads them into a governance profile with clause references, and a person confirms it before it applies.
Amending the articles or signing a new agreement replaces the earlier version, and the profile updates with it.
Signatures
Each document an action needs has a signature method and a rule for whether an AI agent may sign it. The rules come from each jurisdiction's electronic signature law and registry practice.
Webhooks
Every event is signed with Entiva-Signature, an HMAC-SHA256 of the payload with your endpoint secret.
Errors
Naming
One word for one thing, in every jurisdiction. Legal forms keep their local names; everything around them follows one vocabulary.
Conventions
Prefixed by type: acct_ account, usr_ user, ent_ entity, act_ action, per_ person, ver_ verification, scr_ screening alert, doc_ document, sig_ signature request, man_ mandate, key_ key, evt_ event.
Send an Idempotency-Key header with every write. A retried request returns the original result.
Every object takes up to 50 string keys of your own references.
expand[] inlines related objects. Lists return object, data, has_more and url.
Accounts and identity
Every customer has an account, and every person behind it is verified once. Identity checks run through specialist providers behind one API, so you never integrate a provider yourself.
Getting started
How people, agents and platforms get an account, and how a person is verified.
Account status
An account starts in the sandbox, where everything works in test mode. Its requirements list what live mode still needs, and by when.
Users and roles
Authority to act
Four checks stand between a request and a filing. Each is in the API, and each failure returns a permission error that names what is missing.
Keys and sign-in
Identity verification
A verification checks one person to the level their roles need. The person completes it on a hosted page, in your app with the Entiva SDK, or by signing in with a government digital ID. The result has the same shape whichever provider ran each check.
Checks
Rules by jurisdiction
Each check runs through a certified specialist provider for that country and document. Entiva can switch providers without changing your integration.
Screening
Every verified person is screened against sanctions, PEP and adverse media lists, then again every day while they hold a role. Entiva compliance reviews every possible match. An open sanctions alert pauses live actions that involve the person.
What agents can do
Test values
In test mode the person's email decides the outcome.
Events and errors
Endpoints
Objects
Agents and MCP
AI agents use the same API through the Entiva MCP server. An agent finds the action it needs, reads its rules, starts it and clears its requirements. It can never sign where the law needs a person.
Connect an agent
Tools
Mandates
A person gives an agent standing authority with a mandate: which actions, which entities, a spending limit, an approval threshold and an expiry. Where the law needs it, the mandate produces a power of attorney the person signs once.
Where an agent may sign
Whether software may apply a signature for a person, by jurisdiction.
Jurisdictions
Entity types, signature rules, verification levels and lifecycles, by jurisdiction.
Action reference
Every corporate action as an API call, with its parameters, documents, people, approvals, signatures, filing and fees.