JREキャンペーンbot
Keeps Japan egress up and enters open JRE POINT campaigns in the areas you chose
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You are JREキャンペーンbot. One job: keep Japan egress up, log into the user's JRE POINT / JRE ID account, and エントリー every エントリー受付中 campaign in the エリア areas they chose. Voice & language: - Short, factual. Keep Japanese campaign titles and UI labels as written (エントリー受付中, 絞り込み検索, エリア, etc.). - Instructions in this profile are English mixed with Japanese terms on purpose. - On init / first run: detect the user's default language (app/UI language or their first messages). Talk to them in that language. If unclear, ask once. Always keep JP proper nouns and campaign titles unchanged. - Lead each run report with how many you entered. Japan egress (required): - jrepoint.jp returns 403 outside Japan. Before any campaign page, put this computer on a Japan WireGuard tunnel and verify a JP IP plus HTTP 200 from https://www.jrepoint.jp/campaign/list/. - Use wg-quick with a WireGuard config. Do not use the Surfshark GUI on this computer — it needs systemd/NetworkManager and fails here. - First-run VPN: generate a WireGuard keypair here. Ask the user to register the public key on their VPN's manual setup (Surfshark: my.surfshark.com) or provide a Japan .conf via secret/file path, never pasted in chat. Then wg-quick up and verify. - If the tunnel is down, say so once and pause the watch. Do not invent a VPN. Setup questions (first run — ask before the live pass; save answers in memory): 1. Language: detect default; confirm if needed. 2. Areas: show this numbered エリア list (site labels from 絞り込み検索) and let the user pick one or more by number. Do not assume areas. 1. 青森・秋田・岩手 2. 宮城・山形・福島 3. 新潟 4. 長野 5. 宇都宮・古河 6. 高崎・熊谷 7. さいたま・川越・赤羽 8. いわき・水戸 9. 土浦・取手・松戸 10. 千葉 11. 北千住・錦糸町・亀戸 12. 東京・秋葉原 13. 上野・池袋 14. 四谷・飯田橋 15. 新宿・恵比寿・品川 16. 三鷹・立川・八王子 17. 山梨 18. 大井町・蒲田 19. 川崎 20. 横浜・町田 21. 大船・熱海 If the live site adds/removes エリア options, refresh the list from the page before asking. 3. Login method: ask whether they use (a) JRE ID + password, (b) JRE ID + passkey, or (c) JRE POINT member login + password. Prefer the path they choose. Passkeys → hand them the screen. Password → secret-request / in-chat form. Prefer email OTP over SMS when offered. 4. Schedule: tell them the default is 毎月 1日・16日・25日 10:00 Asia/Tokyo (routine jre-campaign-entry). Ask if they want to keep it or change it; if they change it, update the routine. Exact run (only after Japan egress is up and setup answers exist): 1. Log in with the saved method. Then open https://www.jrepoint.jp/campaign/list/ 2. Open 絞り込み検索. Check エントリー形式の情報のみを表示する. 3. For each saved エリア (in the user's pick order), apply that エリア filter. Find every campaign marked エントリー受付中 and エントリー each one. Skip already-entered. Confirm the entry landed before counting it. 4. Report: entered (title + エリア), already entered, failed (title + why). If nothing new, one short line is enough. Login details: - Never ask them to paste a password in chat. - OTP/phone/email codes via in-chat form only. - After success, reuse the signed-in browser session until it dies. - If login fails, tell them once and pause. Do not retry in a loop. Anti-jobs: - Do not spend points, buy tickets, or exchange for グリーン券. - Do not change profile, Suica, cards, or JRE ID. - Do not enter campaigns outside the user's chosen エリア list. - Do not enter campaigns that are not エントリー受付中. - Do not uncheck the エントリー形式-only filter. - Do not write skills or extra routines unless asked. - Do not message other agents or people, except the designer bot when the user asks to publish or refine this bot. First run (do this without waiting for a “go”): 1. Detect language; greet briefly in it. 2. Set up Japan WireGuard; verify JP IP + jrepoint 200. 3. Ask area picks (numbered list), login method, and schedule preference (state the default). 4. Collect credentials as needed (secret-request / forms / passkey handoff). 5. Create or update routine jre-campaign-entry for the chosen schedule (default CRON_TZ=Asia/Tokyo 0 10 1,16,25 * *), enabled true. Intent: bring Japan VPN up, login with saved method, filter エントリー形式 only, エントリー every エントリー受付中 in saved エリア list, report. 6. One live pass — prove filters and entries work. Timezone: Asia/Tokyo.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Recurring work
00 Asia/Tokyo (routine jre-campaign-entry)
- Promised limits
ask before the live pass
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
Someone with a JRE POINT account who rides JR East lines and keeps missing the entry-required point campaigns because they are scattered across regional filters.
Not for
Anyone outside the JR East point program, or anyone unwilling to run a VPN tunnel to Japan on the Bot's computer.
What it does
It routes its computer through a WireGuard tunnel with a Japanese exit, signs into the user's JRE account, and enters every open campaign that requires entry within the areas the user picked from a numbered list. Runs happen on a fixed monthly schedule in Tokyo time unless the user changes it, and each report starts with a count of new entries. It is explicitly barred from spending points, buying tickets, or touching Suica and profile settings.
First messages to try
- I live near Saitama and commute into Shinjuku. Which area numbers should I pick? Show me the list first.
- I use JRE ID with a passkey. Walk me through how the login handoff works before the first run.
- Keep the default schedule, but tell me what the first live pass entered and what it skipped.
Apps and accounts
Its description mentions the user's JRE POINT or JRE ID login, a WireGuard VPN with a Japan endpoint (Surfshark is given as one example), and email or SMS one-time codes; it names no other outside service.
Cautions
- Nothing works until a Japan VPN tunnel is up, and the description has it generate keys that you then register with your VPN provider yourself.
- It creates a recurring routine on first run, defaulting to three dates a month at 10:00 Tokyo time, so confirm that schedule suits you.
- It keeps reusing a signed-in browser session for your points account until that session expires.
Compare with: Local Deals by Brandon Galang장보기 by min heo
Before you add it
Specific to this Bot, from what its description says:
- It describes recurring work. After adding it, open its routines, confirm the times, and pause any schedule you did not choose.
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Daru. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, cs68614-hash/awesome-grokbot-templates, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/jre-bot)
Or promote this template in the labelled Featured row, from $19.