> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/ja/8-ysuksutoshinario/83-purosesukemoderu.md).
# 8.3 導入プロセス：企業・団体向け展開モデル
## ◆ GETは以下の3段階で導入をサポートします。
### ステップ1：ライト連携（非技術連携）
* GET Pay導入（QRコード決済／参加特典配布）
* NFT販売代行／発行サポート
* DAO投票機能の限定活用（Google Form＋GET連携）
### ステップ2：プラットフォーム連携（中規模連携）
* GET Platformへのプロジェクトページ設置
* 投票／支援／NFT販売／限定コンテンツの運用
* マーケティング連携（SNSキャンペーン、イベント開催）
### ステップ3：API／SDKレベルの連携（本格導入）
* 自社サービス内へのGETトークン連携
* 外部ID／Wallet統合、GET Wallet内での表示
* 報酬配布やマイル連動の自動ロジック組込
* ノード連携またはスマートコントラクト活用によるオンチェーン化
---
# 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://docs.global-entertainment-token.org/ja/8-ysuksutoshinario/83-purosesukemoderu.md?ask=&goal=
```
`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.