Labs · Agent Agreement Preflight
Check a signature request before your agent sends it
Your agent drafts an NDA, a service agreement, a lease. Before anyone is asked to sign, this check says whether the request is ready, needs your approval, or is blocked — and exactly why. It never signs, never sends, and never says whether a signature is legally valid.
Not an e-signature service
Jithox does not sign, does not send, does not store your document and does not talk to a signature provider. Only the document's fingerprint (a sha256 hash) and opaque references travel. The decision is a deterministic policy check, not legal advice.
Step 1 of 4 · What will be signed. Nothing is signed or sent by this page.
Five everyday cases
Open one to see the full check with its reasons. Every example is invented; nothing was signed or sent.
What will be signed
Choose the file and the fingerprint is computed in your browser; the file never leaves your device. Or paste a 64-character hash.
How it works
1 · Your agent describes the request
Document fingerprint and version, who signs with which authority, data class, country and signature level, expiry, provider and budget, evidence.
2 · Jithox checks it deterministically
The same request always gets the same decision: policy rules, no model, no lookups, no storage.
3 · You decide
Ready, needs approval, or blocked — with reasons and an approval reference you can approve. Sending stays with you and your provider.
How Jithox's own teams use it
Four teams, four requests, four decisions on a fixed clock. Demonstrations, not live requests.
Evaluated on the fixed clock 2026-09-10T12:00:00Z, so everyone sees the same answer.
MCP/Agent Tooling
Partner terms for a new MCP integrator
The tooling bot prepared partner terms for an integrator. The counterparty is external and the document is confidential, so the owner approves this exact request before it leaves.
exclamation markNeeds your approval
external_recipients · data_class_requires_approval · approval_missing
Security
Pentest authorisation letter drafted by the agent
The security bot wanted to be recorded as the signer of a customer's authorisation letter. An agent never signs by itself: without a standing grant with scope and expiry the request is blocked.
crossBlocked
signer_role_unsupported_for_agent · external_recipients · data_class_requires_approval · signature_level_unknown · approval_missing
Commerce
Reseller agreement with a web shop, approved
The commerce bot prepared a reseller agreement; the owner already approved this exact hash. External and within budget, so it is ready to prepare — sending stays with the owner.
check markReady to prepare
external_recipients · approval_valid
First Cash
Statement of work with a client, over budget
The first-cash bot prepared a statement of work and picked a provider whose estimated cost is above the stated budget. Blocked until the budget or the provider changes; nothing is charged.
crossBlocked
external_recipients · budget_exceeded · approval_missing
What is true about this check
- It is a policy check, not legal advice: it says nothing about whether a signature is legally valid.
- Only the document's sha256 fingerprint travels; the document itself never does.
- Signers are opaque references; an e-mail address, phone number or bank account is refused.
- An AI agent is never the signer: it may act only under a recorded standing grant or representation, with scope and expiry.
- Anything that reaches someone outside your workspace needs your approval of the exact request hash.
- The provider cost is estimated beforehand and compared with your budget; nothing is charged by this check.
- The receipt is unsigned and hash-bound; anyone can recompute it.
- It is a free Labs preview: not sold, not in the sitemap, not a promise.
What this never does
- Sign a document.
- Claim a legal identity.
- Send a signature request.
- Consent on anyone's behalf.
- Store a raw document.
- Call an external provider.
- Claim a signature is legally valid.
- Send customer data to a model.
Free. The interactive check, the API and the connection tool cost nothing in this build; a paid receipted check is a proposal for the owner, not a price. Status: preview local build.
Developer details
Three free routes and one connection tool. The request and result schemas are closed; every decision, reason code and error code is listed in the schema document.
Developer details
- Schema:
- GET https://jithox.com/api/agreement-preflight/v1/schema
- Evaluate:
- POST https://jithox.com/api/agreement-preflight/v1/evaluate
- Fixtures:
- GET https://jithox.com/api/agreement-preflight/v1/fixtures
- Policy:
- jithox.agreement-preflight-policy/v1 · 60/min
- MCP:
- agreement_preflight @ https://jithox.com/api/agent-connection/v1/mcp · CONFIG_READY
- Decisions:
- READY_TO_PREPARE · NEEDS_APPROVAL · BLOCKED · UNAVAILABLE
Through your Jithox connection the tool is called agreement_preflight and needs the scope actions:prepare:agent-agreement-preflight. CONFIG_READY: listed and callable; no client is CERTIFIED against it until a production canary has run.