Customer service
96%
Tickets resolved.
83% → 96% vs the agent alone.
Tide-EnterpriseExplore the use caseTide-1 API
Decision infrastructure for AI agents.
Rippletide checks agent actions against your company’s policies and shows you why a decision was made.
You're on the list.
We'll contact you at about Tide-1 API access.
Coming soon Tide-1 · for builders · Tide it
Decision models / Performance
Results so far.
IAM approvals
96%
Correct access decisions.
Over 9K replayed decisions.
Tide-EnterpriseSee the evidenceCode diff review
1 line
Catch a cross-customer data leak.
Happy path passes. Isolation test fails.
Tide-1Run the sample testsCredit
98.9%
Correct credit assignments.
100+ cases.
Tide-EnterpriseExplore the use caseCustomers & design partners
01 / Tide-1 playground
Tide it.
Customer service agent
Same return. Two customers. Two decisions.
A shopper returns an item after 37 days. Your agent serves two stores with different return policies.
North Store
30-day policyDecline return
37 days is outside this customer's 30-day window.
"action": "decline_return"South Store
45-day policyApprove return
37 days is within this customer's 45-day window.
"action": "approve_return"One agent. Each customer's decision model.Switch the customer, keep the integration.
Code review agent
Teach it once. Catch the next unsafe change.
A patch passes the happy path but exposes another customer's data. Correct the decision, then test the same mistake in a new file.
Executable checks2 / 3 pass
Only the happy path and unknown-record check inform the decision.
Make account isolation part of the next decision.
Your feedback
“Reject any change that can return another customer's data.”
The next decision uses your correction.Same agent integration. Updated decision behavior.
How these examples work
These interactive examples run the JavaScript shown here in your browser. The feedback example applies a structured correction to the next sample decision-policy version. It demonstrates the workflow; it does not call a hosted Tide-1 model.
Customer support agent
Send the ticket. Get the next step.
Illustration
Question
The blender arrived cracked. What should the agent do?
Choices
- Send a replacement
- Refund in full
- Store credit
- Ask for photos
Context
- order
- KX-200 blender, delivered 2 days ago
- message
- It arrived cracked. I still want one.
Recommended
Send a replacement
Memory used: 2 of 12 facts
- Replacement KX-200s ship in 2 days.
- Photos of the crack are on the ticket.
Policy applied
- Damaged on arrival: offer a replacement before a refund.
12 facts. Each question recalls only the ones that match it.
- Replacement KX-200s ship in 2 days.recalled
- Photos of the crack are on the ticket.recalled
- Refunds go back to the original payment method.
- Gift card payments come back as store credit.
- Gold members get free return shipping.
- Orders ship from the Lyon warehouse.
- Final sale items cannot be returned.
- Customers can swap a size once, free.
- Store credit never expires.
- Support replies within one business day.
- Bundles are returned as a whole.
- Prices are in euros, taxes included.
Every active Policy applies to every decision in this bank.
- Damaged on arrival: offer a replacement before a refund.damaged_first
- Refunds over €500 need a manager’s approval.refund_manager
- Never refund an opened item in full after 30 days.opened_window
Customer support agent
Correct it once. The next decision changes.
Illustration
Question
Opened kettle, returned 41 days after delivery. What should the agent do?
Choices
- Store credit
- Decline
- Refund in full
Context
- customer
- Gold member
- days
- 41
Recommended
Store credit
Was Decline, before your correction.
Memory used: 2 of 13 facts
- Gold members get store credit up to 45 days. Your correction
- Opened items: 30-day return window.
Policy applied
- Never refund an opened item in full after 30 days.
13 facts. Each question recalls only the ones that match it.
- Gold members get store credit up to 45 days. Your correctionrecalled
- Opened items: 30-day return window.recalled
- Refunds go back to the original payment method.
- Gift card payments come back as store credit.
- Gold members get free return shipping.
- Orders ship from the Lyon warehouse.
- Final sale items cannot be returned.
- Customers can swap a size once, free.
- Store credit never expires.
- Support replies within one business day.
- Bundles are returned as a whole.
- Prices are in euros, taxes included.
Every active Policy applies to every decision in this bank.
- Damaged on arrival: offer a replacement before a refund.damaged_first
- Refunds over €500 need a manager’s approval.refund_manager
- Never refund an opened item in full after 30 days.opened_window
Illustration: placeholder facts and scores, not a live Tide-1 call.
Request early access02 / Use cases
Every job has decisions with a right answer.
Customer service agent
Refund or replace? It depends on the store.
Use the right store policy, order facts, and customer exceptions to choose the next step.
Input: ticket + customer policy + current facts Choices: replace / refund / request information Output: the next decision for your support agent
customer_model: north_storeTry the playground
KPI96% of tickets resolved
83% → 96% vs the agent alone
Consumer goods group, benchmark on new casesIncident investigation agent
Five likely causes. Investigate the right one first.
Evaluate competing root-cause hypotheses against incident evidence, so the agent can pursue the cause that best explains what happened.
Input: incident evidence + candidate causes Choices: recent change / dependency / configuration Output: the best-supported cause to investigate
Up to +100% Top-1 RCA accuracy
Relative improvement vs. compared solutions
Coding agent / Code diff review
The tests pass, but the diff still leaks customer data.
A lookup still returns the expected order, but now exposes other customers’ orders too. Find the missing account check. Run the tests, apply the fix, and test again.
- orders.find(order => order.id === orderId && order.accountId === accountId) + orders.find(order => order.id === orderId)
1 critical access check
2/3 → 3/3 sample checks Tide-1
Financing agent
Approve now, or ask for the missing document first.
Use application facts, documents, and business criteria to determine what can proceed and what needs a missing document or further review.
Input: application + supporting documents + criteria Choices: proceed / request document / refer for review Output: the next step for the financing agent
98.9% correct credit assignment
100+ cases Automotive group
Portable decisions
New model, same rules. Nothing to re-teach.
Keep your policies, corrections, and learned specialization when you switch agents. Your GPT-based agent, Claude-based agent, or next workflow calls the same decision model. No re-teaching the business rules.
03 / Tide-Enterprise
Connect your data,
agent-ready or not.
01 / Source systems → hypergraph
Add a document, played through. Device return policy is dropped in. Rippletide reads its 3 clauses one at a time. §1 Return window: A faulty device can be refunded within 30 days of delivery, dated by the carrier record. Becomes a Draft Rule. §2 After the window: After 30 days, a faulty device is replaced under warranty instead of refunded. No Rule: an instruction for the agent. §3 Proof of delivery: With no delivery date on the order, ask the customer for it before any refund. No Rule: an instruction for the agent. Then the document connects to the Map: Source, Device return policy, new; Rule, Refund a device only within 30 days of delivery, a Draft, new; Action, refund_customer, already there, now linked. Rules from a document start as Drafts.
02 / Source-quality checks
Reconcile your data before your agent uses it.
The Resolve step of Add a document, played through. Rippletide checks Device return policy against the 4 Sources and Systems it touches: CRM · Accounts, System · 2,140 accounts; ERP · Customers, System · 2,163 customers; Help center · Returns, Source v4 · Zendesk; Order API, System · 18,420 orders. Three flags appear one by one. Inconsistent: One customer, two records, CRM ACME-FR and ERP ACMEFR. Linked automatically. Same registration ID: 552 100 554. Conflicting: Two refund windows for a faulty device. The approved policy and the help center disagree: 30 days, Approved policy, §1, or 14 days, Help center article. 30 days is picked; the Draft Rule uses it: Refund a device only within 30 days of delivery. Saved. Rippletide reuses it when they disagree again. Missing: No delivery date on orders. The Order API returns no delivery date. Until then, the Rule asks the customer for the date. Hypergraph built: 3 flags handled, one Draft Rule.
03 / Runtime enforcement
Your Rules apply every time your agent acts.
Enforce each Rule when you're ready. Every decision traces back to its Rule and Source.
The Map, one question played through. The question is typed into the ask box: A phone delivered 41 days ago is faulty, and the customer wants a refund. Refund or replace? Then Ask. The chain lights in order: Source, Device return policy; Rule, Refund a device only within 30 days of delivery, in Observe; Action, refund_customer. The answer: Recommended: send_replacement. Delivered 41 days ago, past the 30-day refund window. In Observe, Rippletide records this and lets refund_customer run. Then the Rule moves from Observe to Enforce: Blocked: refund_customer. In Enforce, Rippletide stops refund_customer before it runs.
Usable business dataShared decision referenceExplainability & traceability
04 / Enterprise evidence
Then let your
agents cook.
Consumer goods / Customer service
76.5%
Fewer unresolved tickets
Resolution: 83% → 96% vs the agent alone.
Benchmark on new cases.
Automotive / Credit
98.9%
Correct credit assignments
100+ cases.
Credit policies turned into executable rules.
Enterprise software / IAM approvals
96%
Correct access decisions
2% escalated, 2% incorrect. Over 9K decisions replayed.
383 business rules made explicit.
Each result comes from a separate customer evaluation.
For the agent you are building
Bring the decision
your agent needs to get right.
Tide-1 is in closed beta. Leave your email and we’ll reach out.
You're on the list.
We'll contact you at about Tide-1 API access.