JAPAN COMMERCE MCP

Give your AI agent a Japan commerce layer.

One authenticated endpoint exposes the same Japan address, company, sellability, and profitability capabilities as bounded MCP tools. Your agent keeps source availability, missing facts, and warnings instead of inventing certainty.

Get a free API key Try on RapidAPI View setup

Read-only and computeNo email, purchase, publishing, arbitrary fetch, write, or delete tools.

One platform keyThe same key, plan limits, and usage controls apply.

Source-backed outputProvenance and unresolved facts remain visible.

14 PRODUCTION TOOLS · 8 DOMESTIC

From one fact lookup to a Japan entry plan.

resolve_japan_address

Normalize a Japanese address and preserve match evidence.

search_japan_business

Return business candidates without guessing one identity.

resolve_japan_business

Resolve a company with official-source provenance.

check_japan_sellability

Check Japan requirements, missing facts, and current decision.

estimate_japan_profitability

Estimate Japan selling economics with assumptions visible.

plan_japan_commerce_entry

Run sellability then profitability as one bounded plan.

japan_company_verify

企業の実在、法人番号、所在地を確認する。インボイス状態だけの確認には使わない。

japan_address_verify

住所の存在、郵便番号、自治体、一致度を検証する。企業確認には使わない。

japan_invoice_verify

適格請求書発行事業者の登録状態を確認する。企業全般の調査には使わない。

japan_company_name_normalize

法人名を比較・名寄せ可能な形式へ正規化する。実在確認は行わない。

japan_municipality_lookup

住所・郵便番号・自治体名から正式自治体名とコードを返す。

japan_product_sellability

商品を日本で売れるかを判定する。必要手続の詳細だけならcomplianceを使う。

japan_product_compliance

日本で売るための法令、許可、認証、表示、検査、次アクションを返す。

japan_profit_calculate

日本販売時の売上、費用、利益、利益率を計算する。規制判定だけには使わない。

QUICK SETUP

Connect through stateless Streamable HTTP.

Use the production endpoint https://api.japanapistore.com/mcp, send your key as a Bearer token, and keep it in the client's secret configuration. The request below is a protocol-level smoke test for clients that support custom HTTP MCP servers.

curl -X POST https://api.japanapistore.com/mcp \
  -H "Authorization: Bearer $JAPAN_API_KEY" \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: tools/call" \
  -H "Mcp-Name: check_japan_sellability" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_japan_sellability","arguments":{"product_name":"Bluetooth speaker","category":"Electronics","wireless_function":true},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"my-agent","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

Client compatibility

MCP clients differ in how they configure authenticated remote HTTP servers. Use the client's current remote-server settings and never paste the API key into a prompt, repository, or shared config.

EXAMPLE PROMPT

Ask for a decision, not a tool name.

“Can I sell a Bluetooth speaker in Japan, what facts are still missing, and what would the estimated profit look like at ¥8,900?”

The agent can select plan_japan_commerce_entry, return the sellability result first, then the profitability result, while keeping assumptions and missing facts separate.