Deposits · August 2026
SoFi's homepage blocks agents while its product pages stay open
An AI agent ran five ordinary deposits tasks on the public pages of SoFi and scored what each page delivered.
Run 6 August 2026 · five tasks · public pages, logged out · Fintech
78/100
Mystery Agent score
Deposits · rank 4 of 25
Savings rate
90Served as text
Checking comparison
76Partly served
Fee schedule
88Served as PDF
Routing number
76Partly served
Application page
58Partly served
Summary
- SoFi's deep product and legal pages answer a plain fetch even though its homepage requires a script challenge.
- An agent read the savings APY of up to 3.80% and confirmed it in the linked PDF rate sheet.
- The checking and savings FAQ answers, including fee and routing facts, sit in schema markup that a script-free reader can still find.
- Lifting the marketing copy already in that schema markup into plain HTML would let both pages agree.
SoFi also appears in the Credit Cards study, where it scores 74 and ranks 9 of 25.
See that scorecard.
Task by task
Each task is scored out of 100 on completion, answer quality and how directly the answer was reached. Each note describes what the page delivered, with a link to the page the answer was found on.
Task 01Savings rateServed as text90 out of 100
The banking hub states members can earn up to 3.80% APY with a 0.70% Boost, and a linked PDF rate sheet confirms tiered rates of 0.50% base, 4.50% up to $20,000, and 3.10% above that.
Task 02Checking comparisonPartly served76 out of 100
SoFi sells one combined checking and savings account, and its FAQ schema states no overdraft, minimum balance, or monthly fees for either, though the matching marketing chart renders only through an inline script.
Task 03Fee scheduleServed as PDF88 out of 100
The SoFi Bank Fee Sheet PDF, dated May 18, 2026, lists a $0 monthly maintenance fee, a $0 overdraft fee, a $30 outgoing domestic wire fee, and a 0.75% Instant Transfer fee, all as clean text.
Task 04Routing numberPartly served76 out of 100
The routing number, 031101334, appears in the page's meta description and again in its FAQ schema text, both readable without scripts, while the matching hero heading on the same page renders through an inline script.
Task 05Application pagePartly served58 out of 100
The signup page collects a legal name, email, and password across five fields and states plainly that filling out the application comes next, while SSN, government ID, and funding requirements sit behind a separate Eligibility Criteria link.
The SoFi Bank Fee Sheet lists a $0 monthly maintenance fee and a $0 overdraft fee in plain, dated text.
The application page
What the account opening page states to a reader that runs no scripts.
62,166Bytes delivered
1,913Characters of visible text
5Form fields in the first response
After scripts runWhat an applicant needs
Strengths and opportunities
What is working
- Deep product and legal pages are wide open to a plain GET with a generic user agent, even though the homepage itself sits behind a JavaScript challenge. An agent that starts at /banking,the application path, or the legal PDFs never hits a wall.
- SoFi publishes a genuinely complete, well-organized fee schedule and a detailed rate sheet, both as clean two-and-eight-page PDFs that extract to full readable text on the first try.
- FAQ content across the checking, savings and routing-number pages is marked up as schema.org JSON-LD, which places several key answers, including fee waivers and the routing number, into plain text within the raw HTML where a script-free reader can still find them.
Opportunities
- The homepage returns a JavaScript challenge with only 121 visible characters delivered. Publishing a lightweight server-rendered landing page, even a simple one, would let an agent clear the first hop instead of routing around it through direct product URLs.
- Marketing copy on the checking and savings pages, including the fee callouts and the account comparison chart, is built with React.createElement calls inside inline scripts rather than rendered HTML. The same copy already exists in the page's JSON-LD FAQ blocks, so lifting it into plain markup would make the visible page and the machine-readable page say the same thing on the first read.
- The account-opening application page asks for name, email and password without disclosing that SSN, government ID or a funding source will be needed later. A short summary of what is required to finish opening the account would let an agent judge fit before starting the flow.
- llms.txt returns a 404. A short llms.txt pointing to the rate sheet, fee sheet and routing-number pages, all of which are already open to a plain GET, would turn scattered wins into one authoritative index for agents.
Access
Every page the agent requested was delivered on the first attempt. Publishing an llms.txt file would give agent traffic a documented entry point.
Back to the deposits leaderboard · Read the report · How the study works
