Distinguish Mercari US (no public API) from the separate Mercari Shops Japan API when planning integrations
domain: mercari.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the target: mercari.com (US consumer marketplace) has no public seller API - only unofficial scrapers exist
Do not confuse it with Mercari Shops (api.mercari-shops.com), a real GraphQL API that serves only Japan's separate small-business storefront product with Japanese-language docs
For US Mercari, plan on manual listing through the app since there is no documented bulk-listing or order-sync mechanism
If a Japan-market integration is actually the goal, register through the Mercari Shops developer portal instead, which is a distinct product and account system
Known gotchas
Vendors and articles sometimes conflate 'Mercari API' across the US and Japan products - verify the domain and language of any docs found before building
No public roadmap has been published for a US Mercari public API
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?