Docs
Quickstart and SDK usage.
Quickstart
1. Start it
ActaSeal runs in your own infrastructure under Docker Compose:
docker compose up --build
A demonstration set-up starts with sample users and nothing to configure. A production deployment uses your own database, signing key and administrator account. The deployment guide supplied with the software gives the exact settings for each.
2. First-run setup
Sign in with the administrator account you set at start-up, or through your identity provider. A fresh production deployment has no policy loaded: it is healthy, and it refuses every decision with a named reason until you load one.
3. First receipt
With a policy loaded, every decision the gateway makes produces a signed receipt. A runnable
end-to-end example, including a real signed receipt with a bound terms_hash, is
included with every deployment.
4. Verify offline
actaseal verify-receipt --receipt receipt.json --ledger ledger.json --keys keys.json
Or, with no ActaSeal installation at all -- only the public key and the standalone verifier -- use verify.actaseal.com.
API reference
Every deployment serves the reference for its own API, so what you read always matches the version you are running. Most integrations do not need it: the SDKs below make the calls.
SDKs
Python
from actaseal.sdk.thin_client import ActaSeal
guard = ActaSeal(
"https://gateway.example.com", api_key="...",
policy_id="refunds_policy", policy_version="refunds_policy.v1",
)
decision = guard.guard({"action_type": "refund_request", "money": {"amount": "50.00", "currency": "USD"}})
TypeScript
The TypeScript SDK is not published to npm. It is supplied as a package file on request, and installed from that file rather than by name. The snippet below shows its API; it runs after that package is installed.
import { ActaSeal, ActaSealBlocked, ActaSealApprovalRequired } from "@actaseal/sdk";
const guard = new ActaSeal("https://gateway.example.com", { apiKey: "..." });
const sendRefund = guard.wrap(
(amount) => fetch("https://billing.example.com/refund", { method: "POST", body: amount }),
(amount) => ({ action_type: "refund_request", money: { amount, currency: "USD" } }),
);
LangChain / LangGraph
from actaseal.sdk.integrations.langchain_tools import guard_langchain_tool guarded_tool = guard_langchain_tool(guard, my_refund_tool, action_type="refund_request") # BLOCK -> langchain_core.tools.ToolException (surfaced to the model as a tool error) # APPROVAL_REQUIRED -> ActaSealApprovalRequired re-raised for your own retry/escalation logic
OpenAI Agents SDK
Wrap the plain function first, then hand the wrapped function to the SDK to make the tool.
from agents import function_tool from actaseal.sdk.integrations.openai_agents_tools import guard_openai_agents_tool guarded_send_refund = guard_openai_agents_tool(guard, send_refund, action_type="refund_request") refund_tool = function_tool(guarded_send_refund) # A blocked or approval-held call does not run send_refund; the model sees a tool error.
Both adapters are optional imports -- actaseal imports cleanly with neither
framework installed.
MCP
To put ActaSeal in front of an MCP tool server, run the proxy as its own process and point your agent's MCP server setting at it instead of at the tool server:
python -m actaseal.mcp --config proxy.json
Every tools/call is decided first. Only an allowed call is forwarded to the tool
server; a blocked or held call is answered by the proxy and never reaches it.
A tool whose policy requires evidence gets it in the call's _meta, under the
key com.actaseal/evidence: a list of signed evidence packets, the same ones the
SDKs pass. The gateway verifies them and removes it before forwarding, so the evidence never
reaches the tool server. A call held for evidence is told what is required.
One limit of the proxy, stated rather than left to be found: every mapped tool call must carry an amount and currency. The proxy is built for tools that move money or commit to a customer.
Claude connector
A remote MCP server that lets Claude check a refunds export you share in a conversation. Two tools, both read-only:
check_refunds: refunds that broke your refund rule (when you give the limits), duplicate and excessive refunds, repeat claimants, refunds still owed to customers, and refunds with no GST credit note (when you share the credit-note register).draft_credit_notes: draft GST credit notes, one per order, for refunds that have none in the register. Without a GST rate the tax is left blank, never guessed.
It is the same check as /refund-audit/. It stores nothing, needs no sign-in and never moves money; see privacy. Each file is capped at 2,000,000 characters.
It is not in the Claude Connectors Directory yet. For early access, or questions: sales@actaseal.com.
Standards work
draft-xg-payment-dispute-profile -- see the proof section on the landing page for the full list of public standards work and links.
Signature algorithms
Receipts are signed with Ed25519 by default. They can instead be signed with ML-DSA-65 or
ML-DSA-87, or with Ed25519 and ML-DSA-65 together (hybrid). The post-quantum algorithms need the
optional liboqs-python package on the machine that signs and on the machine that
verifies; without it the offline verifier says the algorithm is unsupported rather than passing
the receipt. Conformance vectors for each are in the
public repository.