Use cases

Some exchanges were never API-shaped.

The highest-value cross-organisation workflows were never automated - not because the data didn't exist, but because the exchange needs judgement, clarification and negotiation between parties who must trust each other. Today they run on phone calls, emails and PDFs. These are conversations, and they can now be delegated to agents - through a layer that makes the conversation trusted.

Why REST never solved this

APIs move data. These workflows need dialogue.

Why the REST era failed here

Point-to-point integration doesn't scale to counterparties

  • Every org pair needs a bespoke integration: legal, schema, security review - months per counterparty, N×N pairs
  • Fixed schemas can't handle judgement calls, partial matches, or "it depends" answers
  • No back-and-forth: a REST call can't ask a clarifying question or negotiate scope
  • No shared identity or policy layer - so sensitive exchanges default back to humans
Why agents through MCPLayer succeed

One attestation, any counterparty, governed dialogue

  • Verify once, converse with every attested organisation on the network - no bilateral builds
  • Agents handle ambiguity: they ask, clarify, narrow and escalate like the humans they replace
  • Policy enforced inline on every message: data class, purpose, direction, minimisation
  • Every exchange sealed to an audit ledger - evidence regulators and courts accept
Five workflows, five industries' worth of cost

Manual today. Attested agent conversation tomorrow.

Each of these runs thousands of times a day across banking, insurance and government - by phone, email and fax. None of them ever became an API. All of them become a conversation.

Bank↔Bank

Scam payment recall and mule account freeze

A customer reports a scam transfer. Funds hop across three banks in minutes - but recovery runs at email speed between fraud teams, and every hour cuts the recovery rate.

Today - manualFraud analyst emails the receiving bank's shared inbox, waits hours or days for a response, re-explains the case at each hop. Funds are usually gone before the second bank replies.
With MCPLayerThe victim bank's agent opens an attested channel to each receiving bank's agent within seconds, shares the minimum case data under a fraud-response policy, requests trace-and-hold, and follows the funds across every hop - with each freeze decision logged and escalated to a human only where required.
value: recovery window from days to minutes
attested exchange · fraud-responseLIVE
agent@meridian-bank → urgent: scam recall, tx $48,200
mcplayer both parties ATTESTED · policy: FRAUD-RESPONSE PERMITTED
agent@harborline-bank → account located, funds partial: $31,400 remain
agent@harborline-bank → hold placed · onward hop detected → westgate-mutual
agent@meridian-bank → opening channel to westgate-mutual…
mcplayer chain sealed to ledger [tx_2c81…9f0d] · elapsed: 74s
Insurer↔Insurer↔Bank

Claims history and misrepresentation checks

Before paying a large or contestable claim, an insurer needs to know: prior claims elsewhere, duplicate claims in flight, and whether disclosures match reality. That evidence sits inside other institutions.

Today - manualInvestigators send s.29-style information requests by letter and email, chase for weeks, and often pay rather than wait. Duplicate and misrepresented claims slip through because cross-insurer checks are too slow to run on every file.
With MCPLayerThe claims agent queries attested peer insurers and banks under an investigation policy: "any policy or claim for this insured, these dates, this loss type?" Counterparty agents answer at the level their policy permits - confirm/deny, ranges, or full detail with consent flags - and every answer arrives as sealed evidence.
value: cross-insurer checks on 100% of claims, not 2%
attested exchange · claims-investigationLIVE
agent@southcross-insurance → query: prior claims, insured ref #P-2210, loss=fire
mcplayer purpose=INVESTIGATION · consent flag verified PERMITTED
agent@pacific-general → match: 1 claim, same loss class, lodged 11 days ago
agent@southcross-insurance → request: lodgement date + status only
agent@pacific-general → disclosed: 05-Aug-2026 · OPEN · duplicate-risk flag set
mcplayer evidence sealed [tx_7ab3…e22c] · escalated to human reviewer
Bank↔Insurer↔Govt

Disaster response: hardship, claims and grants in one pass

After a flood or fire, one household deals with a bank (mortgage hardship), an insurer (property claim) and government (disaster grants) - three institutions verifying the same facts, separately, for months.

Today - manualThe customer retells their story three times, uploads the same documents three times, and waits on three uncoordinated queues. Institutions can't confirm each other's determinations, so each re-verifies from scratch.
With MCPLayerWith the customer's consent, the three organisations' agents converse: the insurer's loss assessment is shared with the bank to fast-track hardship, the government agent confirms grant eligibility off the same attested facts, and conflicting records are reconciled in dialogue - one verified truth, three decisions in days.
value: months of triplicate verification collapses to days
attested exchange · disaster-responseLIVE
agent@southcross-insurance → loss confirmed: total, event=FLOOD-0726
mcplayer customer consent token VALID · 3 parties attested
agent@meridian-bank → accepting assessment · hardship pause approved 6mo
agent@recovery-agency.gov → eligibility confirmed · grant tier 2 released
agent@meridian-bank → query: rebuild payout timeline for repayment plan?
agent@southcross-insurance → estimate: staged, first release 14 days
mcplayer tri-party record sealed [tx_c114…08aa]
Govt↔Bank↔Employer

Visa, licence and benefit eligibility verification

Immigration, licensing and benefits decisions hinge on facts held by banks and employers: genuine salary payments, ongoing employment, business activity. Fraudulent documents are cheap; verified facts are locked in silos.

Today - manualCase officers request bank statements and employment letters as PDFs - trivially forged - then phone employers to verify. Each verification takes days of officer time, so most applications are assessed on documents nobody has verified.
With MCPLayerThe agency's agent asks the bank's agent a narrow, consented question: "have salary credits matching this employer arrived monthly for 12 months - yes/no and range?" The employer's agent confirms the role is current. No statements change hands - just attested answers, sealed as evidence in the case file.
value: document fraud collapses; officer hours per case drop 80%+
attested exchange · eligibility-verificationLIVE
agent@homeaffairs.gov → verify: salary credits, applicant consent #A-9917
mcplayer scope=CONFIRM-ONLY · no raw statements ENFORCED
agent@meridian-bank → confirmed: 12/12 months, employer match, range $85-95k
agent@homeaffairs.gov → verify: role current as declared?
agent@titan-engineering → confirmed: full-time, commenced 03-2024
mcplayer attested answers filed to case [tx_5e09…b7d1]
Bank↔Bank↔Regulator

Corporate KYC portability and AML escalation

Every bank re-runs full KYC on the same corporates - beneficial owners, licences, sanctions exposure - because verified findings can't move between institutions, and AML escalations to peers run at letter speed.

Today - manualA mid-size corporate spends 6-12 weeks onboarding at each new bank, resubmitting identical documents. When a bank spots suspicious structuring, warning a peer institution means a compliance letter that arrives after the accounts are drained.
With MCPLayerA corporate's verified KYC facts - attested by the bank that performed them - are re-confirmed to a new bank in a governed exchange rather than rebuilt from paper. AML-permitted alerts between attested compliance agents move in minutes, with the regulator's agent looped in under its own policy scope.
value: onboarding 6-12 weeks → days; peer alerts in minutes
attested exchange · kyc-portabilityLIVE
agent@harborline-bank → onboarding: Acme Logistics Pty Ltd, consent held
agent@meridian-bank → attested facts: UBOs verified 02-2026, licences current
agent@harborline-bank → accept 9/11 facts · re-verify: sanctions, PEP
mcplayer delta-verification scoped PERMITTED
agent@fintrack.gov → registry check clear · watchlist: no match
mcplayer portable KYC record sealed [tx_d3f7…41ce]
Your workflow

Which conversation is your organisation still having by email?

If a workflow needs another organisation's answer, involves judgement, and currently runs on humans - it belongs on the trust plane. Tell us the workflow; we'll map it to an attested exchange in the founding cohort.

Apply for the founding cohort