# japan-message-etiquette (`next_motion/japan-message-etiquette`) Actor

- **URL**: https://apify.com/next\_motion/japan-message-etiquette.md
- **Developed by:** [TOHRU NISHIHARA](https://apify.com/next_motion) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 message checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Japan Condolence & Celebration Message Checker
Before your AI agent sends a message to someone in Japan, check it for imikotoba (taboo words) and honorific errors. Generated Japanese often slips in words like 重ね重ね or たびたび in condolences — a serious faux pas.
Checks
Taboo words by occasion: wedding, funeral/condolence, birth, get-well (omimai), store opening, housewarming
Buddhist terms to avoid in Christian or Shinto condolences (冥福, 成仏, 供養)
Honorific errors: 御中 + 様 together, 各位様, 先生様, title + 様
Each finding has position, reason (EN/JA) and a suggested replacement
Input

```json
{"requests": [{"text": "重ね重ねお悔やみ申し上げます。", "occasion": "funeral", "religion": "christian"}]}
```

Occasions: `wedding`, `funeral`, `birth`, `omimai`, `new_business`, `housewarming`, `business`. Up to 100 messages per run.
Verdicts
`ok` · `caution` (check context) · `ng` (fix before sending) · `unsure` (occasion not covered)
Dictionary-based; may flag harmless usages. Pay per checked message. Operated by NEXT MOTION Inc., Japan. See also: Japan Gift Etiquette Judge, Japan Cash Gift Judge.

### Background

Why AI agents get Japanese etiquette wrong (Japanese article): https://zenn.dev/nextmotion/articles/8f494716422019

# Actor input Schema

## `requests` (type: `array`):

One object per message (max 100). Required: text (Japanese), occasion (wedding, funeral, birth, omimai, new\_business, housewarming, business). Optional: religion (christian, shinto) for funeral messages.

## Actor input object example

```json
{
  "requests": [
    {
      "text": "このたびは重ね重ねお悔やみ申し上げます。心よりご冥福をお祈りいたします。",
      "occasion": "funeral",
      "religion": "christian"
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

One checked message, with taboo words, honorific errors and suggestions.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "requests": [
        {
            "text": "このたびは重ね重ねお悔やみ申し上げます。心よりご冥福をお祈りいたします。",
            "occasion": "funeral",
            "religion": "christian"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("next_motion/japan-message-etiquette").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "requests": [{
            "text": "このたびは重ね重ねお悔やみ申し上げます。心よりご冥福をお祈りいたします。",
            "occasion": "funeral",
            "religion": "christian",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("next_motion/japan-message-etiquette").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "requests": [
    {
      "text": "このたびは重ね重ねお悔やみ申し上げます。心よりご冥福をお祈りいたします。",
      "occasion": "funeral",
      "religion": "christian"
    }
  ]
}' |
apify call next_motion/japan-message-etiquette --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,next_motion/japan-message-etiquette"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/3xAbhE4TbyvXawwAJ/builds/SDieqbO6Vufk2vCnv/openapi.json
