> For the complete documentation index, see [llms.txt](https://phisports.gitbook.io/phigolfg2e-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phisports.gitbook.io/phigolfg2e-white-paper/introduction/phinetworks.md).

# PHINETWORKS

<figure><img src="/files/iro7PTXR8uH5J7hVtWMd" alt=""><figcaption></figcaption></figure>

Founded in 2008, PHINETWORKS secured a proprietary swing analysis algorithm after about four years of development and successfully launched Phigolf in 2017. We hold related patents, design rights, and trademarks both domestically and internationally. Our product’s innovation has been recognized through many awards, including being named one of the PGA Hot Stuff Top 7, achieving Amazon Best Seller status in the United States, and receiving commendations from the Prime Minister, the Minister of Culture, Sports and Tourism, and the Minister of Trade, Industry and Energy.&#x20;

PHINETWORKS will expand into various sports and leisure areas beyond golf and is committed to becoming the world’s leading home sports company by integrating sports and IT.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://phisports.gitbook.io/phigolfg2e-white-paper/introduction/phinetworks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.