> For the complete documentation index, see [llms.txt](https://docs.oshi.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oshi.co/oshi-help-center-jp/oshiherupusentheyoukoso/rinku.md).

# 公式リンク

OshiとGATE2の公式ウェブサイト、SNSアカウント、サポート連絡先。リンクを確認してからご利用ください。

Oshiの公式ウェブサイト、ソーシャルチャンネル、サポート連絡先をまとめました。

> ⚠️ **これらの公式ドメインからのリンクのみを信頼してください。** 詐欺から身を守る方法については[安全に利用するために](https://docs.oshi.co/help-and-support/staying-safe)をご覧ください。

***

### Oshi（プラットフォーム）

| ウェブサイト    | [oshi.co](http://oshi.co)                            |
| --------- | ---------------------------------------------------- |
| X/Twitter | [@oshikatsu\_co](https://x.com/oshikatsu_co)         |
| Instagram | [@oshikatsu\_co](https://instagram.com/oshikatsu_co) |
| YouTube   | [@oshi\_co](https://youtube.com/@oshi_co)            |
| Discord   | [discord.gg/oshi](http://discord.gg/oshi)            |
| お問い合わせ    | <support@oshi.co>                                    |
| ビジネス      | <business@oshi.co>                                   |

***

<figure><img src="https://content.gitbook.com/content/RqQp7knb3WEXx208VXMl/blobs/wXpZrTPlPSZMzBbgtYmx/GATE%202%20X%20Banner.png" alt=""><figcaption></figcaption></figure>

### GATE 2: Tides of Conflict

| ウェブサイト        | [gate2.oshi.co](http://gate2.oshi.co)           |
| ------------- | ----------------------------------------------- |
| X/Twitter（EN） | [@gate\_animeEN](https://x.com/gate_animeEN)    |
| X/Twitter（JP） | [@gate\_anime](https://x.com/gate_anime)        |
| Instagram     | [@gate2anime](https://instagram.com/gate2anime) |
| YouTube       | [@GATE2Anime](https://youtube.com/@GATE2Anime)  |
| お問い合わせ        | <support@gate2.co>                              |

***

<figure><img src="https://content.gitbook.com/content/RqQp7knb3WEXx208VXMl/blobs/D2NSFNCsErBHFLQ1rWtV/Mahoseka%20EN%20HEADER.png" alt=""><figcaption></figcaption></figure>

### 魔法のない世界で生きるということ（MahoSeka）

| ウェブサイト        | [mahoseka.com](http://mahoseka.com)         |
| ------------- | ------------------------------------------- |
| X/Twitter（EN） | [@mahoseka\_en](https://x.com/mahoseka_en)  |
| X/Twitter（JP） | [@mahoseka\_jp](https://x.com/mahoseka_jp)  |
| Instagram     | [@mahoseka](https://instagram.com/mahoseka) |
| お問い合わせ        | <contact@mahoseka.com>                      |

***

**関連記事**

* [安全に利用するために](https://docs.oshi.co/oshi-help-center-jp/help-and-support/nisurutameni.md): 公式チャンネルの確認方法と詐欺対策
* [サポートチャネル](https://docs.oshi.co/oshi-help-center-jp/help-and-support/saptochaneru.md): お困りのときはこちら
* [Oshiについて](https://docs.oshi.co/oshi-help-center-jp/oshiherupusentheyoukoso/oshinitsuite.md): Oshiとは何か、なぜ存在するのか

{% hint style="info" %}
**お困りですか？** <support@oshi.co> · [Discord](https://discord.gg/oshi)
{% endhint %}


---

# 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://docs.oshi.co/oshi-help-center-jp/oshiherupusentheyoukoso/rinku.md?ask=<question>&goal=<user_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.
