<div class="mb-playbook" data-pb-title="DisputeOS — Compliance Clock Engine for Reg E Dispute Resolution" data-pb-description="DisputeOS is the compliance clock engine that makes it structurally impossible to miss a Reg E deadline. Architectural gates replace bypassable alerts. Built by MightyBot for banks and fintechs. SOC 2 Type II certified." data-pb-og-title="DisputeOS — Compliance Clock Engine for Reg E Dispute Resolution" data-pb-og-description="Compliance deadlines as architectural gates, not bypassable alerts. The dispute compliance engine for banks and fintechs. Built by MightyBot." data-pb-og-image="https://cdn.prod.website-files.com/673ad7ebdf90a87e7aa3e9a8/69b39c0e628398b30bba5250_Open%20Graph.png" data-pb-og-url="https://www.mightybot.ai/agents/disputeos" data-pb-twitter-title="DisputeOS — Compliance Clock Engine for Reg E Dispute Resolution" data-pb-twitter-description="Compliance deadlines as architectural gates, not bypassable alerts. The dispute compliance engine for banks and fintechs. Built by MightyBot." data-pb-twitter-image="https://cdn.prod.website-files.com/673ad7ebdf90a87e7aa3e9a8/69b39c0e628398b30bba5250_Open%20Graph.png"><div class="page">
<!-- HERO -->
<div class="hero">
<time class="last-updated" datetime="2026-04-13">Last updated April 13, 2026</time>
<div class="eyebrow">For Banks and Fintechs</div>
<h1>Your dispute system sends alerts. Cash App's did too. They paid $175 million.</h1>
<p class="answer-lead">DisputeOS is a compliance clock engine that makes it structurally impossible for banks and fintechs to miss Reg E dispute deadlines. Deadlines become enforcement gates that block case progression until required actions complete. Full audit trail from Day 0. SOC 2 Type II certified.</p>
<div class="sub">DisputeOS is the compliance clock engine that makes it structurally impossible to miss a Reg E deadline. Deadlines become architectural gates in your system, not bypassable email notifications. When a deadline arrives without the required action, the gate blocks. No snooze button. No "I didn't see the email." Just compliance, enforced by architecture.</div>
<p class="lede"><strong>What DisputeOS does:</strong> it tracks every open dispute's compliance clock in real time, enforces mandatory state transitions at each Reg E deadline (10-day investigation, provisional credit, 45/90-day determination), and produces a complete audit trail that satisfies CFPB examination requirements. Your team stays in control. The system makes sure they can't miss what matters.</p>
<div class="cta-row">
<a class="btn btn-primary" href="https://calendly.com/mightybot-john/disputeos-design-partner-discovery?utm_source=mightybot&utm_medium=landing&utm_campaign=disputeos&utm_content=hero-cta" rel="noopener" target="_blank">Become a design partner</a>
<a class="btn btn-secondary" href="#how-it-works">See how it works</a>
</div>
<div class="hero-stats">
<div class="hero-stat">
<div class="num red">$175M</div>
<div class="lbl">Cash App Reg E penalty (2025)</div>
</div>
<div class="hero-stat">
<div class="num orange">10 days</div>
<div class="lbl">Reg E investigation deadline</div>
</div>
<div class="hero-stat">
<div class="num accent">5,000+</div>
<div class="lbl">US banks at risk</div>
</div>
<div class="hero-stat">
<div class="num green">30 days</div>
<div class="lbl">Design partner pilot</div>
</div>
</div>
</div>
<!-- ENFORCEMENT LANDSCAPE -->
<div class="section">
<h2>The enforcement landscape has changed.</h2>
<p class="section-sub">The <a href="https://www.consumerfinance.gov/enforcement/actions/" rel="noopener" target="_blank">CFPB levied $24.7 billion in enforcement actions</a> between 2021 and 2025. The largest Reg E penalty in history landed in January 2025. Every one of these failures started the same way: a system that sent alerts instead of enforcing deadlines.</p>
<div class="grid-3">
<div class="penalty-card">
<div class="amount">$175M</div>
<div class="entity">Block / Cash App</div>
<div class="cause">Failed to investigate within Reg E timelines. Failed to provide provisional credits within 10 business days.</div>
</div>
<div class="penalty-card">
<div class="amount">$870M</div>
<div class="entity">Zelle (JPMorgan / BofA / Wells)</div>
<div class="cause">Failed to conduct reasonable investigations of error notices. Alleged consumer losses.</div>
</div>
<div class="penalty-card">
<div class="amount">$20.7M</div>
<div class="entity">U.S. Bank / ReliaCard</div>
<div class="cause">Failed to timely investigate prepaid card dispute notices. Froze accounts improperly.</div>
</div>
</div>
</div>
<!-- CONTEXT -->
<div class="section">
<h2>What Reg E actually requires, in 60 seconds</h2>
<p class="section-sub">If you are a compliance officer, you know this cold. If you are a CTO or VP of Operations evaluating tools, this is what your team is responsible for on every single electronic fund transfer dispute.</p>
<div class="grid-2">
<div class="def-card">
<h3>The compliance clock</h3>
<p>When a consumer reports an error on an electronic fund transfer, <a href="https://www.consumerfinance.gov/rules-policy/regulations/1005/11/" rel="noopener" target="_blank">Regulation E (12 CFR 1005.11)</a> starts a clock. The institution has <strong>10 business days</strong> to complete the investigation OR issue a provisional credit while extending the investigation to <strong>45 calendar days</strong> (90 days for POS, out-of-state, or new account transactions).</p>
<p>Miss the 10-day gate and you owe the consumer a provisional credit. Miss the 45/90-day gate and you owe a determination plus written explanation. Miss any of these and the CFPB owns you.</p>
</div>
<div class="def-card">
<h3>Why banks fail</h3>
<p>Banks don't fail because they don't know the rules. They fail because their systems treat deadlines as <strong>email alerts that can be snoozed, ignored, or routed to someone who's on vacation.</strong> Multi-department routing causes systematic timeline breaches. Holiday calendars get miscounted. Provisional credits get mislabeled. Written confirmations delay investigation starts.</p>
<p>Every penalty in the last three years traces back to the same root cause: the system complained, but didn't enforce.</p>
</div>
</div>
</div>
<!-- THE PROBLEM -->
<div class="section">
<h2>Your current tool sends alerts. Here's what happens next.</h2>
<p class="section-sub">Whether you use Fiserv's Nautilus, FIS CBK, FINBOA, Quavo, or a spreadsheet, the failure mode is the same. Alerts are not architecture.</p>
<div class="grid-3">
<div class="card">
<h3>The alert gets lost</h3>
<p>Day 8 email: "Dispute #4721 approaching 10-day deadline." Your analyst is on PTO. The backup analyst has 47 other disputes. The email sits in a shared inbox. Day 11: the deadline passes. Nobody noticed.</p>
</div>
<div class="card">
<h3>The credit doesn't post</h3>
<p>Your analyst knows the investigation needs more time. They request the extension. But the provisional credit doesn't post to the consumer's account because the GL integration is a manual step. The system tracks the intent. Reg E requires the action.</p>
</div>
<div class="card">
<h3>The audit finds the pattern</h3>
<p>Six months later, the CFPB examiner pulls your dispute records and runs a timeline analysis. They find 23% of disputes exceeded the 10-day investigation window without a provisional credit. That's not a one-off mistake. That's a systematic violation. That's Cash App math.</p>
</div>
</div>
</div>
<!-- HOW IT WORKS -->
<div class="section" id="how-it-works">
<h2>How DisputeOS works</h2>
<p class="section-sub">DisputeOS replaces the alert model with an architectural gate model. The system doesn't notify you that a deadline is approaching. It blocks the dispute from advancing until the required action is completed.</p>
<div class="grid-2">
<div class="step-card">
<div class="step-num">1</div>
<h3>Dispute intake starts the clock</h3>
<p>Consumer reports an error (phone, branch, online, mail). The compliance clock starts immediately on oral notice. DisputeOS determines the clock variant: 10-day standard, 20-day new account, 45-day extended, or 90-day POS/out-of-state. Every subsequent deadline is computed to the business day using your institution's actual holiday calendar.</p>
</div>
<div class="step-card">
<div class="step-num">2</div>
<h3>Gate 1: Day 10 enforcement</h3>
<p>At the 10-business-day mark, the system enforces a gate. Either the investigation is complete and a determination has been made, or a provisional credit must be issued to the consumer. If neither has happened, DisputeOS blocks the dispute from advancing and escalates to a named human with audit trail. No state transition without action.</p>
</div>
<div class="step-card">
<div class="step-num">3</div>
<h3>Gate 2: Day 45/90 enforcement</h3>
<p>If the investigation was extended, the 45-day (or 90-day) calendar deadline becomes the next gate. The investigation must be completed and the consumer notified within 3 business days. If provisional credit was issued and no error is found, 5 business days notice must be provided before debiting. Every sub-deadline has its own gate.</p>
</div>
<div class="step-card">
<div class="step-num">4</div>
<h3>Complete audit trail</h3>
<p>Every action, every gate passage, every escalation, and every human override is logged with timestamp, actor, and rationale. When the CFPB examiner asks "show me the timeline for Dispute #4721," your compliance team pulls a single documen
t that answers every question. No reconstruction. No guesswork. The system was the audit trail from Day 0.</p>
</div>
</div>
</div>
<!-- BUILT DIFFERENTLY -->
<div class="section">
<h2>Alerts vs. architecture. That's the whole difference.</h2>
<p class="section-sub">Every other tool in this market optimizes the workflow around compliance. DisputeOS enforces compliance at the system level. The distinction matters when a CFPB examiner is reading your dispute logs.</p>
<div class="card highlight">
<h3>What "compliance as architecture" means</h3>
<p>An alert says "you should do this by Thursday." A gate says "you cannot proceed until you do this." When the CFPB examiner asks why 23% of your disputes missed the 10-day window, you can either say "the alerts went to a shared inbox" or you can say "our system made it structurally impossible to miss." One of those answers costs $175 million. The other doesn't.</p>
</div>
<table>
<thead>
<tr>
<th>Capability</th>
<th>Email alerts (Fiserv, FIS, FINBOA)</th>
<th>Workflow automation (Quavo)</th>
<th>DisputeOS</th>
</tr>
</thead>
<tbody>
<tr>
<td>Deadline tracking</td>
<td>Email notifications, manual follow-up</td>
<td>Dashboard with status indicators</td>
<td>Real-time countdown with architectural gate enforcement</td>
</tr>
<tr>
<td>Missed deadline behavior</td>
<td>Alert gets lost in inbox</td>
<td>Shows "overdue" status in dashboard</td>
<td>System blocks state transition until action is taken</td>
</tr>
<tr>
<td>Provisional credit at Day 10</td>
<td>Manual process, human-dependent</td>
<td>Workflow step, can be skipped</td>
<td>Gate enforced: cannot advance past Day 10 without credit or completed investigation</td>
</tr>
<tr>
<td>Audit trail</td>
<td>Fragmented across email, spreadsheets, core banking</td>
<td>Centralized but workflow-level (not gate-level)</td>
<td>Every gate passage, escalation, and override logged with actor + timestamp + rationale</td>
</tr>
<tr>
<td>CFPB examination readiness</td>
<td>Requires manual report assembly</td>
<td>Pre-built reports, backward-looking</td>
<td>Real-time compliance exposure dashboard + per-dispute audit trail</td>
</tr>
<tr>
<td>Business day calculation</td>
<td>Federal Reserve calendar only</td>
<td>Configurable calendars</td>
<td>Institution-specific holiday calendar with automatic clock adjustment</td>
</tr>
<tr>
<td>Multiple concurrent clocks per dispute</td>
<td>Single deadline tracking</td>
<td>Limited</td>
<td>Full concurrent clock orchestration (investigation + provisional credit + determination + notification)</td>
</tr>
</tbody>
</table>
</div>
<!-- DESIGN PARTNER OFFER -->
<div class="section">
<div class="offer-box">
<h2>Design partner program</h2>
<p>We are onboarding five banks or fintechs as design partners. You get the full DisputeOS platform for 30 days while we calibrate the compliance clock engine against your institution's dispute workflow. In exchange, we co-author a case study and you introduce us to two peer institutions when the pilot completes.</p>
<div class="offer-list">
<div class="offer-item">
<div class="n">30 days</div>
<div class="l">Pilot</div>
</div>
<div class="offer-item">
<div class="n">5 slots</div>
<div class="l">Design partners</div>
</div>
<div class="offer-item">
<div class="n">Zero</div>
<div class="l">Core banking changes required</div>
</div>
</div>
<a class="btn btn-primary" href="https://calendly.com/mightybot-john/disputeos-design-partner-discovery?utm_source=mightybot&utm_medium=landing&utm_campaign=disputeos&utm_content=offer-box-cta" rel="noopener" target="_blank">Request a slot</a>
</div>
</div>
<!-- FAQ -->
<div class="section">
<h2>Frequently asked questions</h2>
<div class="faq-item">
<h3>What is DisputeOS in one sentence?</h3>
<p>DisputeOS is a compliance clock engine that converts Reg E deadlines into architectural gates so banks and fintechs cannot miss a dispute investigation deadline without an explicit, auditable human override. It replaces the email-alert model with structural enforcement.</p>
</div>
<div class="faq-item">
<h3>Does DisputeOS integrate with our core banking system?</h3>
<p>For the design partner program, no core banking integration is required. DisputeOS accepts dispute data via CSV upload or REST API. Your team continues to use their existing core banking system (FIS, Fiserv, Jack Henry) for transaction processing. Provisional credit posting remains a manual action in your core for the pilot. V1 builds API adapters for the Big Three core banking platforms so provisional credits can auto-post from a DisputeOS gate trigger.</p>
</div>
<div class="faq-item">
<h3>How is DisputeOS different from FINBOA?</h3>
<p>FINBOA is a workflow automation tool. It sends compliance alerts and routes disputes through configurable workflows. If a human misses an alert, the deadline passes and FINBOA logs it as overdue. DisputeOS is architecturally different: when a deadline arrives without the required action, the system BLOCKS the dispute from advancing. The failure mode in FINBOA is a missed email. The failure mode in DisputeOS is a blocked gate that requires an explicit human override with an audit trail.</p>
</div>
<div class="faq-item">
<h3>How is DisputeOS different from Quavo?</h3>
<p>Quavo is the market leader in dispute workflow automation, with $300M in funding and 12.5M disputes per year. Quavo optimizes the dispute investigation workflow and recently launched ARIA, an AI investigation agent. DisputeOS is focused on a different layer: compliance enforcement, not investigation automation. Quavo makes your investigators faster. DisputeOS makes sure your institution never misses a deadline regardless of how fast your investigators are. In a mature deployment, Quavo and DisputeOS could coexist: Quavo handles the investigation workflow, DisputeOS enforces the compliance clocks.</p>
</div>
<div class="faq-item">
<h3>What about Fiserv or FIS? We already have dispute management.</h3>
<p>Fiserv has two dispute products and neither enforces compliance at the architectural level. Nautilus Efficiency Manager handles Reg E disputes (debit, ATM, ACH) with email-based deadline alerts. Dispute Expert handles credit card chargebacks (Reg Z) with Ethoca integration and network timers. FIS CBK uses RPA for chargeback processing. All three are workflow and process tools. None of them block a state transition when a deadline is missed. They track compliance; they don't enforce it. Cash App had tracking tools. US Bank had tracking tools. The CFPB doesn't ask "did you track the deadline?" It asks "did you meet the deadline?"</p>
</div>
<div class="faq-item">
<h3>Is MightyBot SOC 2 certified?</h3>
<p>Yes. MightyBot is SOC 2 Type II certified by an independent audit firm against the AICPA Trust Services Criteria for Security, Confidentiality, and Availability. The certification applies to the full MightyBot agent platform, including DisputeOS. A copy of the latest SOC 2 report is available to qualified prospects under NDA.</p>
</div>
<div class="faq-item">
<h3>What data do you need from us to get started?</h3>
<p>Your institution's holiday calendar (which days you close for business) and a sample of open dispute records with intake dates, dispute types, and current status. Most compliance teams can export this from their existing system in an afternoon. We handle normalization. No PII is required for the pilot setup phase; we work with synthetic data until you are comfortable with the platform.</p>
</div>
<div class="faq-item">
<h3>How does DisputeOS handle multiple concurrent clocks on the same dispute?</h3>
<p>A single consumer dispute can run four or more independent clocks simultaneously: the investigation deadline, the provisional credit deadline, the determination notification deadline, and the provisional credit reversal notice deadline. Each clock has its own gate. DisputeOS tracks all of them independently, computes deadlines to the business day using your institution's calendar, and enforces each gate separately. This is the concurrent clock orchestration problem that spreadsheets and email alerts fundamentally cannot solve.</p>
</div>
<div class="faq-item">
<h3>Who built DisputeOS?</h3>
<p>DisputeOS is built on the <a href="https://www.mightybot.ai">MightyBot</a> agent platform. MightyBot does not use drag-and-drop workflow builders. You describe the policy in plain English, upload the source data, and the platform compiles a deterministic execution plan. The compliance clock engine maps directly to MightyBot's policy resolver: each Reg E deadline is a policy with a condition, a priority, and a gate enforcement rule. The platform handles the clock computation, the gate logic, and the audit trail automatically.</p>
</div>
<div class="faq-item">
<h3>What happens after the 30 day pilot?</h3>
<p>If DisputeOS reduced your compliance exposure and your team trusts the gate model, we talk about a paid plan. If not, we shake hands and part ways. No auto-renewal, no lock-in, no surprise bill. We are confident the gate model speaks for itself once you see it running on your real dispute data.</p>
</div>
</div>
<!-- FINAL CTA -->
<div class="section">
<div class="offer-box">
<h2>2026 is the year of the audit.</h2>
<p>Five design partner slots. First come, first served. If your institution processes electronic fund transfer disputes, the CFPB examination cycle is tightening and the penalties are getting larger. Let's make sure your compliance posture is structural, not aspiration
al.</p>
<a class="btn btn-primary" href="https://calendly.com/mightybot-john/disputeos-design-partner-discovery?utm_source=mightybot&utm_medium=landing&utm_campaign=disputeos&utm_content=final-cta" rel="noopener" target="_blank">Become a design partner</a>
</div>
</div>
<!-- SECURITY / SOC 2 -->
<div class="section">
<h2>Built for regulated institutions</h2>
<p class="section-sub">Dispute data is sensitive consumer financial information. DisputeOS runs on infrastructure built for institutions that answer to regulators.</p>
<div class="trust-card">
<div class="trust-copy">
<div class="eyebrow">Security and Compliance</div>
<h3>SOC 2 Type II Certified</h3>
<p>MightyBot is SOC 2 Type II certified, following a successful audit by an independent firm. The certification confirms MightyBot meets the rigorous standards of Security, Confidentiality, and Availability required to process sensitive consumer dispute data, investigation records, and compliance audit trails. Every data access is logged; every agent action is auditable end to end.</p>
</div>
<img alt="AICPA SOC 2 Type II certification badge" loading="lazy" src="https://cdn.prod.website-files.com/673ad7ebdf90a87e7aa3e9a8/682d8e7601846b89fdfdc740_aicpa-soc2.png"/>
</div>
</div>
<div class="footer">
<p>DisputeOS is a product of <a href="https://www.mightybot.ai">MightyBot</a>. Learn more about the MightyBot agent platform and its approach to policy-driven agents for regulated industries.</p>
<div class="footer-links">
<a href="https://www.mightybot.ai">MightyBot home</a> ·
<a href="https://www.mightybot.ai/blog">Blog</a> ·
<a href="mailto:partners@mightybot.ai">Contact</a>
</div>
</div>
</div>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Service",
"name": "DisputeOS",
"alternateName": "DisputeOS Compliance Clock Engine",
"serviceType": "Reg E compliance enforcement engine for banks and fintechs",
"description": "Compliance clock engine that converts Reg E deadlines into architectural gates, making it structurally impossible for financial institutions to miss dispute investigation deadlines without an explicit auditable override.",
"url": "https://www.mightybot.ai/agents/disputeos",
"provider": {
"@type": "Organization",
"name": "MightyBot",
"url": "https://www.mightybot.ai",
"logo": "https://cdn.prod.website-files.com/673ad7ebdf90a87e7aa3e9a8/673ad7ebdf90a87e7aa3ea36_Layer_1%20(4).png",
"description": "Policy-driven AI agents that automate complex financial workflows with 99%+ accuracy. Built for regulated industries. SOC 2 Type II certified.",
"hasCredential": {
"@type": "EducationalOccupationalCredential",
"credentialCategory": "certification",
"name": "SOC 2 Type II",
"recognizedBy": {"@type": "Organization", "name": "AICPA"}
}
},
"audience": {
"@type": "BusinessAudience",
"audienceType": "US banks, credit unions, and fintechs processing electronic fund transfer disputes"
},
"offers": {
"@type": "Offer",
"name": "30-day design partner pilot",
"price": "0",
"priceCurrency": "USD",
"description": "30-day design partner pilot for qualifying financial institutions. No core banking integration required for pilot."
}
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is DisputeOS in one sentence?",
"acceptedAnswer": {"@type": "Answer", "text": "DisputeOS is a compliance clock engine that converts Reg E deadlines into architectural gates so banks and fintechs cannot miss a dispute investigation deadline without an explicit, auditable human override."}
},
{
"@type": "Question",
"name": "Does DisputeOS integrate with core banking systems?",
"acceptedAnswer": {"@type": "Answer", "text": "For the design partner program, no core banking integration is required. DisputeOS accepts dispute data via CSV upload or REST API. V1 builds API adapters for FIS, Fiserv, and Jack Henry core banking platforms."}
},
{
"@type": "Question",
"name": "How is DisputeOS different from FINBOA?",
"acceptedAnswer": {"@type": "Answer", "text": "FINBOA is a workflow automation tool that sends compliance alerts. If a human misses an alert, the deadline passes. DisputeOS is architecturally different: when a deadline arrives without the required action, the system blocks the dispute from advancing. The failure mode in FINBOA is a missed email. The failure mode in DisputeOS is a blocked gate that requires an explicit human override with audit trail."}
},
{
"@type": "Question",
"name": "How is DisputeOS different from Quavo?",
"acceptedAnswer": {"@type": "Answer", "text": "Quavo optimizes the dispute investigation workflow with $300M in funding and 12.5M disputes per year. DisputeOS is focused on compliance enforcement, not investigation automation. Quavo makes investigators faster. DisputeOS makes sure the institution never misses a deadline regardless of investigator speed. In a mature deployment, both could coexist."}
},
{
"@type": "Question",
"name": "What about Fiserv Nautilus or FIS CBK?",
"acceptedAnswer": {"@type": "Answer", "text": "Fiserv Nautilus and FIS CBK provide email-based deadline alerts and basic dispute workflow routing as core banking modules. They are process tools, not compliance enforcement engines. Cash App had alerts. US Bank had alerts. DisputeOS makes it structurally impossible to miss a deadline."}
},
{
"@type": "Question",
"name": "Is MightyBot SOC 2 certified?",
"acceptedAnswer": {"@type": "Answer", "text": "Yes. MightyBot is SOC 2 Type II certified by an independent audit firm against the AICPA Trust Services Criteria for Security, Confidentiality, and Availability. The certification applies to the full MightyBot agent platform including DisputeOS."}
},
{
"@type": "Question",
"name": "What data do you need to get started?",
"acceptedAnswer": {"@type": "Answer", "text": "Your institution's holiday calendar and a sample of open dispute records with intake dates, dispute types, and current status. No PII is required for pilot setup. We work with synthetic data until you are comfortable with the platform."}
},
{
"@type": "Question",
"name": "How does DisputeOS handle multiple concurrent clocks?",
"acceptedAnswer": {"@type": "Answer", "text": "A single dispute can run four or more independent clocks simultaneously. DisputeOS tracks all of them independently, computes deadlines to the business day using your institution's calendar, and enforces each gate separately. This is the concurrent clock orchestration problem that spreadsheets and email alerts cannot solve."}
},
{
"@type": "Question",
"name": "Who built DisputeOS?",
"acceptedAnswer": {"@type": "Answer", "text": "DisputeOS is built on the MightyBot agent platform. The compliance clock engine maps to MightyBot's policy resolver: each Reg E deadline is a policy with a condition, a priority, and a gate enforcement rule."}
},
{
"@type": "Question",
"name": "What happens after the 30 day pilot?",
"acceptedAnswer": {"@type": "Answer", "text": "If DisputeOS reduced your compliance exposure and your team trusts the gate model, we discuss a paid plan. If not, we part ways. No auto-renewal, no lock-in, no surprise bill."}
}
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "MightyBot", "item": "https://www.mightybot.ai"},
{"@type": "ListItem", "position": 2, "name": "Agents", "item": "https://www.mightybot.ai/agents"},
{"@type": "ListItem", "position": 3, "name": "DisputeOS"}
]
}
</script></div>