How we write

The proxymint team: the people who build and run proxymint and answer support. AI tools research, draft, edit and run the first review passes. The team sets the rules every post must pass, and each post is signed by the founder responsible for it: Nick S. or Andrew P.

Automated checks run on every draft: every internal link must point to a live page, and a post may carry no prices.

A fact-check pass compares every claim about proxymint with our own product records and cuts what they do not back. A critic pass then checks each claim and whether the advice fits the reader's job, and fixes what fails. Every post is queued for the team before it publishes, and anyone on the team can stop it.

We cite the primary source wherever one exists: the standard itself, the vendor's own documentation, the court record, the site's own terms. Citations link the source and usually carry a date, the day it was published or the day we checked it.

Our own measurements run on our own gateway and publish with the date, the sample, the method and the commands to rerun them. The first one is proxymint Lab #1.

The proxy check shows what a site sees from your connection, in your own browser. The proxy format converter turns a proxy list into the format your client expects. The status page checks our API and dashboard live.

How to get past a site's blocks, captchas or terms. A block means stop: posts about collecting data lead with the site's official API or data route.

Prices. How pricing works is explained on the pricing page, never inside a post.

Only a change in substance moves the updated date. A typo fix or a new link does not, so the date always means something.

Found a mistake? Send the page and the error to support@proxymint.com. We fix it, and when the correction changes the substance of the post, its updated date moves.

Corrections made after a post goes live are listed here and under the post itself, with their date.