> For the complete documentation index, see [llms.txt](https://hismartpowercom.gitbook.io/hismartpowercom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hismartpowercom.gitbook.io/hismartpowercom/2026-shi-jie-bei.md). # 2026世界杯
[2026世界杯](https://www.hismartpower.com/) — 全球体育数据与盘口资金流向分析专业平台。实时更新机构指数、2026世界杯赛事前瞻预测，分享来自顶尖足球数据分析师的科学资金管理策略。依托大数据模型与智能算法，为全球球迷与体育爱好者提供更精准、更高效的赛事分析体验。\ 地址: 中国广东省深圳市福田区龙尾路 518034\ 电话号码: 852 3568 8813\ 网站: \ 电子邮箱: \ 话题标签: #2026世界杯 #体育竞猜 #真人娱乐 #电子竞技 #娱乐平台\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hismartpowercom.gitbook.io/hismartpowercom/2026-shi-jie-bei.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.