Businesses using AI
Your team already uses ChatGPT, Claude, agents, and automations. The recommendations that matter deserve a record that outlives the chat window.
THE DECISION RECORD FOR BUSINESS AI
Use powerful AI.
Keep proof of every decision.
StoneAI puts an important question to a council of AI models, seals the result with a SHA-256 hash, binds every decision to that exact content with an Ed25519 signature, and writes it to a hash-chained ledger anyone can verify.
AI recommends. Your people decide. StoneAI keeps the receipt.
STONEAI DECREE● AWAITING DECISION
REQUESTGive a new AI agent access to customer billing.
Seat AApprove with limits
Seat BApprove with limits
Seat CHold
COUNCIL RECOMMENDS · 2 OF 3 SEATSApprove with limits
Example data — for illustration.
THE SIMPLE VERSION
StoneAI is the permanent record of what your AI recommended and who said yes.
AI is fast and useful — and it can be confidently wrong. When a recommendation matters, you need to know what was asked, what the models said, what was decided, and whether anyone changed the record afterward. StoneAI answers all four with cryptography, not screenshots.
WHO NEEDS IT?
If an AI recommendation can become a real decision, you need a record of it.
Regulated organizations
Healthcare, finance, insurance, and legal teams are asked to show who decided and why. StoneAI produces signed, hash-chained, publicly verifiable decision records — the kind of evidence auditors ask for. StoneAI itself holds no certifications.
Teams making high-stakes calls
Access grants, refunds, deployments, payments. When an AI recommendation leads to a real consequence, the decision should be bound to exactly what was reviewed.
Fast-growing companies
More tools and more people make decisions easy to lose. StoneAI keeps every decree and every decision in one ledger per organization, isolated from every other customer.
Leaders and boards
You want the speed of AI and an answer to “who approved this?” that still holds up a year from now.
IT and security teams
Decisions reach your systems as HMAC-signed webhooks. API keys are scoped to your organization and can be revoked the moment you need to.
WHY BUY IT?
Because “we trust the AI” is not a business plan.
Without StoneAIOne AI gives one answer.
You may never know what it missed.
Without StoneAIApprovals live in chat and email.
Nothing ties a “yes” to the exact thing that was reviewed.
Without StoneAIRecords can be quietly edited.
There is no clean proof for a customer, board, or auditor.
With StoneAIEvery decision is sealed, signed, chained, and verifiable by anyone you share it with.
HOW IT WORKS
Five steps between a request and a decision you can prove.
You ask
Your application sends StoneAI a question or a proposed action through the API.
The council votes
Several model seats give an opinion. The majority wins, ties break deterministically, and dissent is kept. If every seat fails, the answer is “hold.”
StoneAI seals it
The result becomes a decree, sealed with a SHA-256 content hash. A decree carries no credentials and cannot act on anything by itself.
Your people decide
An approver approves or rejects. The decision is Ed25519-signed and bound to the decree’s hash. A decree takes one decision; a second is refused.
Your systems act
StoneAI records the decision and notifies your systems by signed webhook. It never executes inside them — your code acts on a verified decision.
WHAT YOU ACTUALLY GET
Evidence you can check, not promises you have to believe.
AI council Live
Multi-model by design: seats vote, the majority decides, dissent is preserved. Today the live council runs on fewer independent providers than it is designed for — the status page reports what is actually observed.
Signed decisions Live
Every approval or rejection is Ed25519-signed over the decree, approver, scope, content hash, nonce, and expiry. Change one word and verification fails.
Audit ledger Live
Hash-chained per organization. Each entry commits to the one before it, and the database refuses edits and deletions.
Public receipts Live
Share a link and anyone can check a decision without an account. Ledger roots are anchored hourly to OpenTimestamps on a best-effort basis.
Tenant isolation Live
Postgres row-level security, forced on, keeps each organization’s decrees, approvals, ledger, and billing records separate.
Signed webhooks Live
Decisions are delivered to your endpoint with an HMAC-SHA256 signature, so your systems can confirm the message came from StoneAI.
CLI device login Live
Sign the CLI in from your browser with a device code that expires in ten minutes (RFC 8628).
Risk-based councils Built — rolling out
Council composition that scales with the risk of the decision, with overrides that can only escalate. Implemented and tested; not yet serving customers.
WHERE WOULD YOU USE IT?
Anywhere an AI recommendation could become a real-world consequence.
EXAMPLE REQUEST
“Let this AI summarize a patient record for a clinician.”
WHAT STONEAI RECORDS
The council’s recommendation, the dissenting opinions, the approval scope required, and the clinician’s signed decision.
WHAT YOU CAN PROVE
Exactly what was approved, by which approver on record, and when — and that the record has not changed since.
Example data — for illustration.
WHY TRUST IT?
StoneAI does not ask you to “just trust us.” It keeps receipts.
Every decision is bound to the exact decree that was reviewed. Ledger entries are chained, so a quiet change breaks the chain. Anyone with the link can check a receipt — no account required. The questions it answers:
- What did the council recommend?
- What did the dissenting seats say?
- What approval scope was required?
- What was decided, and by which approver on record?
- Is the signature bound to this exact content?
- Does the ledger entry still match its hash?
S
PUBLIC RECEIPT
Decision verified
- Decision
- Approved with limits
- Ed25519 signature
- Valid
- Content hash
- Matches decree
- Ledger entry
- Valid
8C3F · 19A2 · 7E40 · B611
Example data — for illustration.
THE DIFFERENCE
A chatbot answers questions. StoneAI records what was decided.
Regular AI tool
Gives an answer
Usually one model
Approval lives in chat
History can be edited
Proof means screenshots
StoneAI
Seals the decision
Multi-model council by design
Approval signed and bound to content
Hash-chained ledger that refuses edits
Public receipts anyone can check
BUILT TO FIT YOUR BUSINESS
Connect through an API, not a rebuild.
StoneAI sits beside your AI and business systems, not inside them. Your applications call a documented REST API and receive decisions by signed webhook. Change models or tools without losing your decision history.
REST API · OpenAPI 3.1Signed webhooksCLI device loginPublic receiptsStatus page
THE BOTTOM LINE
You would not let a brilliant new hire approve a $75,000 payment and keep no record of who said yes.
So why would you do that with AI?
READY FOR ACCOUNTABLE AI?
Move fast. Keep the receipt.
Bring StoneAI in before an AI decision has to be explained to a customer, a board, or an auditor.