Resend is one of the developer email APIs Japanese engineers actually reach for — it shows up in Japanese dev writing on its DX alone, with no help from Resend. That's the tell: the demand is already here, pulled in by the product. What's missing is everything around it. There's no Japanese surface at all, and for an email product specifically, there's a second gap most tools don't have — nothing that speaks to how email actually lands in Japan.
Resend has no Japanese surface: no hreflang ja, no /ja route (404), no Japanese documentation (resend.com/docs/ja → 404). Yet Japanese developers adopt it anyway, on developer experience alone — it appears in Japanese engineering blogs and Zenn-style writeups without Resend doing anything to earn that.
This is the most winnable kind of gap: the pull already exists. A Japanese developer evaluating an email API in Japanese finds blog posts but no Japanese docs, no Japanese onboarding, nothing official in their language — so the team defaults to a domestic option (or SendGrid's established Japanese presence) for anything beyond a side project, even though the developers personally prefer Resend.
A Japanese docs surface and a /ja route (hreflang-paired) for the highest-traffic pages — capturing the developers who already arrived on their own.
Resend's docs and marketing say nothing about sending email into Japan. Japanese email has realities a global sender hits immediately: carrier addresses (docomo / au / SoftBank keitai email) with their own filtering and reception quirks, Japanese-language subject and body handling, and the sender practices Japanese recipients and mailbox providers expect.
A Japanese team choosing an email API specifically needs to trust that mail reaches Japanese inboxes. With no Japan-deliverability guidance, the evaluation is "will this even land for our users?" — and silence reads as "they haven't thought about Japan." This is the gap a generic localization pass never fills, because it isn't translation; it's domain knowledge.
A Japan-deliverability guide (carrier email, Japanese sender best practices) — the kind of authority content that turns "do they get Japan?" into "they clearly do."
No 特定商取引法に基づく表記 page was found. Paid tiers price in USD ($20 and up) with no JPY path, and since Japan's 2023 インボイス制度 a foreign USD invoice generally isn't a 適格請求書.
resend.com/pricing — USD only, no 特商法A Japanese company putting Resend on the company card runs it through procurement, which looks for the 特商法 disclosure and prefers a qualified JPY invoice it can deduct consumption tax against. Neither exists, so the paid upgrade — the moment the relationship becomes revenue — hits avoidable friction.
A 特商法 page and a JPY invoicing path for the paid tiers, so the upgrade from the free dev tier to a paid Japanese-company account is frictionless.
With no Japanese pages indexed, Resend surfaces for none of the queries a Japanese developer or team types — 「メール送信 API」, 「SendGrid 代替」, 「transactional email 日本」, 「メール API 比較」.
The individual developer already found Resend. The team decision — the one with budget — starts with a Japanese search, and Resend isn't there. The domestic competitor or the incumbent with a Japanese page gets shortlisted, and Resend's DX advantage never gets to argue its case.
Japanese pages targeting the email-API comparison and alternative-to queries, anchored to the Japan-deliverability content from gap 2.
Five signal dimensions, each 0–20. Verified 2026-06-23:
| 1. Japanese marketing / docs funnel | 3 / 20 |
| 2. Legal / trust (特商法) | 0 / 20 |
| 3. JPY billing / payment | 3 / 20 |
| 4. JP search visibility | 3 / 20 |
| 5. Product Japan-fit (deliverability / locale) | 8 / 20 |
Dimension 5 gets partial credit — Resend handles Unicode and the product works fine for Japanese senders — but loses most of it for having no Japan-deliverability guidance, the one product-fit question an email API specifically has to answer. The score is low not because Resend is weak; its DX is exactly why Japanese developers already use it. It's low because none of the surface that turns that organic pull into Japanese revenue exists yet.
This map is the free slice. The full Japan-readiness audit for Resend covers the Japanese docs/route plan, a Japan-deliverability content outline, the 特商法 fields filled in, JPY billing for the paid tiers, and the Japanese search queries to target — sequenced by return.
Data verified 2026-06-23 against resend.com and its docs/pricing. Scores estimate Japan-market readiness, not product quality — Resend's developer experience is excellent. Corrections or opt-out: hello@glovrex.com.