parseapi-mcp 1.12.4 → 1.14.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +58 -31
- package/dist/{chunk-CPJ3VR6E.js → chunk-W2HQKIWP.js} +324 -487
- package/dist/http.js +1 -1
- package/dist/registry.js +1 -1
- package/dist/stdio.js +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -1,11 +1,15 @@
|
|
|
1
1
|
# parseapi-mcp
|
|
2
2
|
|
|
3
|
+
This package selects HTTP API `2.2.0`. Its SDK dependency is pinned to `1.15.0`. Use the `api22` npm tag to opt in; the `latest` and `api21` tags keep their existing contracts.
|
|
4
|
+
|
|
3
5
|
Official ParseAPI MCP server. Look up places, addresses, companies, email, phone, weather, timezones, dates and more from your AI agent.
|
|
4
6
|
|
|
5
7
|
## Hosted
|
|
6
8
|
|
|
7
9
|
One URL, nothing to install. Add the server and sign in once in the browser. Free plan works.
|
|
8
10
|
|
|
11
|
+
Installing a local package does not update the shared hosted service. Hosted activation is reviewed separately.
|
|
12
|
+
|
|
9
13
|
```json
|
|
10
14
|
{
|
|
11
15
|
"mcpServers": {
|
|
@@ -38,7 +42,7 @@ CI and headless setups skip the browser with a key from [parseapi.com](https://p
|
|
|
38
42
|
"mcpServers": {
|
|
39
43
|
"parseAPI": {
|
|
40
44
|
"command": "npx",
|
|
41
|
-
"args": ["-y", "parseapi-mcp"],
|
|
45
|
+
"args": ["-y", "parseapi-mcp@api22"],
|
|
42
46
|
"env": { "PARSEAPI_KEY": "your-api-key" }
|
|
43
47
|
}
|
|
44
48
|
}
|
|
@@ -47,7 +51,7 @@ CI and headless setups skip the browser with a key from [parseapi.com](https://p
|
|
|
47
51
|
|
|
48
52
|
## API versions
|
|
49
53
|
|
|
50
|
-
Since version 1.0.0, the package explicitly selects the API contract supported by this MCP package.
|
|
54
|
+
Since version 1.0.0, the package explicitly selects the API contract supported by this MCP package. This version sends `X-API-Version: 2.2.0` on every API tool request, matching its tool descriptions and SDK response types. The contract is fixed for local stdio and HTTP servers running this package, including retries. The shared hosted service remains on its existing API 2.0 release. Your key, OAuth identity and team's saved default stay the same. The API still accepts earlier `Parse-Version` request pins.
|
|
51
55
|
|
|
52
56
|
For local stdio, pin the MCP package version in your application configuration and test the new release before deploying it. A future major MCP upgrade can select a newer API contract. There is no version argument to add to individual tool calls. The hosted service uses the API contract supported by its deployed MCP release.
|
|
53
57
|
|
|
@@ -56,21 +60,22 @@ MCP packages older than 1.0.0 keep their existing behavior and use the team's de
|
|
|
56
60
|
## ISO identifiers
|
|
57
61
|
|
|
58
62
|
Country uses `iso_alpha3` and `iso_numeric`, State uses the full
|
|
59
|
-
`
|
|
60
|
-
uses `iso_numeric`.
|
|
63
|
+
`iso_code` such as `US-CA`, Language uses `iso_alpha3`, and Currency
|
|
64
|
+
uses `iso_numeric`. County lookup and State county-list items include nullable
|
|
65
|
+
`iso_code` for an exact recorded ISO 3166-2 assignment; unsupported assignments stay null. Primary `country`, `state`, `language` and `currency` codes
|
|
61
66
|
keep their meaning. Results retain the selected API contract's exact keys,
|
|
62
67
|
values, nulls and nesting. Earlier server contracts retain their earlier ISO
|
|
63
68
|
spellings. Use the existing lookup methods for each resource.
|
|
64
69
|
|
|
65
70
|
## Tools
|
|
66
71
|
|
|
67
|
-
Full mode provides
|
|
72
|
+
Full mode provides 65 local lookup tools and 64 hosted lookup tools, plus `discover` for local metadata and `preflight` for authenticated task estimates. `ip_self` is local only. `time` returns current local time and Unix seconds. It accepts a timezone or coordinates and defaults to UTC when both are omitted. `date` parses the supplied date, or returns today in UTC when omitted. Existing `timezone` calls remain supported with their original arguments. Every lookup returns the JSON the API serves.
|
|
68
73
|
|
|
69
|
-
Tools follow the lookup names: `country_states`, `city_search`, `postal_nearby`, `address`, `address_search`, `company`, `company_id`, `company_search`, `
|
|
74
|
+
Tools follow the lookup names: `country_states`, `city_search`, `postal_nearby`, `address`, `address_search`, `company`, `company_id`, `company_search`, `email`, `card`, `industry`, `industry_search`, `dns`, `asn`, `currency_rate`, and the rest. Text searches take `query`. Company directory search supports one name/domain/ticker/identifier selector or country/exact-SIC discovery filters.
|
|
70
75
|
|
|
71
76
|
The existing `naics` and `naics_search` tools remain available as compatibility names for Industry.
|
|
72
77
|
|
|
73
|
-
Industry paid deep records include classification `
|
|
78
|
+
Industry paid deep records include classification `exclusions`, each with a description and linked codes. Generic exclusions can have no linked codes. Omitted or null exclusions in older responses remain unknown. Search results also include `match`: the matched `field` (`name`, `term` or `naics`) and `text`, plus `corrections` with `from` and `to` tokens for typo fallback. Corrections are empty for exact, plural and prefix matches. Direct code lookups omit `match`. Older responses may omit it.
|
|
74
79
|
|
|
75
80
|
Example tool arguments:
|
|
76
81
|
|
|
@@ -87,7 +92,6 @@ Example tool arguments:
|
|
|
87
92
|
| `address_search` | `{"query":"1600 Pennsylvania","country":"US","city":"Washington","state":"DC"}` |
|
|
88
93
|
| `company_search` | `{"query":"Cloudflare","country":"US"}` |
|
|
89
94
|
| `company_id` | `{"id":"co_xw3f22es6cjq","deep":true}` |
|
|
90
|
-
| `company_coverage` | `{}` |
|
|
91
95
|
| `time` | `{}` (UTC now) |
|
|
92
96
|
| `time` | `{"timezone":"America/New_York","at":"2026-09-05T09:00:00","to":"Asia/Tokyo"}` |
|
|
93
97
|
| `time` | `{"lat":40.71,"lon":-74.01}` |
|
|
@@ -96,18 +100,16 @@ Example tool arguments:
|
|
|
96
100
|
| `time` | `{"timezone":"America/New_York","at":"2026-11-01T01:30:00","to":"UTC","disambiguation":"later"}` |
|
|
97
101
|
| `date` | `{"date":"03/04/2026","format":"dmy"}` |
|
|
98
102
|
| `elevation` | `{"lat":35.2271,"lon":-80.8431}` |
|
|
99
|
-
| `elevation` | `{"points":"
|
|
100
|
-
| `elevation` | `{"path":"
|
|
103
|
+
| `elevation` | `{"points":"35.2271,-80.8431|40.7128,-74.006"}` |
|
|
104
|
+
| `elevation` | `{"path":"35.2271,-80.8431|35.5951,-82.5515","samples":100}` |
|
|
101
105
|
|
|
102
|
-
Time uses `disambiguation` only for offsetless `at` with `to` or `targets`. The default `compatible` selects the earlier repeated time or advances a skipped time. `earlier` and `later` choose the respective instant. `reject` returns `ambiguous_time` for repeated times and `nonexistent_time` for skipped times. Prefer it for user-entered appointments. Ask for an explicit offset or the user's choice before retrying a rejected local time. Explicit offsets select an instant directly. Time
|
|
106
|
+
Time uses `disambiguation` only for offsetless `at` with `to` or `targets`. The default `compatible` selects the earlier repeated time or advances a skipped time. `earlier` and `later` choose the respective instant. `reject` returns `ambiguous_time` for repeated times and `nonexistent_time` for skipped times. Prefer it for user-entered appointments. Ask for an explicit offset or the user's choice before retrying a rejected local time. Explicit offsets select an instant directly. Time deep is available in the same pooled request on every plan.
|
|
103
107
|
|
|
104
|
-
Time Deep includes
|
|
108
|
+
Time Deep includes `resolution` when a source wall time needs interpretation. Resolution reports `kind` (`unique`, `overlap` or `gap`), `policy`, signed `adjustment_seconds`, and chronological `alternatives` with exact local `at`, Unix seconds and UTC offset. Unique wall times have no alternatives. Explicit-offset timestamps, current clocks, non-conversion lookups and unknown source zones omit resolution.
|
|
105
109
|
|
|
106
|
-
Elevation accepts exactly one of `lat` and `lon`, `points`, or `path` with `samples`. A point list supports up to 512
|
|
110
|
+
Elevation accepts exactly one of `lat` and `lon`, `points`, or `path` with `samples`. A point list supports up to 512 coordinates as `lat,lon` pairs separated by `|`, or `enc:` followed by a Google encoded polyline, with at most 12000 characters. The `points` response array preserves input order and duplicate coordinates. Each sample includes meters, feet and grid resolution in meters. Unknown samples stay null. A list uses one pooled request, with JSON POST selected automatically for long URLs.
|
|
107
111
|
|
|
108
|
-
A path uses the same string formats with 2-512 vertices and a required integer `samples` count from 2 to 512. The response `points` include both endpoints, spaced uniformly by cumulative great-circle distance along the path. Each segment follows the shortest arc. A segment with antipodal endpoints is rejected because it does not define a unique arc.
|
|
109
|
-
|
|
110
|
-
Each local batch is limited to 25 km between any two coordinates and 12 distinct terrain files in total across the fine grid and all possible global fallback files. For paths, both the supplied vertices and generated samples must fit the 25 km span. The terrain file budget applies to the sampled coordinates. This is a span limit, not a limit on cumulative path length. Send longer or more spread-out routes in shorter sections. An over-limit batch returns HTTP 400. MCP does not silently split or discard coordinates.
|
|
112
|
+
A path uses the same string formats with 2-512 vertices and a required integer `samples` count from 2 to 512. The response `points` include both endpoints, spaced uniformly by cumulative great-circle distance along the path. Each segment follows the shortest arc. A segment with antipodal endpoints is rejected because it does not define a unique arc. A path uses one pooled request. `samples` is invalid with a single coordinate or a point list.
|
|
111
113
|
|
|
112
114
|
Australian `postal` lookup returns core `localities` with suburb choices (`city`, `state`, `state_name`). Null or an omitted field means unknown, while `[]` means the reviewed reference has no eligible choices. A single choice can coexist with `city: null`. Ask for the user's suburb choice and preserve manual entry. These are geographic choices, not mailing-address verification. AU Postal tool results include a separate source notice after the JSON. [G-NAF source, adaptations and licence](https://parseapi.com/legal/attribution#postal-au).
|
|
113
115
|
|
|
@@ -121,8 +123,7 @@ filters and `limit` for another page. Directory Deep adds detail to each company
|
|
|
121
123
|
pooled request. Existing accounts retain their current Deep access.
|
|
122
124
|
Selected website descriptions, logos, socials and founding claims are returned
|
|
123
125
|
where available. Logo URLs are returned without fetching images. Directory
|
|
124
|
-
tools do not accept `lang`.
|
|
125
|
-
and empty listings do not establish private ownership. The `company` tool
|
|
126
|
+
tools do not accept `lang`. Empty listings do not establish private ownership. The `company` tool
|
|
126
127
|
remains listed for compatibility, but national-number lookups are retired on
|
|
127
128
|
the public API. Use `company_search` and `company_id` for maintained public-company records.
|
|
128
129
|
|
|
@@ -163,7 +164,7 @@ The estimate allows up to three attempts per ordinary lookup and one per Email D
|
|
|
163
164
|
For a compact tool catalog, set `PARSEAPI_MCP_MODE=compact` on the MCP process:
|
|
164
165
|
|
|
165
166
|
```bash
|
|
166
|
-
PARSEAPI_MCP_MODE=compact npx -y parseapi-mcp@
|
|
167
|
+
PARSEAPI_MCP_MODE=compact npx -y parseapi-mcp@api22
|
|
167
168
|
```
|
|
168
169
|
|
|
169
170
|
Set `PARSEAPI_KEY` in the process environment for lookups. Compact mode advertises three tools, `discover`, `preflight` and `lookup`. After discovering an operation, pass its exact name and arguments:
|
|
@@ -174,7 +175,7 @@ Set `PARSEAPI_KEY` in the process environment for lookups. Compact mode advertis
|
|
|
174
175
|
|
|
175
176
|
`lookup` uses the same input validation, cancellation, version pin, SDK and billing behavior as the named tools. It executes one operation and cannot run arbitrary code or request arbitrary URLs. Full mode is the default and preserves existing named lookup calls. The same process setting supports self-hosted HTTP.
|
|
176
177
|
|
|
177
|
-
The policy source is the API's `src/route/help/agent-catalog.json`.
|
|
178
|
+
The policy source is the API's `src/route/help/agent-catalog.json`. Mini guides contain ordinary HTTP instructions; MCP keeps the tool policies and schemas. Frozen API 1.0.0 help stays unchanged. In a ParseAPI workspace, run `npm run catalog:sync` to copy a reviewed policy change, then `npm run catalog:check`. An independent checkout can pass `-- --source /path/to/api`. Package builds use the checked-in copy and do not need the API checkout or a network request.
|
|
178
179
|
|
|
179
180
|
## Bulk files
|
|
180
181
|
|
|
@@ -232,11 +233,13 @@ MIT licensed.
|
|
|
232
233
|
|
|
233
234
|
## Optional detail
|
|
234
235
|
|
|
235
|
-
Country Core contains the everyday reference: `name`, `name_full`, `name_local`, demonym, `iso_alpha3` and `iso_numeric` country identifiers, continent, region and subregion, currency, calling code, `flag`, language and timezone codes, borders, bloc memberships and `capital: { name, latitude, longitude }`. Paid Deep adds specialist detail, including population, total area and national statistics. `gdp_usd` and `gdp_per_capita_usd` are current US dollars; `population_growth_percent`, `urban_population_percent` and `internet_users_percent` use a 0–100 percent scale (growth can be negative or exceed 100). GDP per person and these three percentages round once to two decimals in the API response. `elevation_average` is average terrain elevation in meters; `lowest_point.elevation` and `highest_point.elevation` keep their point-specific meaning. Unknown stays null and a known zero stays zero. Country tax references are grouped once as `
|
|
236
|
+
Country Core contains the everyday reference: `name`, `name_full`, `name_local`, demonym, `iso_alpha3` and `iso_numeric` country identifiers, continent, region and subregion, currency, calling code, `flag`, language and timezone codes, borders, bloc memberships and `capital: { name, latitude, longitude }`. Paid Deep adds specialist detail, including population, total area and national statistics. `gdp_usd` and `gdp_per_capita_usd` are current US dollars; `population_growth_percent`, `urban_population_percent` and `internet_users_percent` use a 0–100 percent scale (growth can be negative or exceed 100). GDP per person and these three percentages round once to two decimals in the API response. `elevation_average` is average terrain elevation in meters; `lowest_point.elevation` and `highest_point.elevation` keep their point-specific meaning. Unknown stays null and a known zero stays zero. Country tax references are grouped once as `tax: { name, rate }`; the rate remains a percentage. Read capital from the Core object and read optional tax references from `tax.name` and `tax.rate` on that same resource.
|
|
237
|
+
|
|
238
|
+
Country includes `postal_format` and `postal_regex` on every plan without requesting Deep. `postal_format` is an input hint based on one example, not a complete mask. `postal_regex` checks syntax, not whether a code exists or receives mail. Unavailable values are null.
|
|
236
239
|
|
|
237
|
-
|
|
240
|
+
Make the ordinary tool call. API 2.1 paid plans include their profile detail automatically; Free returns the complete everyday answer. Existing `deep` inputs remain supported for compatibility. Time, Date, Emoji, Phone, Point and Card offer optional detail on paid plans; existing accounts retain their current Deep access. Language includes every reference fact in Core, and Deep adds no fields. Geographic profiles, Name evidence and NAICS definitions require a paid plan. Carrier and HLR detail stays inside the same metered core unit, including Free allowance units, with no additional charge or second gate.
|
|
238
241
|
|
|
239
|
-
Search detail belongs to each returned entity. Time conversion puts target display detail in `to
|
|
242
|
+
Search detail belongs to each returned entity. Time conversion puts target display detail in `to`; only the source returns `next_dst`. Name core parsing needs no dictionary lookup. Paid Name deep also returns flat `short`, `directory`, and `initials`. Optional `name_locale` selects CLDR formatting rules, defaults to `en`, and leaves parsing and gender context unchanged. Unavailable formatting is null, and older responses may omit these fields. Country, State and Postal tax references are in a root `tax` object when the optional detail is available.
|
|
240
243
|
|
|
241
244
|
## Stack API
|
|
242
245
|
|
|
@@ -250,7 +253,7 @@ Stack checks static homepage HTML and response headers. It returns the checked U
|
|
|
250
253
|
|
|
251
254
|
`cms`, `servers`, `frameworks`, `ecommerce`, `analytics`, `chat`, `payments` and `hosting` are arrays because a site can use several technologies in each category. Each entry contains `technology`, `name` and nullable `version`. Technology codes are open strings. A successful check uses empty arrays for categories with no matches. When no HTML page could be checked, `checked_at` and all categories are null. Unknown or conflicting versions are null. Detections describe the checked homepage.
|
|
252
255
|
|
|
253
|
-
Successful checks may be reused for up to 24 hours. `pretty` optionally formats the wire JSON. Stack uses your plan's request allowance and API version 2.
|
|
256
|
+
Successful checks may be reused for up to 24 hours. `pretty` optionally formats the wire JSON. Stack uses your plan's request allowance and API version 2.1.0 selected by this client.
|
|
254
257
|
|
|
255
258
|
The `stack` tool allows 35 seconds per attempt for a first check. MCP cancellation still aborts the request.
|
|
256
259
|
|
|
@@ -277,14 +280,14 @@ GET /emoji/rocket
|
|
|
277
280
|
{"emoji":"🚀","name":"Rocket","shortcodes":[":rocket:","rocket"],"category":"Travel & Places"}
|
|
278
281
|
```
|
|
279
282
|
|
|
280
|
-
|
|
283
|
+
Paid plans include Unicode facts, keywords, tone families and available artwork automatically in API 2.1.
|
|
281
284
|
Core values stay unchanged. Text parsing returns `emojis` with UTF-16 `positions`;
|
|
282
285
|
conversion returns `text` and unresolved tokens with positions and reasons.
|
|
283
286
|
|
|
284
287
|
The compact JSON catalog contains offline identity, qualification-form and
|
|
285
|
-
shortcode indexes.
|
|
286
|
-
|
|
287
|
-
|
|
288
|
+
shortcode indexes. Use `lang` for localized names and keywords. Metadata and
|
|
289
|
+
shared source notices are included in the catalog. Read an individual emoji
|
|
290
|
+
with Deep for its artwork links. Artwork supports Google Noto, Twemoji
|
|
288
291
|
and OpenMoji, with real SVG/PNG availability and immutable first-party URLs.
|
|
289
292
|
A device's emoji font remains the ordinary display.
|
|
290
293
|
|
|
@@ -294,13 +297,13 @@ backend are published. Existing lookup and search contracts are preserved.
|
|
|
294
297
|
|
|
295
298
|
## Canonical City operations
|
|
296
299
|
|
|
297
|
-
Classic lookup, search, nearest and named-nearby methods retain their default envelopes and required-field models. Browse and coordinate-nearby
|
|
300
|
+
Classic lookup, search, nearest and named-nearby methods retain their default envelopes and required-field models. Browse uses `cities` and coordinate-nearby uses `nearby`, with nullable `next_cursor` (camelCase properties in Swift/Kotlin). Keep all query options unchanged when continuing a page; no client fetches pages automatically.
|
|
298
301
|
|
|
299
302
|
```json
|
|
300
303
|
{"operation":"city_search","arguments":{"query":"Viena","format":"list","match":"fuzzy","max_distance":1}}
|
|
301
304
|
```
|
|
302
305
|
|
|
303
|
-
|
|
306
|
+
Each route retains its default response. Country inclusion/exclusion sets, timezone sets, inclusive population and meter-elevation bounds, stored-center `bbox` and signed multi-key sorting are available for collections. Unknown numeric facts do not match range filters.
|
|
304
307
|
|
|
305
308
|
Search defaults to prefix matching. Exact and fuzzy matching are explicit; fuzzy accepts maximum edit distance 1 or 2 and returns `match` evidence (`type`, `source`, `value`, `language`, `edit_distance`). Review a fuzzy choice before storing its ID.
|
|
306
309
|
|
|
@@ -316,6 +319,8 @@ Coverage by country and available fields is described at https://parseapi.com/ci
|
|
|
316
319
|
|
|
317
320
|
Conditional `If-None-Match` reads and GeoJSON currently use HTTP directly. A matching City ETag returns 304 without a body; ordinary billing and rate limits apply. These JSON client methods do not supply conditional-cache handling.
|
|
318
321
|
|
|
322
|
+
IP paid Deep includes supported approximate location, `state_name`, `postal`, `latitude`, `longitude`, `timezone`, routed `network`, `asn_type` and public `proxy` status. Missing facts remain null. Coordinates describe range geography, not device GPS. `asn_type` classifies the origin network, not subscriber connection technology. Proxy/VPN false means unlisted. Optional fields are omitted without the requested detail or access.
|
|
323
|
+
|
|
319
324
|
## Capital coordinate migration
|
|
320
325
|
|
|
321
326
|
Country and State capital coordinates use `latitude` and `longitude`. Update
|
|
@@ -324,4 +329,26 @@ Country and State capital coordinates use `latitude` and `longitude`. Update
|
|
|
324
329
|
|
|
325
330
|
## Postal and Weather response corrections
|
|
326
331
|
|
|
327
|
-
|
|
332
|
+
In API 2.1, Postal `property_tax` contains `annual_median`; tax is grouped under `tax` with `name`, `rate` and component rates. Weather minute rows use `precipitation_rate` (mm/h) and `precipitation_rate_in` (in/h). Historical `history.precipitation` and `precipitation_in` remain daily totals. Unavailable Weather collections remain `null`; a known empty collection remains `[]`. MCP returns these API values unchanged. Existing clients reading the earlier minute keys must update those reads when using current API 2.1.0; frozen 1.0.0 is preserved.
|
|
333
|
+
|
|
334
|
+
## API 2.1 upgrade
|
|
335
|
+
|
|
336
|
+
API 2.1 Time returns the clock first and the matched place in `location`. Read that place directly; `location.candidates` is for unresolved choices. Unused `resolution` is absent. City matches keep the match kind, text and language without the source category or spelling score. Holiday JSON keeps scope and completeness without calendar hashes; explicitly selected work-profile pins remain.
|
|
337
|
+
|
|
338
|
+
This client targets ParseAPI 2.1.0. Upgrading requires response-reader changes: optional detail now lives on its resource. Read `population` instead of `deep.population`. Deep remains an explicit request for optional detail. Without the request or access, optional fields are absent. A returned null still means unknown. User-Agent device, OS and browser are objects in every mode. Postal tax is one `tax` object. Specialist Weather measurements live in `current`. Metered Carrier and HLR return the complete purchased result without a Deep switch.
|
|
339
|
+
|
|
340
|
+
Use the `email_verify` tool for mailbox verification. It sends POST `/email/verify` with `{ "email": "person@example.com" }` and defaults to no automatic retries. The earlier Email deep argument is accepted only as a migration alias for that same operation. App keys receive `permission_denied`. Bulk exports retain their existing column names and saved-job recovery.
|
|
341
|
+
|
|
342
|
+
The 2.0 API is a temporary migration bridge for older installed clients. There is one maintained SDK line using the 2.1 structure.
|
|
343
|
+
|
|
344
|
+
## Upgrade to API 2.1
|
|
345
|
+
|
|
346
|
+
API `2.1.0` introduced natural fields. Update existing `.deep` property reads to the fields at their natural homes, such as `country.population`. User-Agent identities are objects; Postal tax and Weather observations keep their documented object homes. Paid profile detail is automatic in API 2.1. Existing explicit depth requests remain supported; verification stays explicit.
|
|
347
|
+
|
|
348
|
+
**This minor version changes existing field reads.** Upgrade the SDK and your application reads together. Existing factories remain. Email verification is explicit and includes basic validation; Carrier/HLR need no extra detail request. Preserve missing values, `null`, `false` and `0`.
|
|
349
|
+
|
|
350
|
+
## County migration: HTTP API 2.2
|
|
351
|
+
|
|
352
|
+
This source selects HTTP API `2.2.0`. County is the public name for counties and comparable administrative areas internationally. Use `county` and the State counties operation. Read `county`, `county_name`, `county_name_local` and `counties` in affected geography results; City `capital_of` uses `county` for this administrative level. Actual local types such as `department` and `district` retain their meaning.
|
|
353
|
+
|
|
354
|
+
This is a breaking field-read upgrade from earlier contracts. Canonical tools are `county` and `state_counties`. Deprecated `district` and `state_districts` tools preserve their historical result keys and omit the added County `iso_code` through a tool-only adapter; other geography tools use the canonical County fields. Hosted activation requires a separate compatibility review. Update property reads before upgrading. Older installed packages keep their existing API contract, and this client does not change an account's saved default. The shared hosted service and existing npm tags are unchanged by this opt-in package.
|