Monitoring Tells You It Happened. Documentation Helps You Act.
Search for an identity theft app and nearly everything you find is monitoring: dark-web scans, new-account alerts, score trackers, one-tap freezes. Those tools have a real job — they detect. But detection is where the job ends. The moment an alert fires about a loan you never opened, a monitoring app has done everything it will ever do for you.
What comes next is not a monitoring problem; it is a documentation problem, governed by the Fair Credit Reporting Act. Identity theft victims have two main written paths: FCRA Section 605B, which requires a bureau to block information resulting from identity theft within 4 business days of receiving a complete request, and FCRA Section 611, which requires reinvestigation of a disputed item's accuracy within 30 days (45 in some cases). Both paths run on paper — specific elements, specific attachments, specific addresses — and no dashboard alert produces any of it.
605b.ai sits on that second half of the timeline. It is not monitoring and does not pretend to be. It is documentation software for the aftermath: the part where you have to prove who you are, identify exactly what is fraudulent, and put the right letters in the mail.
What the App Does, Step by Step
The workflow is deliberately boring, because dispute documentation should be boring. Here is the entire loop:
- Upload your credit report. A PDF from AnnualCreditReport.com or downloaded directly from a bureau works. The analysis runs on the report you actually received, not generic assumptions.
- The AI flags items — backed by the report's own text. Every flagged account, inquiry, or address is tied to the lines that appear in your report, so each letter can quote the exact entry instead of vaguely gesturing at negative items.
- You confirm what is actually fraudulent. Software cannot know your transaction history; only you can say which accounts are not yours. Nothing goes into a letter you have not confirmed.
- Pick the correct legal track per item. Identity theft items go the 605B blocking route; ordinary inaccuracies go the 611 reinvestigation route. Conflating the two is one of the most common self-filing mistakes.
- Generate letters that cite the right statute. Each letter states what is disputed, why, and under which FCRA section, with your evidence listed as enclosures.
- You print, sign, and mail. 605b.ai never sends anything for you. Certified mail with return receipt is the standard recommendation, because the delivery date starts the statutory clock.
- Track deadlines with reminders. The 4-business-day block window and the 30/45-day reinvestigation window are tracked from delivery, with reminders when a response is due or overdue.
The 605B Four-Element Packet Builder
Section 605B(a) is unusually precise about what a blocking request must contain. A bureau's 4-business-day obligation is triggered only when it receives all four statutory elements.
Miss one element and the bureau may treat the request as incomplete — the clock never starts. The packet builder in 605b.ai is essentially a strict checklist: it will not mark a packet ready until all four elements are present, and it flags gaps — no identity theft report attached, an item described but not identified by its actual report entry — before you print. One honest caveat belongs here: even a complete packet is a legal request, not a guaranteed result. The statute allows a bureau to decline or later rescind a block in limited circumstances, for example if it reasonably determines the request was made in error or contains a material misrepresentation. Complete documentation removes the procedural reasons to say no; the decision is still the bureau's. The four elements:
- Proof of your identity — typically government-issued ID plus something tying you to your current address, per each bureau's published requirements.
- A copy of an identity theft report — the FTC report from IdentityTheft.gov, a police report, or both.
- Identification of the information resulting from the identity theft — the specific accounts, inquiries, or entries, exactly as they appear on the report.
- A statement that the information does not relate to any transaction of yours.
Beyond the Big Three: Specialty Bureaus
Identity theft rarely confines itself to Equifax, Experian, and TransUnion. A fraudulent checking account surfaces in ChexSystems or Early Warning Services; a utility account opened in your name lands in NCTUE; LexisNexis and Innovis hold files that feed lending, insurance, and tenant-screening decisions. Many victims discover these agencies only at the worst moment — a denied checking account application months after they thought the cleanup was finished.
These are consumer reporting agencies under the FCRA, and identity theft dispute rights largely extend to them. 605b.ai's 60+ letter templates include disputes addressed to the specialty bureaus, so the same case that produced your Equifax packet can produce the ChexSystems one.
iOS, Android, and Web: One Case, Every Screen
605b.ai runs on the web and as an iOS and Android app, with the same case synced across all three. In practice the split is natural: the phone is where you photograph certified-mail receipts and return-receipt cards the moment they come back, and where deadline reminders arrive as notifications; the web app is where you review each letter line by line before printing. Nothing in the workflow requires a particular device — a dispute file built entirely on a phone is just as complete.
Free Analysis, One-Time Purchase, No Subscription
The analysis is free: upload a report and see what the AI flags — and which legal track fits each item — before paying anything. Generating the letters and the 605B packet is a one-time purchase. There is no subscription, and that is a design decision rather than a pricing footnote: much of the credit repair industry bills monthly, and a monthly bill quietly rewards disputes that drag on. Documentation software has the opposite incentive — the goal is a complete file, mailed once, done.
If you are comparing tools, the useful questions are what a tool automates (drafting and tracking versus sending), whether it acts on your disputes itself, and what it costs by the time a case stretches across several months. Those comparisons are covered head-to-head elsewhere on this site.
Who It Is For — and Who It Is Not For
605b.ai fits an identity theft victim who is willing to run their own paperwork: someone who wants every letter drafted, every 605B element checked, every deadline tracked, and every receipt stored in one place — but who signs and mails everything personally.
One more thing belongs in every victim's toolkit: escalation. If a bureau misses a statutory deadline or rejects a properly documented request without explanation, you can file a complaint with the CFPB, which forwards it to the bureau and requires a response. The dispute timeline page covers when and how to escalate.
It is not the right tool if:
- You want a service to act on your behalf. 605b.ai never contacts a bureau, mails a letter, or makes a call for you. Services that dispute on your behalf exist; that is a different category with different trade-offs — including, for paid services, coverage under the Credit Repair Organizations Act.
- You need legal advice. Complex situations — criminal identity theft, a lawsuit, a collection judgment built on fraudulent debt — are attorney territory. Documentation software can organize the record an attorney will want, but it cannot advise you.
- You want monitoring. 605b.ai does not watch your credit or send fraud alerts; pair it with a security freeze and whatever monitoring you already use.
Frequently asked questions
Analyze your report and organize suspicious items for your own dispute workflow.
Analyze Your Credit Report →