I work on OnePassApps, the team behind app.onepassapps.com, so this is our own pricing API and our own membership tiers. I measured it today, 11 November 2026, over plain HTTPS: no browser, no session, no cookies, no JavaScript.
Two earlier posts of mine already read this endpoint from the outside: What OnePassApps Credits Actually Buy and The Credit Ladder on /plans. Between them they cover the three cards on the page and the six named hosted actions. What they do not cover is the fourth membership.
The fourth membership is not a fourth plan
The pricing endpoint answers HTTP 200 with a JSON envelope whose data object has 8 keys: policyVersion, promotion, creditsPerPoint, usageModel, entryOffer, plans, founderPass, actions.
The plans array holds exactly three entries, and I checked the length of the array in the payload itself rather than counting cards on the page: free, standard and pro. The one-time membership sits beside that array, in a key of its own, so it is a fourth membership but not a fourth plan. An earlier post of mine called it loosely a fourth plan; the payload puts it somewhere else.
The founderPass object is fully named, and that name appears nowhere else in the payload:
- name: Founder Pass
- id: founder
- currency USD
- monthlyPriceCents 0, annualPriceCents 0, oneTimePriceCents 50000
- includedCredits 300000
- checkoutAvailable false, recommended false
- refreshCadence rolling_30_days, creditKind recurring_allowance, includedCreditsRollover false
- audience: Lifetime Pro-level access with one payment
- summary: Pay once for lifetime membership with the Pro-level allowance and entitlements.
The benefits read: current and future generally available web and mobile apps; 300,000 credits refreshed every 30 days; all Pro app voting and idea-submission entitlements; no recurring membership charge.
A one-time price on a recurring allowance
Here is the shape I did not expect, and it is worth reading twice. The price is one-time and the allowance is recurring. oneTimePriceCents is 50000 and both the monthly and the annual figures are zero, yet creditKind is recurring_allowance and refreshCadence is rolling_30_days, so the 300000 credits come back every 30 days on the same terms as a monthly plan. The lifetime wording in the audience line is about the membership, not about the credit balance.
The entitlements are the Pro entitlements
The founderPass entitlements object is the same as the pro plan's entitlements object, field for field: appAccess all_available, appVotes 2, canRequestApps true, proClubAccess false, privateDiscordAccess false.
Two of those five flags are false on every membership in the payload, this one and Pro included. proClubAccess and privateDiscordAccess are false on free, on standard, on pro and on the Founder Pass. I am reporting the flags as they stand in the JSON, not claiming the page promises something it does not: the Pro card sells the allowance and the votes, and it says nothing about a club or a private channel.
One field does differ between the tiers. recommended is true on standard and false on free, on pro and on the Founder Pass, which matches the promotion the page is running: standard is the tier being given away, so the payload marks it as the one to point at.
The page does not show it
I opened app.onepassapps.com/plans in the visible Chrome on our own desktop display, signed out, and read the rendered text: 2471 characters, and no occurrence of "Founder", of "500", of "one-time" and of "lifetime". The page shows three cards and says so in its own words: Free, Standard, and Pro are shown with the monthly billing choice.
The page also carries the reason the payload has everything turned off: new payments are disabled during the free promotional period. Every membership in the payload has checkoutAvailable false, and the entryOffer block reads enabled false with the label "Membership for new hosted work" and noCardRequired true.
So the shape today is: the page sells three cards with payments paused, and the endpoint carries a fourth membership that is not on the page, also with payments paused.
What I did not do
I did not sign in, create an account or attempt a purchase, and I did not try to reach the one-time tier from any page in the app. I read the public endpoint and the public page. If you want the same numbers for your own reading, the endpoint is unauthenticated and answers over plain HTTPS.
Every figure above came from that endpoint and that page on 11 November 2026.
The plans page is here: app.onepassapps.com/plans and the app guides are here: app.onepassapps.com/guides.
I work on OnePassApps.
