技能潮 SkillTide 提交收录
官方说明开源项目7 天前
chaoz23/king-county-permit-status

chaoz23/king-county-permit-status

Look up building permit status for King County, WA — searches across city + county jurisdictions. Agent-friendly: pipe, schema, tool.json.
在 GitHub 查看 ↗直链 · 无中转页
★ 数取值
1 ★ · chaoz23/king-county-permit-status · 取自该仓库的 GitHub 页面 · (2026-10-16 20:00:20 核对)
来源明细
从该仓库的 GitHub 页面直接读取 · 条目类型:开源项目
收录与活跃
收录于 2026-10-10 · 最近见到 2026-10-10 · 共见到 3 次 · 被 1 个来源列出
评分构成
综合分 103 · 1 ★ · 1 个来源 · repo
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: 开源项目。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 chaoz23/king-county-permit-status;我们收录于 2026-10-10;最近见到 2026-10-10。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

King County Permit Status

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Look up building permit history and status across King County, WA jurisdictions — county-level permits (septic, critical areas, grading) and city-level permits (building, mechanical, electrical) can all apply to the same address. Coverage is live where a jurisdiction offers an open permit feed, and falls back to the correct municipal portal link everywhere else.
**Coverage today:** 🟢 **20/39** cities live (status + history) · 🟠 **19/39** indexed (issued-permit history from the King County Assessor; current status needs the city portal, which next_step names) · plus unincorporated King County. See the coverage scorecard below for the per-city breakdown.
Hosted API + MCP (no install)
The same lookup is served read-only, no auth, from permits-api.secondlandings.ai
(server.py, zero dependencies; see deploy/README.md):
| | |
|---|---|
| **MCP** (Streamable HTTP) | POST https://permits-api.secondlandings.ai/mcp — tool king_county_permit_status, arg query |
| **REST** | GET https://permits-api.secondlandings.ai/api/lookup?q=1817+Morris+Ave+S,+Renton+WA — optional limit, since=YYYY-MM-DD, types=electrical,mechanical |
| **Vendor map** | /vendor-map (and /vendor-map.json) — which permitting system each of the 39 cities runs, how it is queried or why it can't be, electrical authority, per-type routing; generated from the adapter config (scripts/gen_vendor_map.py, also in docs/vendor-map.md) |
| **OpenAPI 3.1** (typed) | /openapi.json · agent orientation /llms.txt · CLI definition /tool.json · /healthz |
Results are live; the server caches each query for 15 minutes and rate-limits
per client (30/min) to protect the municipal portals. **Known hosted-only gap:** Tyler's
hosted Civic Access (Redmond) returns 403 to datacenter IPs, so from the hosted endpoint a
Redmond lookup carries the Assessor index plus a next_step with reason: source_blocked
instead of live Redmond records; run lookup.py locally for those. Every other source
answers from the droplet. Run it yourself with
python3 server.py or docker compose up — server.json is the MCP Registry manifest.
Parcel-number searches query every supported MyBuildingPermit and live city
portal because a bare parcel number does not identify its city jurisdiction.
Address searches are routed by **geometry, not the mailing city**: the address
is geocoded with King County's four-county locator and the point is tested
against the city-limits polygons. A "Kent, WA" address that sits in
unincorporated King County is searched as county, not Kent; an address with no
city in it is routed correctly instead of fanning out to every jurisdiction; and
Pierce-side addresses of Milton/Pacific/Auburn get a pierce: parcel id. The
mailing city is only used when geocoding fails (jurisdiction.basis says which).
What you get
| Field | Description |
|---|---|
| action | found (permits returned), none (no matches), refine (connection issue) |
| permit_count | Unique permits found before any filter (= summary.total) |
| summary | **Answer from this first.** Computed over every permit matching since/types, not just the returned rows: total, matched, returned, truncated, open, closed, status_unknown, by_type, by_status, by_year, years [oldest, newest], latest |
| permits | Up to limit records (default **50**), newest first — a 356-permit commercial parcel is ~56k tokens unshaped; the summary carries the whole picture |
| filters | The limit / since / types that produced this response |
| searched | Which jurisdictions were searched |
| separate_portal | If the city has an unsupported portal: city name + URL + prose note |
| next_step | Structured twin of separate_portal for agents: kind: manual_portal_search, reason (no_feed / electrical_only / parcel_resolution_failed / source_incomplete / source_blocked — the city's live system refused this client with 403), portal_url (the portal's actual search page when known — PermitTrax, LAMA, OpenGov, Kent), vendor, search_by (inputs that page accepts; empty when login-gated), query, query_type, covers_electrical, hint |
| errors | Source errors when a search is incomplete; may accompany permits from successful sources |
| trust_level | live (every applicable source answered), partial (a source errored or hit its result cap — see errors), fallback (nothing searchable). A city that needs a manual portal visit (next_step) is a scope fact, not distrust, and no longer lowers this |
来源
github · https://github.com/chaoz23/king-county-permit-status
按领域浏览
开源项目
Traction
1 ★
收录于
7 天前

更多开源项目

查看开源项目全部 731 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引