Proxies for Mercari do one of three jobs: opening Mercari Japan from outside Japan, keeping a resale account off Mercari's account-linking radar, or scraping sold prices without tripping its bot checks. Mercari cares about one rule above all, one person per account, so the wrong proxy for Mercari gets a second account flagged or a scraper blocked inside a handful of requests.
We run a proxy network, so we see both ends of this: the Mercari accounts people keep alive for months, and the batches that go "under review" in a week. This is the honest version of which proxy type fits which job, how many IPs you need, why accounts want a fixed IP and scrapers want a rotating one, and the part a proxy cannot fix.
What proxies are best for Mercari?
For running accounts, static residential or ISP proxies, one dedicated IP each, geo-matched to the account's country. For scraping listings and sold prices, rotating residential, since datacenter ranges get challenged and repeat visitors get rate-limited. For reaching Mercari Japan from abroad, a residential IP inside Japan. Datacenter lands a new account "under review" fast, and free public proxies are worse.
Why people use proxies for Mercari
Three jobs cover almost everything, and they do not want the same kind of IP.
- Reaching Mercari Japan from another country. Mercari runs two separate markets: Mercari US at mercari.com and Mercari Japan at jp.mercari.com. The Japanese market is far larger and full of listings that never surface anywhere else, which is why collectors and resellers abroad want in. It is built for Japan, though: from a foreign connection much of it is gated, and the app is not offered in non-Japanese app stores. A Japanese residential IP lets you browse and search the real jp.mercari.com catalog and read live prices, the first thing anyone sourcing from Japan needs.
- Stealth and second selling accounts. Mercari's terms are one account per person, and suspensions are meant to stick. Sellers who get banned, or who want a second storefront, open fresh accounts, and Mercari's defenses exist to catch that. The moment a new account shares an IP, device, phone number, or payout method with a banned one, Mercari links them, and the new account tends to land "under review" before the first sale.
- Scraping and price research. Mercari's sold-listing history and live asks are the comps resellers price against, like eBay sold prices. There is no open public API, so pricing tools and arbitrage sourcing pull the pages and internal endpoints directly, which runs into Mercari's rate limits and bot checks. Rotating residential IPs spread the load so no address looks like a machine.
What Mercari actually reads
Mercari links accounts and spots automation off a stack of signals. A proxy touches only the first, which is why people who treat an IP as the whole disguise get caught.
- IP address and subnet. The loudest network signal. Two accounts on one IP, or one small subnet, read as one owner. Hosting and datacenter ranges are distrusted on sight, and a public IP a banned Mercari account already used is dirty before you start. Signups from a flagged IP routinely land "under review" on day one.
- Device fingerprint. Mercari is app-first, and the app reads a hard device identifier alongside canvas, fonts, and screen signals. Two accounts from one phone get clustered even behind clean IPs, so serious multi-account sellers run separate devices, not just separate proxies.
- Phone number. Selling on Mercari needs an SMS-verified phone number, and this is the identifier Mercari leans on hardest. One number per account, and a number reused from a banned account relinks the new one immediately. No proxy touches this.
- Payment and payout details. A linked card, bank account, and shipping address tie an account to a real person. Reuse a payout method or address from a suspended account and Mercari connects them regardless of how clean the IP is.
- Challenges and rate limits. Signup and login serve a reCAPTCHA when traffic looks automated, and the browse and search endpoints rate-limit an IP that reads too fast. Datacenter IPs and machine-gun timing trip both quickly.
- Region and market. A US IP sees mercari.com in dollars; a Japanese IP sees jp.mercari.com in yen. Point a session at the wrong country and you read the wrong market's prices, poisoning any sourcing math.
Which proxy type fits which Mercari job
Four proxy types show up in Mercari setups, and the cheapest is rarely the right one.
Datacenter proxies come from hosting providers, and Mercari can tell. Fast and cheap, but for accounts they are the quickest route to an "under review" hold, and for scraping they get challenged almost immediately.
ISP proxies are static residential IPs on datacenter-grade hardware: they read as a real home connection but stay fast and always on. For Mercari accounts this is usually the sweet spot. The IP is residential and never changes, so an account keeps logging in from one trusted address for months.
Residential proxies are IPs from real home connections. For scraping Mercari they are the right call, because they look like ordinary shoppers and rotate across a large pool so no single address stands out. A Japanese residential IP is also what opens Mercari Japan from abroad. If the type is new to you, our explainer on what a residential proxy is covers how it differs from datacenter.
Mobile proxies are carrier 4G and 5G IPs, shared by thousands of real phones behind Carrier-Grade NAT. Mercari cannot hard-ban one without hitting genuine customers, which makes mobile the most durable tier for an account that keeps getting burned. It is the priciest option, and most setups never need it.
| Mercari job | Proxy type that usually works | Session mode | Notes |
|---|---|---|---|
| Stealth or second selling account | ISP or static residential | Static, one IP per account | One IP each, never shared; datacenter lands "under review" |
| Scraping listings and sold prices | Rotating residential | Rotate, sticky per search | Beats rate limits and challenges; datacenter flagged |
| Reaching Mercari Japan from abroad | Residential in Japan | Sticky per session | Opens jp.mercari.com; checkout still needs JP payment + address |
| Repeatedly burned, high-risk account | Mobile (4G / 5G) | Static or sticky | Hardest IP to ban; fits the app; highest cost |
| One-off market peek or a test | Free list, then verify | n/a | Fine to look; never to build an account on |
The rule in that table is the money-saver: use the cheapest tier the job tolerates, and step up only when holds or blocks prove you must.
Sticky or rotating: the job decides
This is where Mercari setups go wrong most often, because the two main jobs want opposite things from the same proxy.
An account wants to stay put. A real seller logs in from the same home connection every day, so a Mercari account should hold one static IP and never move off it. Rotate an account's IP and you have told Mercari it is either traveling impossibly or being shared, and both draw a review. Static residential and ISP proxies hold one address indefinitely. If all you have is a rotating pool, pin it to a sticky session so the account still sees one steady exit.
A scraper wants the reverse. Pulling thousands of listings from one IP is the fastest way to hit Mercari's rate limit, so scraping wants rotation: a fresh IP per request, or a short sticky window long enough to page through one search before moving on. Browsing Mercari Japan to source deals sits in between: hold one Japanese IP sticky for the session so your searches stay coherent, then drop it. Same provider, opposite settings, and getting it backwards is behind a large share of the Mercari problems we see.
How many IPs you actually need
Size it from the job, not a number that sounds impressive. For accounts, one dedicated static IP per account, never shared: two accounts on one IP is the exact pattern Mercari links, so five stealth accounts means five separate IPs, each geo-matched, ideally on different subnets.
Mercari accounts (one dedicated static IP each, never shared):
account A -> 198.51.100.20 ISP, US, matches its address + phone
account B -> 198.51.100.21 ISP, US, its own device / antidetect profile
account C -> 203.0.113.10 residential, Japan, a jp.mercari.com seller
Scraping Mercari (rotating residential, sized by bandwidth):
one pool -> rotate per request, sticky only while paging one search
Sourcing from Mercari Japan (browse only):
one JP IP -> sticky for the session, reads jp.mercari.com in yen
For scraping there are no named IPs to count: you buy bandwidth through a rotating pool, which is why residential is metered per gigabyte, not per address. Our pricing is pay-as-you-go with a balance that does not expire, so held IPs and burst scrapes bill for what they use, not idle time.
The free versus paid reality for Mercari
Free proxies and Mercari are a bad match, and it is worth being blunt about why. Most free proxies are datacenter IPs that die within minutes, and only a small fraction work at any given moment. For scraping Mercari they get challenged and rate-limited almost as fast as you load them. For an account it is worse: a free public IP has been used by hundreds of people, some who ran banned Mercari accounts through it, so it is already dirty, and a new account on it can land "under review" the day it is created. Free public proxies are also the shared, logged, sometimes hostile kind we cover in are free proxies safe.
Where free is genuinely fine: a one-off look at how a price shows in another market, or testing that your scraper's plumbing works before you point paid IPs at it. Our free proxy list at /free-proxy-list re-checks and refreshes every few minutes and spans 100+ countries across HTTP, HTTPS, SOCKS4, and SOCKS5, so it is a real tool for a quick job, including a first peek at Mercari Japan.
For real Mercari work the paid line is simple: rotating residential for scraping, a dedicated static IP for accounts, a steady Japanese residential IP for Mercari Japan. Our residential proxies start at $0.99/GB pay-as-you-go with no KYC, which covers all three without a monthly commitment.
Setting it up without getting flagged
For scraping, setup is ordinary. Put a rotating residential proxy in your HTTP client or headless browser, region-match it to the market you are pulling (US or Japan), pace the requests so you do not machine-gun the endpoints, and back off on the first reCAPTCHA instead of retrying straight into a block.
For accounts and for Japan access, the proxy is only the first layer:
- One dedicated IP per account, held static, geo-matched to the account's country, and never touched by any other account of yours.
- A separate device or antidetect profile per account. Because Mercari is app-first and reads a device ID, a clean IP behind a shared phone still clusters. The proxy fixes the network identity; a separate device or antidetect browser fixes the device one.
- Fresh hard identifiers. A new SMS-verified phone number, and a card, payout method, and address not tied to any banned account. This is the layer people skip and the one Mercari leans on hardest.
- Never cross the streams. Do not log into the new account and the old, burned one from the same IP, device, or phone number, ever. One slip links them.
- Verify the IP before you build on it. Confirm it is alive, residential, and in the right country first, especially for a Japanese IP where the whole point is the location. Our free checker at /proxy-checker shows the real exit location, and our walkthrough on how to check if a proxy is working covers what to look for.
The honest part
A proxy solves one problem completely: it makes each account, scrape request, or Mercari Japan session come from a clean, believable connection in the right country. That matters here, because the network is the loudest link and the geo-lock is real. But it is one layer, and Mercari has more.
The layer no proxy touches is the hard-identifier stack. Selling on Mercari means an SMS-verified phone number, a linked card or bank account, and a real address, and Mercari links accounts by those no matter how clean the IP is. A reused phone number or payout method relinks a suspended seller instantly. Mercari Japan goes one further: a Japanese IP lets you browse and search, but checking out still needs a Japanese payment method and a Japanese shipping address, which is why forwarding services like Buyee or ZenMarket exist to hold those for buyers abroad. That is the honest ceiling, and any provider selling proxies as a guarantee against a Mercari ban, or as a full key into Mercari Japan checkout, is selling a story.
What good proxies do is give your setup a fair, isolated shot: accounts that look like separate real sellers, scrapes that look like ordinary shoppers, and a genuine Japanese connection into Mercari Japan. For accounts that means ISP or static residential; for scraping and Japan access it means residential, rotating for the scrape and steady for the browse. Start free on our list at /free-proxy-list, re-checked every few minutes, good for a market peek or a plumbing test. When it is a real account, scrape, or line into Mercari Japan, move to residential at $0.99/GB pay-as-you-go with no KYC, and let the rest of your setup do its part.
Frequently asked questions
What kind of proxy is best for Mercari?
It depends on the job. For a selling account, use ISP or static residential proxies, one dedicated IP per account, held in place and geo-matched to the account's country. For scraping listings and sold prices, use rotating residential, because datacenter ranges get challenged and repeat visitors get rate-limited. For reaching Mercari Japan from abroad, use a residential IP inside Japan. Datacenter proxies are the fastest route to an account landing under review, and free public proxies are worse.
Can a proxy let me buy from Mercari Japan from another country?
A Japanese residential IP lets you browse and search the real jp.mercari.com catalog and read live prices, which is the part most buyers abroad are missing. It does not let you check out. Mercari Japan still needs a Japanese phone number, a Japanese payment method, and a Japanese shipping address, none of which a proxy provides. That gap is why forwarding and buying-proxy services (Buyee, ZenMarket, and the like) exist to hold the Japanese payment and address for you. The proxy gets you seeing the market; the forwarding service gets you the item.
Will a proxy stop my Mercari account from being banned or linked to a banned one?
Only partly. A clean, separate IP removes the loudest link, the network one, but Mercari also links accounts by device fingerprint (it is app-first and reads a device ID), by the SMS-verified phone number, and by payment and address details. A dedicated IP is necessary but not sufficient. You also need a separate device or antidetect profile and fresh hard identifiers, because Mercari relinks a suspended seller instantly off a reused phone number or payout method.
How many Mercari proxies do I need?
For accounts, one dedicated static IP per account, never shared, so five accounts means five separate IPs, each geo-matched and ideally on different subnets. Two accounts sharing one address is the exact pattern Mercari links together. For scraping there are no named IPs to count: you buy bandwidth through a rotating residential pool and size by how much data you pull. For sourcing from Mercari Japan you need one steady Japanese IP per browsing session.
Can I use free proxies for Mercari?
For a real selling account, no. Most free proxies are datacenter IPs shared by hundreds of people, already flagged, and sometimes already used by banned Mercari accounts, so a new account built on one can land under review the day it is created. Free proxies are fine for a one-off look at how a price shows in another market, or for testing a scraper's plumbing. Verify any proxy with a checker before you rely on it.