house.bim/bimhouse

REMOTE · BIM.HOUSE · SCANNED AUG 3

bim.house — words become buildings. Generate BIM, check code & structure, quote materials.

Available components

+3 this week 62 62 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 29 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability51

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 6381 tokens (~220/item across 29 items; 29 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage96

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
89% of tool parameters carry a description.Partial

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · bim.house

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http house-bim-bimhouse https://bim.house/mcp

# ~/.codex/config.toml

[mcp_servers.house-bim-bimhouse]
url = "https://bim.house/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "house-bim-bimhouse": {
      "type": "remote",
      "url": "https://bim.house/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add house-bim-bimhouse --url https://bim.house/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  house-bim-bimhouse:
    url: "https://bim.house/mcp"

// mcp.json

{
  "mcpServers": {
    "house-bim-bimhouse": {
      "type": "http",
      "url": "https://bim.house/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 58

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://bim.house/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=bim.house	CN=YE2,O=Let's Encrypt,C=US	7 Jul 2026	5 Oct 2026	ECDSA 256	ECDSA-SHA384	5ea43ab90a367f9197b0c50c6c45f774469
SANs: *.bim.house, bim.house
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of bim.house. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
house.	present	12289	8	Verified
bim.house.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000; includeSubDomains
content-security-policy	default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' blob: https://unpkg.com https://cdn.jsdelivr.net https://cdn.skypack.dev https://js.stripe.com https://enabler-analytics.fly.dev https://koe.live https://www.googletagmanager.com https://www.google-analytics.com; script-src-elem 'self' 'unsafe-inline' blob: https://unpkg.com https://cdn.jsdelivr.net https://cdn.skypack.dev https://js.stripe.com https://enabler-analytics.fly.dev https://koe.live https://www.googletagmanager.com https://www.google-analytics.com; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdn.jsdelivr.net https://unpkg.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' https: data: blob:; connect-src 'self' https://koe.live https://api.qrserver.com https://*.solana.com https://api.devnet.solana.com https://api.mainnet-beta.solana.com https://enabler-analytics.fly.dev https://js.stripe.com https://api.stripe.com https://cdn.jsdelivr.net https://unpkg.com https:
x-content-type-options	nosniff
x-frame-options	SAMEORIGIN
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(self), microphone=(self), geolocation=(self), payment=(self "https://js.stripe.com")

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://bim.house/mcp	Verified	200
http (plaintext)	http://bim.house/mcp	HTTPS enforced	301	https://bim.house/mcp

MCP tools — 29 exposed · ~6,278 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

admin_set_site_context ~282

[EN] Bulk-set site conditions for any houses (admin only, admin_token; no edit_token). Pass `entries`: [{slug, zoning?, road_width_m?, high_district?, fire_district?, climate_zone?, latitude?, neighbor_setback_m?, min_lot_area_m2?, shadow_regulation?}]. DB + cache applied immediately. For operators to backfill zoning/road-width (e.g. from reinfolib) across all properties. / 任意の物件の敷地条件を一括上書き (管理者のみ・edit_token 不要)。entries 配列で複数物件をまとめて投入。DB+キャッシュ即時反映。用途地域/道路幅員等の実データを全物件へ流し込む運用者向け。

Input Output Examples

Name	Type	Req	Description
admin_token	string	yes	管理者トークン (必須)
entries	array	—	物件ごとの敷地条件。各要素は {slug(必須), zoning?, road_width_m?, north_setback_m?, neighbor_setback_m?, high_district?, fire_district?, climate_zone?, latitude?, min_lot_area_m2?, shadow_regulation?}
slug	string	—	単一指定する場合 (entries の代わり)

No output schema declared.

No examples provided.

chat ~181

[EN] AI chat about architecture/BIM/code/MU. Requires Bearer API key; first ¥300 (5 calls) free. / bim.house / MU の AI チャット。メール認証して /console で発行した API キーで認証必須 (Authorization: Bearer <APIキー>)。未チャージでも初回 ¥300 分 (5 回) は無料、使い切ったら /credits でチャージ。建築・BIM・法規・SIPs・MU について日本語で答える。引数 message (必須) と history (任意, [{role, content}])。

Input Output Examples

Name	Type	Req	Description
history	array	—	直前までの会話履歴 (任意)
message	string	yes	ユーザーの質問・メッセージ

No output schema declared.

No examples provided.

create_house ~1,150

[EN] Build a new house (bim.json) from an address alone (geocoded, auto-named, climate-aware) or full elements; returns slug + edit_token + viewer/permit URLs + inline houki & structure verdicts. No auth (private by default, rate-limited). / 新しい物件 (bim.json) を作成する。name か address のどちらか必須 — 住所だけ渡せば geocode で座標を引き「<地名>の家」と自動命名して家が建つ (REINFOLIB_KEY 設定時は用途地域も実値注入)。elements (bim.json v1 要素配列) を渡すとそのまま保存、省略すると敷地寸法から住宅 BIM を自動生成。name/rooms に「薪ストーブ・土間・ロフト・カーポート・書斎・ピアノ・サウナ」等の言葉が入ると対応する要素 (煙突・炉台・はしご込み) を自動配置し、寒冷地住所ならトリプルガラス+付加断熱+雪止めに外皮を格上げ。「平屋」「2階建て」も階数に反映。slug と edit_token、viewer/json/permit URL と適用 features・site (座標/用途地域ソース) を返す。

Input Output Examples

Name	Type	Req	Description
address	string	—	所在地 (これだけでも家が建つ。geocode で座標解決・気候/積雪も住所から自動設定)
construction_jpy	integer	—	概算工事費円
elements	array	—	bim.json v1 要素配列。各要素 {id,cls,label,descr,shape:'box'\|'cylinder',x,y,z,w,d,h,rotation?} (mm)。省略可。
existing_year_built	integer	—	既存建物の建築年 (西暦)。1981年5月以前は旧耐震 (耐震診断推奨)、2006年以前(または未指定)はアスベスト事前調査を概算に自動計上する。project_type=renovation\|change_of_use のときのみ使う。
floors	integer	—	階数 (既定 1)
gross_m2	number	—	延床面積㎡
land_area_m2	number	—	敷地面積㎡
lot_d_m	number	—	奥行 m (簡易シェル生成に使用)
lot_w_m	number	—	間口 m (簡易シェル生成に使用)
name	string	—	物件名 (address を渡せば省略可 — 地名から自動命名)
private	boolean	—	true で物件一覧 (/property) に非掲載・直リンクのみ。既定 false=掲載。
project_type	string	—	[EN] 'new' (default) builds a from-scratch cost estimate. 'renovation'/'change_of_use' treat this as an EXISTING building being remodeled: foundation/frame/roof default to ¥0 (reused as-is) and only…
renovation_scope	array	—	改修対象の工種 code 配列 (demo/interior/fittings/electrical/plumbing/hvac/roof/exterior/frame/found/temp/pv)。project_type=renovation\|change_of_use のときのみ有効。省略時は典型的なフルリノベ (demo+内装+建具+電気+給排水+空調) を既定スコープとして使う。
renovation_scope_m2	number	—	実際に改修する範囲の面積㎡ (例: 3階建282㎡の建物のうち1階94㎡だけ改修するなら94)。省略時は gross_m2 (建物全体) を使う。project_type=renovation\|change_of_use のときのみ有効。
rooms	string	—	室構成サマリー
seismic_retrofit	boolean	—	true で耐震補強費 (建物全体延床×単価) を概算に含める。project_type=renovation\|change_of_use のときのみ使う。
structure	string	—	構造 (例: RC 打放しコンクリート)
zoning	string	—	用途地域 (例: 近隣商業地域)

No output schema declared.

No examples provided.

create_product ~456

[EN] Register a new catalog product SKU (needs Bearer API key; insert-only, no overwrite). / 建材カタログ (products) に新しい製品 SKU を登録する。サッシ/窓/断熱材/照明/設備/家具/ドア等。Authorization: Bearer <APIキー> (/console で発行) が必須。登録後は /catalog と search_catalog に即反映。既存 SKU の上書きは不可 (insert-only)。

Input Output Examples

Name	Type	Req	Description
brand	string	—	ブランド (例: YKK AP, LIXIL)
category	string	yes	カテゴリ (必須)。例: サッシ, 窓, 断熱材, 照明, 設備, 家具, ドア
description	string	—	製品説明
eta_value	number	—	日射熱取得率 η値
ifc_class	string	—	IFC クラス (省略時はカテゴリから推定。例: IFCWINDOW)
install_jpy	integer	—	施工費の目安円
jan_code	string	—	JAN コード
lead_time_days	integer	—	納期 (日)
mfr_code	string	—	メーカー型番
name	string	yes	製品名 (必須)
price_jpy	integer	—	メーカー希望小売税抜円
sku	string	yes	一意な SKU (英数・- _ . 、64字以内)。例: YKK-APW330-W
spec	object	—	追加スペック (任意の key/value オブジェクト)
stock_status	string	—	在庫 (in_stock/low_stock/order/made_to_order/discontinued。既定 in_stock)
tags	string	—	カンマ区切りタグ
u_value	number	—	熱貫流率 U値 W/m²K
url	string	—	メーカー公式ページ URL
warranty_years	integer	—	保証年数

No output schema declared.

No examples provided.

delete_zoning_rule ~101

[EN] Remove a zoning rule override (reverts to engine defaults) — admin only. / 用途地域規制ルールの上書きを削除し、エンジン既定値に戻す。管理者のみ。

Input Output Examples

Name	Type	Req	Description
admin_token	string	yes	管理者トークン (必須)
profile	string	—	法域 (既定 Japan)
zoning	string	yes	用途地域名

No output schema declared.

No examples provided.

get_build_plan ~121

[EN] Construction plan for a house: schedule (Gantt) + per-trade order packages (cost, lead, region-driven spec constraints, inspection checklist). / 物件の施工計画。工種(こうしゅ)別に工程(ガント) + 発注パッケージ(概算・工期・地域由来の仕様制約・検査チェックリスト) を返す。見積を工種に割って自動生成。

Input Output Examples

Name	Type	Req	Description
slug	string	yes	物件 slug

No output schema declared.

No examples provided.

get_houki_rules ~141

[EN] List the building-code checks the engine runs (law refs) + any active zoning-rule overrides; pass slug to also get that house's effective site conditions + houki verdict. / houki エンジンがチェックする法規項目 (根拠条文) と、登録済みの用途地域規制ルール上書き一覧を返す。slug を渡すとその物件の有効敷地条件 + 法規判定も同梱。

Input Output Examples

Name	Type	Req	Description
slug	string	—	任意。指定すると有効敷地条件 + houki 判定も返す

No output schema declared.

No examples provided.

get_house_bim ~102

[EN] Fetch a house's full bim.json v1 (project meta + elements) by slug. / slug を指定して物件の完全な bim.json v1 (project メタ + elements 配列) を取得。include_elements=false でメタのみ。

Input Output Examples

Name	Type	Req	Description
include_elements	boolean	—	elements を含めるか (既定 true)
slug	string	yes	物件 slug (list_houses 参照)

No output schema declared.

No examples provided.

get_product ~80

[EN] Get one product's full detail by SKU (price, U-value/η, stock, JAN, successor). / SKU を指定して 1 製品の詳細 (価格・性能値 U値/η値・在庫・JAN・後継品) を取得。

Input Output Examples

Name	Type	Req	Description
sku	string	yes	製品 SKU

No output schema declared.

No examples provided.

get_site_context ~126

[EN] Get a house's effective site conditions used by houki_check (zoning, road width, high/fire district, climate zone, latitude, neighbor setback, min lot area, shadow regulation). / houki_check が使う物件の有効敷地条件を取得 (用途地域・道路幅員・高度/防火地区・気候区分・緯度・隣地距離・敷地面積最低限度・日影規制)。

Input Output Examples

Name	Type	Req	Description
slug	string	yes	物件 slug (必須)

No output schema declared.

No examples provided.

houki_check ~94

[EN] Run the Japanese Building Standards Act check (coverage, FAR, slopes, daylight, ventilation) and return pass/fail. / 建築基準法チェック (建ぺい率・容積率・北側/道路斜線・採光・換気) を houki-engine で実行し合否を返す。

Input Output Examples

Name	Type	Req	Description
slug	string	yes	物件 slug

No output schema declared.

No examples provided.

list_contractors ~80

[EN] List registered contractors, optionally filtered by prefecture/trade. / 登録業者の一覧。都道府県・工種で絞り込み可。

Input Output Examples

Name	Type	Req	Description
prefecture	string	—	都道府県 (任意, 例: 北海道)
trade	string	—	工種 code (任意)

No output schema declared.

No examples provided.

list_houses ~152

[EN] List curated public houses (famous buildings, landmarks); set include_user=true for public user houses. / 運営 curated 公開物件 (有名建築・巨大ランドマーク・SOLUNA 等) の一覧。slug / 規模 / 要素数 / bim.json 充足率(%) を返す。ユーザー作成物件 (u-*) は既定では含まない (直リンクで個別取得は可)。include_user=true で公開ユーザー物件も含める。

Input Output Examples

Name	Type	Req	Description
include_user	boolean	—	公開 (private=false) のユーザー作成物件も含める (既定 false)

No output schema declared.

No examples provided.

list_incomplete_addresses ~130

[EN] List public houses whose address is incomplete (missing town name / placeholder), so they can be corrected — admin only. Fixing them lets zoning be derived from coordinates. / 住所が不完全 (町名欠落・プレースホルダ) な公開物件を一覧する。管理者のみ。直すと座標から用途地域を判定でき投入できる。

Input Output Examples

Name	Type	Req	Description
admin_token	string	yes	管理者トークン (必須)
limit	integer	—	返す最大件数 (既定200・最大2000)

No output schema declared.

No examples provided.

list_mine ~58

[EN] List products you registered (needs Bearer API key). / 自分 (API キーのアカウント) が登録した製品の一覧を返す。Authorization: Bearer <APIキー> 必須。

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

match_contractors ~153

[EN] Match contractors to a house by trade × location (prefecture or lat/lng+radius). One house's order naturally splits across local builders. / 工種 × 場所 (都道府県 or 緯度経度+対応半径) で業者をマッチ。trade 省略で全工種を一括。1棟の発注が地域の複数業者に自然に分かれる。

Input Output Examples

Name	Type	Req	Description
slug	string	yes	物件 slug
trade	string	—	工種 code (任意): temp/found/frame/roof/exterior/fittings/electrical/plumbing/hvac/interior/pv/inspection

No output schema declared.

No examples provided.

material_quote ~138

[EN] Catalog-priced cost estimate: BOM, total, ¥/m², lead times and critical path from the BIM takeoff. / カタログ連携の概算見積もり。BIM 要素 takeoff × 建材カタログ実価格 (窓/ドア/設備) + 原単位 (躯体/仕上げ) で BOM・総額・㎡単価を算出し、各資材の納期 (lead_time_days) と在庫、クリティカルパス納期も返す。

Input Output Examples

Name	Type	Req	Description
slug	string	yes	物件 slug

No output schema declared.

No examples provided.

place_in_house ~310

[EN] Place a *live reference* to another service's catalog into a house (needs edit_token) — not a copy. source 'mu' refs a wearmu.com brand slug (goods made by MU); source 'device' refs a device.house room key (word-driven hardware). The viewer / GET /api/projects/<slug>/furnishings resolves these at view time so stock is always live and never duplicated. / 家に MU(wearmu.com の作ったもの) や device.house(言葉で動く実機) の在庫を *参照* で置く。edit_token 必須。複製せずポインタだけ持ち、表示時に各サービスをライブ解決する(常に最新・売れたら消える)。source='mu' は brand slug(例 biruwa)、source='device' は部屋キー(entrance/living/bedroom/kitchen/outdoor/any)。

Input Output Examples

Name	Type	Req	Description
edit_token	string	yes	create_house が返した edit_token (必須)
ref	string	yes	mu: brand slug (例 biruwa, mcp) / device: 部屋キー (living 等)
room	string	—	家の中の置き場所 (表示用・任意)
slug	string	yes	物件 slug (必須)
source	string	yes	'mu'=wearmu.com / 'device'=device.house

No output schema declared.

No examples provided.

place_order ~122

[EN] Create a DRAFT purchase order for one trade of a house to a contractor (does NOT send anything — human sends later). / 物件の1工種を業者へ発注 (ドラフト作成のみ・⚠送信はしない)。spec/検査リストを同梱。

Input Output Examples

Name	Type	Req	Description
contractor_id	integer	yes	match_contractors / list_contractors の contractor_id
slug	string	yes	物件 slug
trade	string	yes	工種 code (get_build_plan の phases.trade)

No output schema declared.

No examples provided.

register_contractor ~252

[EN] Register a contractor (supply side, self-serve). Requires Bearer API key. trades = trade codes or 'all'; location via prefectures and/or lat/lng+service_radius_km. / 業者を登録 (供給側セルフサーブ・API キー必須)。trades=工種 code 配列か 'all'、場所は prefectures か lat/lng+service_radius_km。

Input Output Examples

Name	Type	Req	Description
contact	string	—	連絡先 (メール等)
fulfillment	string	—	labor / kit / both (既定 labor)
lat	number	—	拠点緯度 (任意)
lead_time_days	integer	—	標準納期日数 (任意)
lng	number	—	拠点経度 (任意)
name	string	yes	業者名 (必須)
prefectures	array	—	対応都道府県
service_radius_km	number	—	対応半径 km (任意)
trades	array	—	対応工種 code の配列、または 'all'

No output schema declared.

No examples provided.

retire_product ~95

[EN] Retire (discontinue) a product you created (needs Bearer API key; soft, not hard delete). / 自分が登録した製品を取り下げる (生産終了化。ハード削除はしない)。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は不可。

Input Output Examples

Name	Type	Req	Description
sku	string	yes	取り下げる SKU (必須)

No output schema declared.

No examples provided.

search_catalog ~165

[EN] Search the building-materials catalog (3,900+ SKUs) by keyword/brand/category. / bim.house の建材・設備カタログ (3,900+ SKU) を検索。窓/断熱/設備/家具などを brand・category・キーワードで絞り込む。

Input Output Examples

Name	Type	Req	Description
brand	string	—	ブランド完全一致 (例: YKK AP, LIXIL)
category	string	—	カテゴリ完全一致 (例: 窓, 断熱材, 設備)
limit	integer	—	最大件数 (1-50, 既定 20)
q	string	—	キーワード (商品名・型番・JAN・タグを部分一致)

No output schema declared.

No examples provided.

set_forkable ~136

[EN] Allow or forbid others from forking (copying) a house (needs edit_token). / 他者がこの物件をフォーク (コピー) できるかを切り替える。edit_token が必要。forkable=false で他者のコピー作成を禁止 (既定は全て可)。

Input Output Examples

Name	Type	Req	Description
edit_token	string	yes	create_house が返した edit_token (必須)
forkable	boolean	yes	true=フォーク可 (既定) / false=フォーク不可
slug	string	yes	物件 slug (必須)

No output schema declared.

No examples provided.

set_site_context ~413

[EN] Override a house's site conditions for houki_check (needs edit_token). Only provided fields are updated; returns the re-run houki verdict. Fixes false NGs from assumed defaults (e.g. set the real road width). / 物件の敷地条件を上書きして houki_check に反映する。edit_token 認証が必要。指定したフィールドのみ更新し、再判定した houki を返す。既定値による誤 NG (例: 前面道路幅員) を実値で是正できる。

Input Output Examples

Name	Type	Req	Description
climate_zone	integer	—	省エネ地域区分 1-8
edit_token	string	yes	create_house が返した edit_token (必須)
fire_district	string	—	防火地域 / 準防火地域
high_district	string	—	高度地区 (例: 第1種高度地区)
latitude	number	—	緯度 (日影計算用)
min_lot_area_m2	number	—	敷地面積の最低限度 (㎡)
neighbor_setback_m	number	—	隣地境界距離 (m) — 隣地斜線
north_setback_m	number	—	北側隣地距離 (m)
road_width_m	number	—	前面道路幅員 (m) — 道路斜線・容積率低減に効く
shadow_regulation	object	—	日影規制の条例値 {measurement_height_m, limit_5m_h, limit_10m_h, start_hour, end_hour}。省略時は用途地域+規模で自動判定
slug	string	yes	物件 slug (必須)
zoning	string	—	用途地域 (例: 第一種住居地域)

No output schema declared.

No examples provided.

set_visibility ~136

[EN] Toggle a house's public listing on/off (needs edit_token). / 物件の掲載/非掲載を切り替える。edit_token (create_house の返り値) が必要。private=true で物件一覧から非掲載 (直リンクは残る)。進化ループの低スコア物件の淘汰などに使う。

Input Output Examples

Name	Type	Req	Description
edit_token	string	yes	create_house が返した edit_token (必須)
private	boolean	yes	true=非掲載 / false=掲載
slug	string	yes	物件 slug (必須)

No output schema declared.

No examples provided.

update_house ~428

[EN] Update an existing house's bim.json (needs edit_token): swap elements or patch project meta; returns a re-run houki verdict. Versioned each save. / 既存物件の bim.json を更新する。edit_token (create_house の返り値) が必要。elements (bim.json v1 要素配列) を渡すと差し替え、project (object) でメタ (name/construction_jpy/proposed_gross_m2 等) のみ更新も可。get_house_bim で現状を取得 → 編集 → update_house → 返り値の houki (法規再判定) を確認、のループで自分の LLM だけで設計改善が完結する。保存ごとに履歴 (bim_versions) が残る。

Input Output Examples

Name	Type	Req	Description
edit_token	string	yes	create_house が返した edit_token (必須)
elements	array	—	bim.json v1 要素配列 (全置換)。省略時は既存要素を維持
elements_json	string	—	elements の JSON 文字列版 (strict-schema クライアント用)
note	string	—	変更メモ (履歴に残る・500字まで)
project	object	—	メタ更新 (name / construction_jpy / proposed_gross_m2 / proposed_floors / proposed_structure / proposed_rooms / project_type['new'\|'renovation'\|'change_of_use'] / renovation_scope[配列] / renovation_scope_…
slug	string	yes	物件 slug (必須)

No output schema declared.

No examples provided.

update_product ~237

[EN] Update fields of a product you created (needs Bearer API key; your SKUs only). / 自分が create_product で登録した製品のフィールドを更新する。Authorization: Bearer <APIキー> 必須。他者/公式 SKU は更新不可。指定したフィールドのみ上書き。

Input Output Examples

Name	Type	Req	Description
brand	string	—	—
category	string	—	—
description	string	—	—
eta_value	number	—	—
install_jpy	integer	—	—
jan_code	string	—	—
lead_time_days	integer	—	—
mfr_code	string	—	—
name	string	—	—
price_jpy	integer	—	—
sku	string	yes	更新対象の SKU (必須)
spec	object	—	追加スペック (上書き)
stock_status	string	—	in_stock/low_stock/order/made_to_order/discontinued
tags	string	—	—
u_value	number	—	—
url	string	—	—
warranty_years	integer	—	—

No output schema declared.

No examples provided.

upsert_zoning_rule ~356

[EN] Add/update a zoning regulation rule (coverage/FAR/slope/height limits) — admin only (admin_token). Applies to all houses matching (profile, zoning). / 用途地域の規制ルール (建ぺい/容積/斜線/高さ等) を追加・更新する。管理者のみ (admin_token)。(profile, zoning) に一致する全物件の houki に反映。

Input Output Examples

Name	Type	Req	Description
absolute_height_limit_mm	integer	—	絶対高さ制限 mm (null=なし)
admin_token	string	yes	管理者トークン (必須)
coverage_pct	number	—	建ぺい率上限 %
far_pct	number	—	指定容積率 %
far_road_coefficient	number	—	前面道路幅員容積率低減係数 (住居0.4/他0.6)
north_slope_start_mm	integer	—	北側斜線起点高 mm (null=適用外)
profile	string	—	法域 (既定 Japan)。例: Japan / SpainCatalonia / UsaHawaii / France
road_applicable_distance_m	number	—	道路斜線適用距離 (m)
road_slope_d	integer	—	道路斜線勾配分母 (1.25=4)
road_slope_n	integer	—	道路斜線勾配分子 (1.25=5)
zoning	string	yes	用途地域名 (部分一致キー。例: 第一種住居)

No output schema declared.

No examples provided.

whoami ~83

[EN] Verify API-key auth: returns your account email if a valid Bearer key is sent. / API キー認証の確認。Authorization: Bearer <APIキー> (/console で発行) を付けると認証済みアカウントの email を返す。Web/CLI どちらからでも使える。

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	58
27 Jul	59
28 Jul	59
29 Jul	60
30 Jul	59
31 Jul	61
1 Aug	61
2 Aug	61
3 Aug	62