Decentralised News · Agentic Finance · Decision research
By Heath Muchena · Source review 2026-11-14 · Instrument version 1.0.1
What Matters
A protection label is useful only when its entity, account, asset and loss trigger match. A broker-failure scheme, a payment dispute and a platform warranty do not promise the same remedy for an agent mistake.
“My account is protected” is an incomplete operating assumption. Before an agent can trade or move money, name the event the protection is supposed to address. A security falls in price. A broker fails with customer property missing. A bank fails. A third party initiates a transfer. Those descriptions lead to different documents and different claim processes.
This guide uses a US consumer and retail-investor scope, with official SIPC, FDIC and CFPB material plus narrowly identified provider examples. It does not apply US rules to South African accounts, classify every crypto asset, or decide whether a particular loss is recoverable. The relevant entity and product still need checking even when the customer lives in the United States.
DN’s AI Agent Insurance guide addresses policy and broker questions. This article adds a loss-trigger record: what happened, where the asset was held, which arrangement is being invoked, and what evidence remains missing. It combines payment recourse and agent-loss scenarios without assuming either universal protection or universal exclusion.
DN Evidence Block
Sources reviewed: 2026-11-14 · Evidence type: Primary US scheme and regulator guidance, plus named public provider disclosures; original evidence-routing tool and synthetic scenarios.
Scope: US retail securities custody, insured-bank deposits, consumer electronic transfers and credit-card billing disputes. Coinbase examples are limited to the cited product and US warranty provisions. An OKX explanation illustrates a liquidation-fund mechanism without establishing US product availability.
- Official SIPC, FDIC and CFPB materials distinguish the loss triggers addressed by their respective arrangements.
- Coinbase One US warranty clause8 expressly excludes transfer requests authenticated by API key; the other eligibility conditions remain relevant.
- Ten primary sources were consulted on 13 November 2026. No individual account, policy schedule, enrollment or claim was inspected.
Not established by this work: Coverage eligibility, claims outcomes, balances, pass-through insurance records, contract enforceability, legal classification of a specific agent action, or any South African equivalent.
Original DN instrument · version 1.0.1
DN US Loss-Protection Scope Record
Match a reported loss event to the next document-review question. This evidence router does not decide legal coverage, liability or reimbursement.
Enter your assumptions or load a labelled example. Required blank numbers stay missing; unknown evidence remains unknown. Use nonpersonal labels only. This instrument makes no network requests and uses no persistent browser storage.
Use your own inputs
No current result. Complete inputs or load an illustrative example.
Educational US evidence routing only. No coverage determination, legal advice, scheme-limit calculation, deadline calculation, provider endorsement or claim submission. User-entered labels are not verified; rights may overlap and depend on facts and documents outside this record.
1. SIPC: separate missing customer property from investment performance
SIPC explains that its protection concerns eligible customer cash and securities at a financially troubled member broker. Its limit is $500,000 per customer, including up to $250,000 for cash within the scheme’s scope. A decline in security value or bad investment advice is not the loss it reimburses. SIPC’s own explanation should be the starting point, rather than a platform badge.
For an agent, distinguish the order decision from the custody event. “The model selected a security that fell” and “the broker failed with securities missing” are different allegations. Save the statement, the actual carrying entity and the asset description before invoking a limit. Do not count each application login as a separate protection allowance.
The SEC’s SIPC bulletin also identifies important product boundaries, including most crypto assets and unregistered investment contracts. Do not convert that into a blanket finding about every tokenized instrument. The legal instrument and custody arrangement matter. This article’s tool therefore routes a case for review and never labels a named token covered.
2. FDIC: identify the bank, deposit and failure event
FDIC guidance describes a standard $250,000 limit per depositor, per insured bank, per ownership category. The relevant event is failure of an insured bank, and eligible deposit products are distinct from investments. The FDIC deposit-insurance FAQ explains the categories and points readers to its own estimation tools.
A nonbank application introduces another question. The FDIC’s third-party-app guidance says the nonbank itself is not FDIC-insured. Pass-through protection depends on funds reaching an insured bank and the applicable ownership and recordkeeping conditions. Nonbank insolvency is not transformed into insured-bank failure merely because the app names a partner bank.
Record where cash is actually held and what would have to fail. If the agent can sweep cash between a brokerage, a bank product and a crypto balance, preserve the state at the event time. A logo captured before a transfer does not answer where the asset was held afterward. The local record deliberately does not add several platform balances into a supposed insured total.
3. Electronic-transfer rights: investigate authority and the transaction facts
The CFPB’s Regulation E compliance aid distinguishes qualifying consumer electronic transfers and explains unauthorized-transfer rules. Actual authority, the consumer’s benefit and how access was obtained matter. It also explains why fraudulently induced credential disclosure is not simply treated as voluntary furnishing of an access device that removes the protection.
That is a reason to preserve facts, not to invent a rule that all agent transactions are authorized or that every prompt-injection incident is unauthorized. Save the instruction, approval scope, access method, requested amount, executed amount and notice history. Do not edit a case description to fit the word “fraud” if the evidence shows a different event.
A personal consumer account and a business treasury account are not interchangeable for this analysis. Nor should every blockchain transfer be assumed to fall within the same consumer-account definition. For an actual suspected error, notify the relevant institution promptly and obtain the applicable process. The tool helps assemble the questions; a qualified adviser or the responsible institution must assess the legal facts.
4. Card disputes: identify the charge being challenged
A card charge can have a billing-error process without turning a later trading result into a refundable purchase. The CFPB’s credit-card dispute guidance tells consumers to contact the issuer promptly and preserve their rights with a written billing-error notice within 60 calendar days after the charge appeared on the statement. It distinguishes the process for some defective goods or services.
Before using “chargeback” in an agent design, identify the transaction in dispute. Is it an unauthorized card charge, a duplicate bill, an undelivered service, or a correctly delivered service that produced an unwelcome investment outcome? These are different factual claims. Do not assume that funding an account creates a guarantee on everything later bought or sold there.
The useful operational artifact is a notice record: statement date, disputed charge, reason, issuer instructions, submission evidence and response. This guide does not determine network chargeback eligibility, calculate a deadline from an incomplete record, or suggest reversing a legitimate payment to recover unrelated market losses.
5. Insurance funds and custody insurance: ask whose loss is addressed
The phrase “insurance fund” can describe a trading-system backstop. OKX’s published explanation distinguishes an eligible shortfall beyond liquidation collateral from a refund of the liquidated trader’s lost margin. The page is educational and explicitly warns that product availability varies by region; it is not evidence that a US reader can trade a particular derivative or claim from its fund.
Custody crime insurance is another arrangement. Coinbase’s insurance overview says its crime policy protects a portion of digital assets across storage systems against specified theft losses, while excluding personal-account access losses caused by compromised credentials. It also says losses can exceed recoveries. That is a description of the published policy summary, not a review of the policy schedule or a promise to an individual user.
Ask four questions before a protection label enters a product comparison: Who is insured or entitled to claim? Which property is in scope? Which event triggers the response? Which limits and exclusions apply? A headline fund balance, a custody policy and a user reimbursement promise should occupy separate rows in the evidence register.
6. Platform warranties: check whether the agent’s access method is excluded
A current, concrete example is Coinbase One’s US account-protection warranty. Clause 8 excludes outbound transfer requests authenticated by API key. Clause 7 excludes transfers the user authorizes by mistake. The disclosure also limits scope to qualifying Coinbase-hosted outbound transfers and excludes named products such as Coinbase Prime and Coinbase Wallet. Membership, enrollment, region and other conditions still apply.
This creates a specific design question: if an agent is connected through an API, is the team relying on a promise whose text excludes that authentication path? The answer must come from the applicable warranty and the actual request method, not from the fact that the brand advertises account protection elsewhere.
Record the clause number and dated wording before enabling access. The cited US warranty describes itself as a limited warranty rather than insurance. Do not extend its exclusion to every possible statutory right or claim against every party. Conversely, do not relabel it as general protection against hallucinated orders, wrong addresses, private-key loss or trading losses.
7. Complaint routes: preserve recourse without mistaking a process for an award
The CFPB complaint process routes complaints to companies, obtains responses and allows consumer feedback. That process is useful evidence of an escalation route. It is not itself a policy or a determination that reimbursement is due. A regulated status, helpdesk or complaint form should therefore be recorded separately from a financial promise.
Use the following original scenario discipline. For a price decline after an authorized trade, start with the investment decision and any specific misconduct allegation. For assets missing in broker failure, investigate the custody and scheme conditions. For a disputed transfer, preserve authority, authentication and notice facts. For a platform warranty, examine the exact trigger and exclusions. One incident may require several records because several legal relationships are involved.
The DN tool returns a next-review route and unresolved evidence fields. Even a record with no unknown fields is only a complete set of user assertions. It is not a coverage opinion. That keeps the useful work concrete: find the right document, preserve the event evidence and send a well-scoped question to the institution or adviser who can assess it.
Methodology, limitations and corrections
DN compared the trigger and scope described by the cited primary materials, then designed a conservative local routing instrument. It uses no statistical model or probability of recovery. The next-review labels are editorial workflow instructions. A published trigger mismatch identifies a difference between the selected event and the arrangement described here; it does not deny every claim a person might have under another law, contract or set of facts.
The unknown-field count covers jurisdiction, entity, product, notice and event. A known mismatch is reported separately rather than hidden inside that count. The output always states that coverage is not determined. Synthetic examples test the distinction between a market decline and broker failure, between nonbank and bank failure, and between a contractual question and a statutory payment claim.
Source checks were performed on 13 November 2026. FDIC guidance was available through its official indexed publications; direct page rendering was restricted during the check. No signed policy, private account eligibility screen, regulator determination or claim file was reviewed. For an actual incident, obtain the applicable current documents and qualified advice while promptly preserving notice rights. No South African equivalence is asserted.
Instrument version 1.0.1 preserves an unknown FDIC loss event as an unresolved review question. It does not label that missing fact a known trigger mismatch. This pre-publication correction was checked on 13 November 2026.
For corrections, identify the claim, source and date when contacting Decentralised News. A new record-creation timestamp does not refresh its underlying evidence.
Change log: version 1.0.1, 2026-11-14. Initial documentation review, original instrument and labelled examples.
Frequently asked questions
Does SIPC reimburse an AI-selected trade that loses money?
SIPC’s published scope excludes ordinary market losses. If the facts also involve missing assets, broker failure or another allegation, preserve those separately and obtain a case-specific assessment. Calling the trade automated does not itself identify a remedy.
Does a partner-bank logo insure money against an agent mistake?
It does not establish that result. Identify the bank, deposit ownership, actual location of the money and event. Deposit insurance and rights concerning disputed payments are different questions; a nonbank interface can sit above several products.
Are all losses involving shared credentials excluded from consumer protection?
No blanket rule is justified. The CFPB distinguishes actual authority and fraudulently obtained access, among other facts. Do not equate every disclosure with loss of statutory rights or every software error with an unauthorized transfer.
Can an exchange account-protection benefit cover an API transfer?
Read the specific benefit. The reviewed Coinbase One US warranty has an express API-authenticated-transfer exclusion. That observation is limited to the named warranty and does not decide rights under another arrangement or a different product.
Can a complete tool record be used as a coverage certificate?
No. It shows the entered scope and directs the next review. Even zero unknown fields means only that the user supplied classifications. The institution, insurer, scheme or qualified adviser still needs the actual facts and applicable documents.
Does this guide establish equivalent protection for South African accounts?
No. This article deliberately uses a US scope. A South African account needs its own legal entity, product, statutory regime, policy and complaint-route review. A familiar international brand does not make the US scheme portable.
Primary sources
- SIPC: What SIPC Protects. Eligible missing customer cash and securities, stated limits, and market-loss/bad-advice boundaries. Reviewed 2026-11-13.
- SEC Investor Bulletin: SIPC Basics. Product and custody boundaries, including crypto-related caveats; no individual instrument classification. Reviewed 2026-11-13.
- FDIC: Deposit Insurance FAQs. Bank-failure trigger, deposit-product scope and per-depositor/bank/ownership-category limit; official indexed text reviewed. Reviewed 2026-11-13.
- FDIC: Banking With Third-Party Apps. Nonbank distinction and conditional pass-through deposit-insurance requirements; official indexed text reviewed. Reviewed 2026-11-13.
- CFPB: Electronic Fund Transfers FAQs. Consumer-account/EFT scope, authority and fraud distinctions, and error-resolution context. Reviewed 2026-11-13.
- CFPB: How do I dispute a charge on my credit card bill?. Prompt notice and written billing-error process; not a rule guaranteeing refund of investment losses. Reviewed 2026-11-13.
- Coinbase insurance overview. Published crime-insurance scope and personal-account credential exclusion; not the complete insurance policy. Reviewed 2026-11-13.
- Coinbase One account protection disclosures — United States. Limited-warranty product/region/enrollment conditions and US clauses7–8 on mistaken and API-authenticated transfers. Reviewed 2026-11-13.
- OKX: What is an insurance fund?. Educational distinction between liquidation shortfall backstop and refund of lost margin; no US product availability inference. Reviewed 2026-11-13.
- CFPB: Learn how the complaint process works. Complaint routing, company response and consumer feedback, rather than an insurance benefit. Reviewed 2026-11-13.
Turn the finding into a decision
Before paying for a protection add-on or selecting a trading venue because of an insurance label, complete one record for the exact account and loss event. Request the applicable policy, warranty or scheme evidence and ask the provider to identify the claim route. DN’s related guides can help frame that request. No platform or insurance purchase is recommended by this comparison.
Related DN research
Disclosure: Analysis and instrument results are editorial. Where labelled affiliate links appear, DN may receive compensation when you sign up or buy through them. Commercial relationships do not determine findings. No tested integration or guaranteed outcome is implied.
