A creator-economy founder who spoke only French came to us wanting new tools built directly into a platform his creators already used, a platform that offered no API at all. We found a way in through the browser's own requests, and delivered a full build: the extension, the web app and the sync behind it. He later sold the business at a good profit.
Background
The founder messaged one day, in French. None of us on the project spoke French, so every call ran through a translator. We typed in English, he read the French version appear beside it, then typed his reply and sent it back the other way. Even the shortest of those calls ran close to an hour.
He had found real gaps in the tools OnlyFans gives its creators, and he wanted a Chrome extension that filled them from inside the platform's own pages, closely enough that it felt like part of the product. That meant a panel next to every conversation showing what a fan had spent, with notes and tags, plus saved scripts, an emoji bar and reminders. The plan was to get it right for one creator first, then grow it into a tool for agencies managing many creators at once.
The problem: no API
The product was hard in two ways. Everything we built sat on top of someone else's interface, so any change the platform made on its side was ours to absorb. And the platform had no API, official or otherwise. This was before coding agents, back when ChatGPT could barely hold a single file in its head. A search turned up one four-year-old open-source project that had reverse-engineered the platform's API in the past. It no longer worked.
What we built
The old project's source code gave us a starting point. Watching the network requests the platform's own site made in the browser showed that a signed-in user's session token could reach endpoints the platform never exposed on purpose. So rather than work out how the platform signed its own requests, we let the platform do the signing itself. The extension waits for the page's own request for the signed-in user, copies its headers, and sends that same request again. For anything heavier, the server opens the creator's own session in a headless browser and reads the data as the platform's own page loads it.
How it works
Replaying the page's own request
The extension watches one specific network request the page already makes for its signed-in user and keeps a copy of its headers. Once that request completes, it sends the same request again with those headers attached. The headers are never inspected or parsed, just carried along untouched, so whatever signing method the platform uses keeps working without anyone having to reverse-engineer it by hand.
A headless browser that mimics the creator
For data that simple request-replay could not reach, the server opens a real, signed-in session for that creator in a headless browser, sets the right cookies and browser identity, and waits for the platform's own page to fetch the data it needs. When the extension needs to write something back, such as saving a note, the same headless session intercepts and edits the platform's own outgoing request so the platform signs it exactly as if the creator had clicked it themselves.
Living inside someone else's pages
Since the platform is a single-page app, the extension has to notice route changes on its own and wait for the right element to appear before mounting its panels next to it. Getting the sizing to match the host page, rather than clash with it, took its own round of fixes.
Moving the sync to its own server
The first version opened a headless browser for every fan visible on screen at once, which took minutes to load for a creator with a large following. We moved the sync to run on its own server instead, so the extension could read data that was already stored rather than fetching it live. When several new creators signed up at the same time, opening a browser session for each one at once started crashing the server, so we added a queue that works through new creators three at a time and refreshes every creator's data every six hours.
The result
The extension went live on the Chrome Web Store, the web app started taking payments through Stripe, and the founder wrote back that everything was working.
Everything seems to be working perfectly
Jocelyn, founder of a creator-economy SaaS
A founder who could not share a language with his development team ended up with a working product on a platform that gave him no official way in. He later sold the business at a good profit.
The project was complex due to the lack of public APIs, but he first explored alternative solutions before creating custom APIs
Jocelyn, founder of a creator-economy SaaS
Who did what
Burhan Pasha was the client lead and owned delivery. Saif Pasha ran the translated calls with the founder, found the way into a platform with no API, and led the engineering behind the extension, the headless browser sync and the queue that kept it running. The Silverthread Labs team built the extension, the web app and the infrastructure around it.
If your product needs to work with a platform that was never built to be worked with, start here.