原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

CREHQ Location Intelligence

作者:groundroof版本 0.1.7i★ 0i电脑或云端官方网站 ↗
注册名称io.github.groundroof/crehq-mcp-server

安装方法

能做什么

CREHQ entity affiliation, brand, site, franchise, credit, and location-intelligence tools.

作者提供的原文

  • 连接方式 电脑或云端
  • 账号或密钥 云端:连接时登录该服务(OAuth) · 本地:需要 CREHQ_API_KEY
  • 分类 旅行、地图与天气

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分15/100

质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 CREHQ Location Intelligence。按照 https://mcp.popnx.com/i/groundroof-crehq-mcp-server.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.crehq.com) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称CREHQ Location Intelligence
    Remote MCP server URL · 地址https://mcp.crehq.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsCREHQ Location Intelligence

  4. 试一试

    用 CREHQ Location Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 CREHQ Location Intelligence,或回答中出现 CREHQ Location Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称CREHQ Location Intelligence
    Connection · 地址https://mcp.crehq.com/mcp
  3. 在聊天中选择 CREHQ Location Intelligence

    开启新聊天,输入前先从插件列表中选择 CREHQ Location Intelligence

  4. 试一试

    用 CREHQ Location Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 CREHQ Location Intelligence,或回答中出现 CREHQ Location Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user crehq https://mcp.crehq.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 CREHQ Location Intelligence 在列表中并显示已连接

  4. 试一试

    用 CREHQ Location Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 CREHQ Location Intelligence,或回答中出现 CREHQ Location Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 CREHQ Location Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 CREHQ Location Intelligence,或回答中出现 CREHQ Location Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 CREHQ Location Intelligence 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 CREHQ Location Intelligence,或回答中出现 CREHQ Location Intelligence 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://mcp.crehq.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 CREHQ Location Intelligence 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user crehq https://mcp.crehq.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "crehq": {
      "url": "https://mcp.crehq.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "crehq": {
      "type": "http",
      "url": "https://mcp.crehq.com/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user crehq --env CREHQ_API_KEY=your-value -- npx -y crehq-mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "crehq": {
      "command": "npx",
      "args": [
        "-y",
        "crehq-mcp-server"
      ],
      "env": {
        "CREHQ_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "crehq": {
      "command": "npx",
      "args": [
        "-y",
        "crehq-mcp-server"
      ],
      "env": {
        "CREHQ_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "crehq": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "crehq-mcp-server"
      ],
      "env": {
        "CREHQ_API_KEY": "your-value"
      }
    }
  }
}

需要你填写的值

  • CREHQ_API_KEY 机密 必填 env
    你的 CREHQ API 密钥。可在 https://crehq.com/developers/sandbox/ 获取免费的沙盒密钥。
    查看英文原文Your CREHQ API key. Get a free sandbox key at https://crehq.com/developers/sandbox/.

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
57/周
许可证i
未注明许可证
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.1.7
发布到注册中心i
2026年7月11日
代码最后更新i
2026年10月14日
最近检查
2026年11月15日
作者
groundroof
软件包
npm: crehq-mcp-server
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 groundroof 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于37天前

  • ! 注意

    有许可证

    GitHub 无法识别许可证类型;请打开文件自行查看

  • ✓ 通过

    端点有响应

    在 69 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

已公开的漏洞(OSV.dev)

OSV.dev 中没有 crehq-mcp-server@0.1.7 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/groundroof-crehq-mcp-server.svg)](https://mcp.popnx.com/en/servers/groundroof-crehq-mcp-server)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“旅行、地图与天气”中的其他服务器比较i

  • 星标数多于此分类中其他 2025 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2025 个服务器的 13% 更新
  • 基础检查结果等于或优于此分类中其他 2025 个服务器的 63%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

CREHQ Location Intelligence 安全吗?

它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:CREHQ_API_KEY

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于37天前,最新版本(0.1.7)于4个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Mu, Award Travel Finder, Killbottleneck, Gondola Award Travel Search, Whimsical

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mu

News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.

作者:micro正在增长★ 4414个月前更新

在云端运行✓ micro.mu

Killbottleneck

Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.

作者:tengolabs起步阶段↓ 328/周★ 1413天前更新

在你的电脑上运行✓ 服务方 · killbottleneck.com

Whimsical

Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.

作者:WhimsicalCode起步阶段★ 112个月前更新

在云端运行✓ 服务方 · whimsical.com
与相似项目对比
本项
CREHQ Location Intelligence
MuAward Travel FinderKillbottleneckGondola Award Travel SearchWhimsical
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装需要安装在电脑上在云端运行,无需安装在云端运行,无需安装
需要密钥是否否是否否
可在 Claude 中按 + 添加否否否否否是
基础检查4/54/43/33/34/44/4
许可证NOASSERTIONAGPL-3.0MITMITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

CREHQ MCP Server

A Model Context Protocol server that turns CREHQ's live location-intelligence REST API into native tools for Claude and other AI agents. Ask an agent *"where should Chipotle open next?"*, *"which hotel chain is this venue affiliated with?"*, *"who has ever occupied this address?"*, or *"what are Aspen Dental's credit signals?"* — and it can actually answer, backed by CREHQ's canonical, multi-source verified database (government records, franchise filings and brand-published data) of franchise & multi-unit brands, individual storefronts, FDD financials, credit signals, and site-level tenancy history.

This is a thin wrapper over CREHQ's existing production API (https://crehq.com/wp-json/crehq/v1). It does not store data or modify anything server-side — it authenticates with your API key and forwards calls.


What it exposes (33 tools)

Upgrade / paywall routing

  • crehq_request_upgrade — use when a sandbox user asks for premium data such as credit signals, FDD/Item 19, site-selection criteria, real-estate requirements, contacts, source provenance, change history, bulk downloads, whitespace, co-tenancy, or site timeline. With a free sandbox key, this records upgrade intent in CREHQ and returns the user a clear upgrade path instead of saying the data does not exist.
  • crehq_intelligence_preview — for Pro self-serve keys, spends the one monthly controlled intelligence preview credit and returns a bounded evidence frame without exposing raw premium tables or redistribution rights.

Entity affiliation

  • crehq_resolve_entity_affiliation — resolve a venue URL, name, or address to an evidence-backed affiliation status, canonical brand, operator, and parent company across hotels, restaurants, retail, healthcare, banks, auto dealers, EV charging, and other location categories. Valid outcomes include branded, independent, not a commercial venue, and unresolved. A paid-access response preserves its exact checkout URL and CREHQ intent id. Checkout emails a new Pro key that must be installed before retrying; the current credential is not upgraded in place.

Companies / brands

  • crehq_companies_list — list brands, filter by category & expansion status
  • crehq_companies_search — resolve a brand name → CREHQ company id (start here)
  • crehq_company_get — canonical brand profile, verified unit count, ownership
  • crehq_company_credit_signals — credit profile, sponsor/issuer context, ratings, capital structure
  • crehq_company_franchise — FDD fees, royalties, investment, Item 19 figures
  • crehq_company_real_estate — site-selection criteria & target geographies
  • crehq_company_contacts — real-estate / development decision-maker contacts

Locations

  • crehq_locations_list — store records by brand / state / category
  • crehq_location_get — one location with full attributes & verification trace
  • crehq_locations_search — fuzzy multi-field location search
  • crehq_locations_nearby — radius search around a lat/lng (trade-area mapping)
  • crehq_locations_bulk — bulk pull by id list, brand list, or GeoJSON polygon
  • crehq_locations_events — cross-brand open/close/relocate lifecycle stream
  • crehq_location_history — full event log for one physical store

History & flagship differentiators

  • crehq_company_changes — date-bounded change feed for one brand
  • crehq_company_occupancy — point-in-time roster (footprint on a past date)
  • crehq_site_timeline — every brand that ever occupied an address, over time

Premium intelligence (Intel & Enterprise tiers)

  • crehq_whitespace — markets where competitors are present but the brand isn't
  • crehq_co_tenancy — which brands cluster near this brand's stores
  • crehq_location_site_profile — CREHQ Modeled Site Profile for one location
  • crehq_company_site_pattern — empirical brand site pattern from observed footprint/context
  • crehq_recent_location_context — recent observed/opening rows with traffic, demographics, and coverage flags

Modeled Site Profile outputs must be described as CREHQ-modeled from observed location/context data, not as company-stated site requirements unless the response includes explicit stated-requirement provenance.

The Modeled Site Profile REST routes are staged pending explicit production approval. Until those routes are published, these three tools may return a 404 even though the MCP catalog advertises them for local testing.

Datasets

  • crehq_datasets_list / crehq_dataset_get / crehq_dataset_download / crehq_dataset_categories
  • crehq_purchased_datasets_list — list dataset snapshots purchased by the connected key owner, including snapshot date and hosted MCP access status.
  • crehq_purchased_dataset_locations — query rows from a buyer-owned point-in-time dataset snapshot during the hosted access window.

Trends

  • crehq_trends_company — outlet/fee/financial time series for a brand
  • crehq_trends_geographic — metro/state concentration & velocity

Getting an API key

  1. Free sandbox (1,000 calls/mo, 2 req/s, no credit card; rows per brand are limited monthly, and every response shows the exact row budget): https://crehq.com/developers/sandbox/ — enter your email, complete the browser verification challenge, and a key is emailed to you. The key is delivered by email only and looks like crehq_live_xxxxxxxx…. Sandbox keys can run bounded location lookups (crehq_locations_list by brand, and crehq_locations_nearby by radius) and call the entity-affiliation resolver once per month. If the user asks for premium intelligence, call crehq_request_upgrade; it records the requested topic for CREHQ follow-up and tells the user what to upgrade.
  2. Pro MCP — $99/mo, self-serve Stripe checkout. Includes bounded D1 location queries, selected D2 provenance fields, 25,000 core calls/month, up to 250 affiliation resolver calls/month, and one controlled intelligence preview per month. Start at https://crehq.com/developers/sandbox/#pro-checkout.
  3. Datasets / Intelligence / Enterprise — buy licensed point-in-time dataset snapshots when you need the file; use enterprise licensing for premium intelligence, refresh plans, API/feed delivery, redistribution, embedded rights, and SLAs. See https://crehq.com/pricing/.

Fastest way to try CREHQ in an agent

  1. Get a sandbox key at https://crehq.com/developers/sandbox/.
  2. For hosted/remote MCP clients, add https://mcp.crehq.com/mcp and authorize with that key.
  3. For local stdio clients, install with npx -y crehq-mcp-server and set CREHQ_API_KEY.
  4. Ask: Use CREHQ to identify the brand, operator, and parent affiliation of the venue at https://www.earleycrescent.org/.

Self-serve keys expose the affiliation resolver, bounded location lookups, upgrade routing, purchased-dataset access, and the controlled intelligence preview. The backend still enforces the key's actual Free, Pro, and purchased dataset entitlements, returning a structured upgrade or purchase response when needed. Intel and Enterprise keys expose broader API tools according to the key's CREHQ tier.


Install & build

Requires Node.js ≥ 18.

Install the published stdio server with npx:

CREHQ_API_KEY=crehq_live_xxxxx npx crehq-mcp-server

Or build from source:

git clone <this-repo> crehq-mcp-server

cd crehq-mcp-server npm install npm run build # compiles TypeScript → dist/ cp .env.example .env # then edit .env and set CREHQ_API_KEY

Verify your key against the live API before wiring up a client:

export CREHQ_API_KEY=crehq_live_xxxxx

./test.sh # exercises 6 read endpoints with curl

Run the server standalone (it speaks MCP over stdio, so it will wait for a client on stdin — Ctrl-C to exit):

CREHQ_API_KEY=crehq_live_xxxxx node dist/index.js

Connect to Claude Desktop

Add this to your claude_desktop_config.json:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{

"mcpServers": { "crehq": { "command": "npx", "args": ["-y", "crehq-mcp-server"], "env": { "CREHQ_API_KEY": "crehq_live_your_key_here" } } } }

Restart Claude Desktop. The CREHQ tools appear under the tools (🔌) menu.

Other MCP clients

Any stdio-capable MCP client (Claude Code, Cursor, Cline, Continue, the mcp CLI, custom @modelcontextprotocol/sdk clients, etc.) connects the same way — run node dist/index.js as the server command with CREHQ_API_KEY in the environment.

Claude Code:

claude mcp add crehq --env CREHQ_API_KEY=crehq_live_xxxxx -- npx crehq-mcp-server

Hosted remote connector

The hosted Cloudflare Worker version is kept in remote/. It provides the same CREHQ connector as a remote MCP server at https://mcp.crehq.com/mcp, with OAuth/key exchange and scope gating for premium tools. Its own deploy notes are in remote/DEPLOY.md and connector-submission copy is in remote/CONNECTOR-SUBMISSION.md.

The MCP Registry metadata lives in server.json, with registry ownership declared by mcpName in package.json.

Maintainer workflow

GitHub Actions owns the repeatable release path:

  • CI builds and tests the stdio package and the hosted Worker on every push.
  • Deploy Remote MCP deploys remote/ changes to Cloudflare Workers and then verifies https://mcp.crehq.com/health.
  • Publish npm publishes the stdio package from a vX.Y.Z tag or manual workflow dispatch. It skips safely when that package version already exists.

Required repository secrets are already named:

  • NPM_TOKEN
  • CLOUDFLARE_API_TOKEN
  • CLOUDFLARE_ACCOUNT_ID

Configuration

Env varRequiredDefaultPurpose
CREHQ_API_KEYyes—Your crehq_live_… key
CREHQ_API_BASEnohttps://crehq.com/wp-json/crehq/v1Override API base (staging/proxy)
CREHQ_TIMEOUT_MSno30000Per-request timeout in ms
CREHQ_API_SURFACEnoautoAuto-detect sandbox vs full key; can be selfserve or full for debugging

Error handling

Tools never crash the agent's turn — failures come back as a readable message with a fix-it hint:

  • No key set → instructs you to set CREHQ_API_KEY and links the sandbox.
  • 401 / 403 → "invalid or revoked key / endpoint not in your tier" + upgrade link. For credit signals, FDD, site-selection criteria, contacts, provenance, change history, bulk data, whitespace, co-tenancy, or site timeline, call crehq_request_upgrade.
  • 404 → "check the id/slug; resolve it with a search tool first."
  • 429 → respects Retry-After; reminds you of the free-tier 2 req/s limit.
  • Self-serve guidance → whatever the API says about its own limits is passed through verbatim: the API's message, row_budget (used / limit / basis / reset), the full_dataset offer, upgrade_url / enterprise_url, did_you_mean slugs, and the markets a brand is served in. Successful self-serve calls lead with a short guidance block (coverage_note, total_available / has_more, row_budget, full_dataset, resolved_from, market_scope, and the Enhanced (D2) preview label, fields and note) ahead of the JSON rows.
  • 5xx / timeout / network → transient-error guidance to retry with backoff.

Pagination, cache, and stream cursors (X-WP-Total, X-CREHQ-Next-Since, X-CREHQ-Cache, rate-limit he

只显示了开头部分;其余内容请在仓库中阅读