What it adds

Tools 1

reinfolib_quarter

Environment variables it needs 1

REINFOLIB_API_KEY

README

From the reviewed commit 9191d0e ↗; it updates when the author re-pins.

jp-reinfolib

Read one city's MLIT transaction prices for one year and one quarter. The tool is reinfolib_quarter. It calls XIT001 only (priceClassification 01, language ja). It does not create a cron job, and it does not write a file.

「このサービスは、国土交通省の不動産情報ライブラリのAPI機能を使用していますが、提供情報の最新性、正確性、完全性等が保証されたものではありません」

A reply that includes a count or an excerpt also includes:

出典：国土交通省　不動産情報ライブラリ（https://www.reinfolib.mlit.go.jp/）

「不動産取引価格情報」（国土交通省）をもとに件数と抜粋を作成

The only site link is that top page. The product name and the tool name do not use the Japanese name 不動産情報ライブラリ as a product name. Site terms article 3 (7) do not allow that name for a product, service, or application unless MLIT approves it. The identifier jp-reinfolib is the host token. MLIT has not been asked about this.

Quick start

Set REINFOLIB_API_KEY in the Hermes process environment or in the profile's .env; the plugin reads it through the Hermes secret scope. An empty value is not sent. The key is the header Ocp-Apim-Subscription-Key and is not placed in the URL.

HERMES_HOME selects the Hermes home you are talking to. A command with no HERMES_HOME and no -p uses that process's default home. This plugin does not take -p or --profile. Those are Hermes flags.

hermes plugins install <owner/repo>
hermes plugins enable jp-reinfolib

Ask for reinfolib_quarter with city, year, and quarter. city is five ASCII digits. The first two digits are 01–47. Example: 13104 is Shinjuku-ku. A designated city needs a ward code, not the city code. Example: 14101 is Tsurumi-ku, Yokohama, not 14100. Those 20 city codes are the rows without 区 on the Ministry of Internal Affairs sheet 「R6.1.1政令指定都市」 in the 2024-01-01 workbook https://www.soumu.go.jp/main_content/000925835.xlsx. The API uses the first five digits of that six-digit code. A designated-city code is refused before any request, with error_type bad_city and problem designated_city. The submitted code is not copied. A municipality name is refused as invalid_argument / bad_city before any request, and the name is not copied into the error. The error names field, problem, expected, and allowed_fields. This plugin does not look names up. MLIT XIT002 lists municipality codes. Years run from 2005 through the current year. 2005 allows quarters 3 and 4 only. A quarter whose first month is still ahead of today is refused before any request. price_classification defaults to 01 and language defaults to ja. Any other value, or any other argument, is refused before any request, in the same field / problem / expected / allowed_fields shape.

Slash form, which does not schedule anything:

/jp-reinfolib 13102 2015 2

What a call returns

ok true means count is the full length of the official rows and records is the first 20 of those rows, keeping only these 12 columns: Type, Region, MunicipalityCode, Prefecture, Municipality, DistrictName, TradePrice, PricePerUnit, Area, UnitPrice, Period, PriceCategory. Official columns that are not in that list are dropped, including FloorPlan, BuildingYear, Structure, Use, Purpose, Remarks, and DistrictCode. truncated is true when count is greater than 20. period is {year}年第{quarter}四半期. fetched_at is UTC when this result was built, YYYY-MM-DDTHH:MM:SSZ. It is not the upstream publication time.

count_by_type counts Type over every row in the quarter, not over the 20-row excerpt. median_trade_price is computed from TradePrice values that are non-empty ASCII digit strings, read as integers, over the whole quarter. Those values are sorted. An odd count uses the middle value. An even count uses the mean of the two middle values. When that mean is a half, the string ends in .5. It is not a binary float. Empty prices and values that are not digit strings are left out. If none remain, median_trade_price is null. median_trade_price_by_type uses that same rule once per Type. A type with no digit price is left out.

The XIT001 manual types Area, TradePrice, PricePerUnit, and UnitPrice as strings. The published example for Area is 80. A value that is not an ASCII digit string is returned as {"kind": "not_digits"} and the original text is not copied. One such field does not discard the quarter. A MunicipalityCode of the right 5-digit shape that is not the requested code is {"kind": "other_municipality", "code": "..."}. The manual does not say that a designated-city code returns ward codes. A code that is not 5 digits is {"kind": "not_code"}, and that text is not copied. Period or PriceCategory that does not match the request still discards the whole body. There is no unit conversion.

error_type not_found with status_code 404 means no data for that city, year, and quarter. It is not zero rows and it is not unchanged prices. The same 404 is what a ward code of the right shape but no published rows returns, so those two cases are not separated. A designated-city code is refused before that request.

Other failures use a fixed English sentence per error_type, plus status_code when the server sent one. The upstream body is not copied. detail is one of a fixed set of words (bad_city, future_quarter, empty_data, and the rest listed in the tool result). When detail is missing_key, the sentence names REINFOLIB_API_KEY. A bad origin and a key that would appear in the URL stay on the shorter config sentence.

Each request stops if no bytes arrive for 30 seconds. There is no separate deadline for the whole call, because a call is one GET. Nothing is retried. The decoded body cap is 8000000 bytes. gzip is decoded only when Content-Encoding is gzip.

After a GET returns, the same process waits 1 second before it starts another. The first GET does not wait. Another process does not share that wait. The wait is not stored in a file.

Plain http is refused before the key is sent, except for 127.0.0.1 and localhost. On that loopback path the key is not encrypted. Redirects are not followed, so a 301, 302, 303, 307, or 308 does not send the key to the next host. A proxy set in the environment is not used, so the key is not sent to it.

REINFOLIB_BASE_URL, when set, is an origin only: scheme, host, and optional port. The path is always /ex-api/external/XIT001.

Who can call it

The tool is on for every surface, including gateways. Anyone you allow on a gateway can call it with your key. There is no separate user list and no approval prompt. A read still runs under cron, yolo, approvals off, and unattended sessions. There is no daily cap. MLIT has not published a numeric request cap.

Stop the tool with hermes tools. That switch does not stop /jp-reinfolib. Stop the slash command with allow_admin_from, user_allowed_commands, group_user_allowed_commands, or by disabling the plugin. A room's group_user_allowed_commands can also apply to DMs.

Weekly check

The Automation Blueprint jp-reinfolib:weekly-city-check is registered only when Hermes has register_automation_blueprint. Otherwise registration is skipped. The city slot asks for a 5-digit code, not a municipality name. Example: 13104 is Shinjuku-ku. A designated city needs a ward code, not the city code. The default is Monday at 09:00, once a week, in Hermes's timezone or the computer's clock if none is set. It calls only reinfolib_quarter, for the latest started quarter and the quarter before it. Publication lags the quarter, so the latest started quarter is often HTTP 404, and many weeks both reads have no data. It does not say that rows are new, because this plugin does not remember a previous count. Hermes puts a cron instruction in front of the job prompt. That instruction says to answer exactly [SILENT] when there is nothing to report, and Hermes then does not deliver the run. If every read is HTTP 404, this check may answer [SILENT] and the message may not arrive. If a read has data, the run is one short message with period, count, and truncated. A failure is not answered as [SILENT].

This plugin does not create a cron job. The job exists only after you schedule the blueprint. Scheduling it twice creates two jobs. hermes plugins remove does not remove a job you already scheduled. Stop that job with hermes cron remove on its id (and Hermes's -p when the profile is not the default). The blueprint registrar takes no toolset list, so a job you create from it follows Hermes's cron rules and may include MCP servers you have enabled.

When register_automation_blueprint is missing, the tool still loads. The bundled skill weekly-city-check states the same steps and does not create a job.

A scheduled run is one model turn. A turn that calls the tool is at least two model requests.

Update

hermes plugins update jp-reinfolib

Run that in the HERMES_HOME you want to update.

Key handling

The key is compared, as text and as any 12-character span, against the JSON that would be returned, including one percent-decode and one \uXXXX decode. If it matches, the whole result is replaced with error_type internal and a fixed sentence. A twice-encoded value is outside that check.

Checked on the live API

On 2026-10-12, city 13102, year 2015, quarter 2 returned HTTP 200 and 176 rows after gzip. City 01999 for 2015 quarter 2, and city 13102 for 2026 quarter 3, returned HTTP 404. Those calls were at least 1 second apart. Upstream HTTP 429 was not returned. A year outside 2005 through the current year is refused before a request, so it has no upstream status code. The success fixture in this repository keeps the live column names and drops district, price, and area values.

Not checked: contract prices (02), land prices, tile APIs, the top-page notices, and a slash command sent from a real gateway room. Rows added later inside a quarter you already read are not something this plugin tracks. Site terms article 5 (3) say that can happen.

License

MIT. The plugin is standard library only. python_dependencies is empty.

More by TakeshiTGAL

All 23 plugins by TakeshiTGAL →

author-feed❖ Community★ 0

Read one public profile and watch one account, with profile_get, author_feed and author_watch. Disclosure — HTTPS GET only to public.api.bsky.app, no API key, and no program on your machine. The tools are on for every surface, including gateways, and ask for no approval: anyone you allow on your gateway can call them. Turn a surface off with hermes tools. hermes author-feed schedule creates one cron job, a model turn every hour by default (two or more model requests, no daily cap). Delivered to local unless you pass --deliver, so no chat by default. Run hermes author-feed unschedule before removal. A leftover job after the plugin is gone stops with hermes cron remove <id>. Under plugins.isolation: host the watch cannot run and posts a notice saying so on every run. The first run only records what is already there. One run reads at most the latest 3 pages and announces a new post by this account on them. When every row on those pages is new, with no saved post or mark, and the feed still offers another cursor, it also posts a possible-miss notice, at most once in 24 hours while that keeps happening. Replies, including the account's own thread continuations, are not announced. It relies on private Hermes parts, so an update can stop it. State stays in <HERMES_HOME>/plugin-data/author-feed after uninstall.

Tools

doc-markdown❖ Community★ 0

Convert one local file to Markdown with doc_convert on Linux and macOS, built on Microsoft's MarkItDown. Microsoft and MarkItDown are trademarks of the Microsoft group of companies. Disclosure — the doc_markdown toolset is on by default on every surface, including a gateway, so anyone you allow there can call doc_convert; stop it with hermes tools. It does not fetch pages. Unattended sessions still convert when Hermes calls the tool. This plugin creates no cron job. A child process runs MarkItDown with no Hermes keys in its environment; on macOS the plugin runs ps about every 10 ms to watch that child's memory. It stops 8 seconds after its converters load, at 60 seconds if loading never finishes, or above 922746880 bytes. It is not a sandbox: after realpath it may read any allowlisted path it can open. Unpublished Hermes code locates the Hermes home, and a failed check refuses the path. Removal deletes the plugin directory, not the markitdown package. Windows was not tested.

Tools

event-read❖ Community★ 0

Read one CalDAV calendar collection you run, with list_events and read_event. Disclosure — Sends CALDAV_USER and CALDAV_PASSWORD as Basic auth to your CALDAV_URL, does not follow redirects, and starts no local program. Over plain http that password travels unencrypted. The tools are on for every surface, including gateways, and the plugin has no user list of its own: anyone you allow on your Hermes gateway reads the calendar with your password. Turn a surface off with hermes tools. A watch is a cron job you create yourself with hermes cron create. Each run is at least one model turn, there is no daily cap, and the job stays until you run hermes cron remove. Under plugins.isolation: host the watch cannot run and posts a notice saying so on every run. When the watch can run, it reports a problem on the first run, when the cause changes and again after 23 hours, or on every run when its data directory cannot be written. Each request gives up after 20 seconds without data, and a whole call has no time limit. The watch relies on private parts of Hermes, so an update can stop it. State lives in plugin-data/event-read. Not tested against a vendor-hosted calendar.

Tools

hermes-gensyn-delphi❖ Community

Seven read-only tools. Disclosure — Seven read-only tools for Gensyn Delphi prediction markets; no funds move and nothing is signed or sent. Needs Node.js 20.18+ and a manual `npm ci --ignore-scripts` in the plugin folder (installs the pinned @gensyn-ai/gensyn-delphi-sdk and its locked npm deps) before the tools work. Runs a local Node subprocess per call (25 s deadline, not a sandbox). Sends your DELPHI_API_ACCESS_KEY only to delphi-api.gensyn.ai (testnet) or api.delphi.fyi (mainnet); history and quotes read api.goldsky.com and gensyn-testnet/mainnet.g.alchemy.com without the key, and quotes use a throwaway in-memory key the SDK requires. Tools are on for every surface by default, including messaging gateways, where anyone admitted can run these reads on the owner's key (rate limit 30 requests per minute per process); disable per surface with `hermes tools`.

Tools

hermes-gensyn-ree❖ Community

ree_validate_receipt, ree_verify_receipt, ree_infer. Validate does not re-execute and does not stand behind text_output, finish_reason, token_count, model.name, or ree_version. Verify re-executes on CPU. Infer runs one of three small models and writes one receipt. Disclosure — Starts containers from the local image gensynai/ree:v0.8.0 (pinned by digest) and never pulls it; running docker pull yourself is consent to the REE-Binary-License. ree_verify_receipt and ree_infer mount ~/.cache/gensyn and ~/.cache/huggingface read-write (a Hugging Face token file stored there is visible to the container; no token is passed in the environment), may download Hugging Face weights for any model a receipt names, and their container network is not limited to Hugging Face; they ask for Hermes approval on every call and refuse under cron, yolo, approvals off, single-query, unattended runs, host isolation, or when the approval API is missing. ree_validate_receipt runs with network none, does not ask, and returns no receipt text. Any person admitted to one of your gateways can call these tools and approve containers on your Docker daemon; disable per surface with hermes tools. Choosing "always" adds one config.yaml allowlist line per call and never covers the next call. New receipts and temporary work files are written under ~/.cache/hermes-ree; nothing is stored under HERMES_HOME. The container is not a hostile-code sandbox. No cron is created.

Tools

index-search❖ Community★ 0

Search one index you run and watch one saved query, with index_search, index_health and index_watch. Disclosure — Sends MEILI_API_KEY as a Bearer token to your MEILI_HOST. Over plain http that key travels unencrypted, and a master or admin key is sent as given, so use a search-only key. The tools are on for every surface, including gateways: anyone you allow on your Hermes gateway can search with your key and approve a watch. Turn a surface off with hermes tools. index_watch schedule creates one cron job that runs a model turn every 15 minutes (two or more model requests when it calls the tool) with no daily cap, and it watches only the first 20 hits. The job stays after uninstall until you run hermes cron remove, with -p and the profile name when the profile is not default. Scheduling and unscheduling ask for Hermes approval every time and are refused under cron, yolo, approvals off, unattended sessions and plugins.isolation: host, where the watch only posts a notice that it cannot run, on every run. Answering "always" adds an unused line to config.yaml. The watch relies on private parts of Hermes, so an update can stop it.

Tools

← Back to the catalog · catalog built Oct 17, 2026