【合作自薦】為小飯票 Nomtiq 等出海 Agent 插件提供超穩定 Google Maps/SERP 備用源

[talordata-serp-api]

大佬們好！

近期關注到 ClawHub 社群中由 @OakcoderX 開發的 小飯票 Nomtiq 插件，產品邏輯非常讚，精準切中了 AI 找餐廳和在地生活推薦的剛需。

研讀了項目的技術文檔與搜尋路由規則，註意到小飯票在海外（大陸以外）的餐廳搜尋中，底層默認硬編碼調用的是 Serper。我們團隊是 TalorData 的官方人員，我們提供企業級的 Google Maps / 多引擎 SERP 數據抓取服務，非常希望能作為並列備用源接入生態。

針對獨立開發者和高並發 AI Agent 場景，我們比原通道有幾個非常現實的升級優勢：

1. 高並發穩定性：我們原生自帶全球住宅代理網路，能完美扛住 AI Agent 多步推理（Deep Search）或長鏈 Agent 工作流時的高頻聯網穿透，絕對不會彈驗證碼或被谷歌限流。
2. 多引擎數據：除了 Google Maps 之外，我們還能橫向聚合 Bing、Yandex 等多維數據，返回的 JSON 結構極度乾淨。

關於合作與福利：
我們的平台目前非常開放，新用戶註冊無需綁定信用卡，直接默認贈送 500 次免費請求額度，足夠生態內的開發者和小飯票的用戶做完美的在地冷啟動測試。

另外，我們平台目前支持聯盟夥伴計劃（Affiliate），可以為小飯票等開源插件作者定制專屬的推薦連結。後續導流過來的付費用戶，作者都能獲得長期的高比例流水返傭，希望能藉此為社群內的優質開源項目提供一份可持續的資金支持。

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed August 10, 2026, 11:03 AM ET / 15:03 UTC.

Summary
Keep open for a maintainer product and ownership decision. Current ClawHub already supports publishing independently developed web-search provider plugins, but it cannot itself choose Nomtiq’s runtime fallback or endorse this commercial provider.

Reproducibility: not applicable. this is a commercial integration proposal, not a reported malfunction with a current-main reproduction path.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Include redacted logs or terminal output.

Maintainer decision needed

Question	Recommendation
Should ClawHub coordinate or endorse TalorData as a commercial fallback provider for Nomtiq, or direct it to publish an independently reviewed provider plugin without an endorsement?	Use the independent publisher path: Ask TalorData to submit a standalone provider plugin through normal validation and security review, with no ClawHub endorsement or Nomtiq change.

Why: The repository already provides a distribution path, but commercial sponsorship and a third-party plugin’s runtime fallback policy require maintainer and plugin-owner intent.

Next step
A maintainer must decide the commercial endorsement and third-party runtime ownership boundary; there is no bounded ClawHub defect for an automated repair PR.

Security
Needs attention: The advertised CAPTCHA and rate-limit avoidance through residential proxies needs policy and package-level security review before any promotion.

Review details

Best possible solution:

Use the existing registry path for a standalone, source-attributed web-search provider plugin with explicit credentials, compatibility metadata, install/update documentation, terms-compliant behavior, and a smoke proof; let Nomtiq’s owner independently decide whether to add it as a fallback.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a commercial integration proposal, not a reported malfunction with a current-main reproduction path.

Is this the best way to solve the issue?

Unclear: a standalone plugin uses the existing registry route, but endorsing it or changing Nomtiq’s fallback policy requires explicit product and plugin-owner agreement.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• A commercial endorsement could be mistaken for a safety or reliability guarantee; no package, provider terms, credential model, or runtime proof has been submitted.
• The residential-proxy and CAPTCHA/rate-limit-avoidance claims require policy review before any listing or integration is promoted.

Codex review notes: model internal, reasoning high; reviewed against 82313c2bb17f.

Label changes

Label justifications:

• P3: This is a speculative commercial integration and endorsement proposal, not a reported broken ClawHub behavior.

Evidence reviewed

Security concerns:

• [low] Review rate-limit-evasion claims before promotion — docs/acceptable-usage.md:46
  The proposal markets residential proxies as preventing CAPTCHA and rate limiting; any submitted package must demonstrate terms-compliant behavior and transparent credentials before it can be reviewed as a marketplace listing.
  Confidence: 0.9

What I checked:

• Web-provider plugin surface: Current catalog classification recognizes plugin manifests declaring web-search providers and classifies them under the web category, supporting a standalone provider-package route. (packages/schema/src/pluginCategories.ts:56, 82313c2bb17f)
• Published plugin workflow: Current documentation supports publishing external code plugins with explicit compatibility metadata and waiting for pre-publication security checks. (docs/cli.md:656, 82313c2bb17f)
• Ownership boundary: VISION.md: The product boundary assigns ClawHub distribution, provenance, and scanning, while OpenClaw owns runtime and installation execution; this proposal’s fallback routing is therefore outside a ClawHub code repair. (VISION.md:99, 82313c2bb17f)
• History and release provenance: Blame attributes the current web-provider classification to Patrick Erichsen’s 87ca030 commit; git tag --contains reports v0.23.3 and main contains that commit, so the standalone publication/discovery path is already shipped. (packages/schema/src/pluginCategories.ts:56, 87ca030c30f3)
• Marketplace policy: A future package must be reviewed carefully because the proposal advertises residential proxies to avoid CAPTCHA and rate limits, while marketplace policy prohibits rate-limit abuse. (docs/acceptable-usage.md:46, 82313c2bb17f)

Likely related people:

• Patrick Erichsen: Blame attributes the current web-provider manifest classification to Patrick’s shipped package-publication commit. (role: recent registry and plugin-surface contributor; confidence: high; commits: 87ca030c30f3, a643b75eca24; files: packages/schema/src/pluginCategories.ts, VISION.md)
• Conor Bronsdon: Recent history attributes the publishing documentation path to Conor, making them a useful adjacent contact for the self-publish route. (role: recent publishing-documentation contributor; confidence: medium; commits: fd3bef4ae758; files: docs/publishing.md)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.