日本語 | English
About the Establishment of These Terms
We established these Terms on November 3, 2026, and they take effect on December 3, 2026. Most of those who have started using the public API can continue to use it without changing how they use it. Please check by the effective date that your use complies with these Terms. If you do not agree to these Terms, stop using the API, revoke your personal access tokens, revoke the authorizations in Authorized apps (including MCP clients), and delete the OAuth apps you registered by the effective date.
These Terms set out the following points:
- These Terms also apply to the remote MCP server and to its use from MCP clients (such as Claude and ChatGPT)
- Using the API is free of charge, and you can use it without individual permission, including for commercial purposes
- Tokens and client secrets must be kept secret and must not be shared with others
- Operations performed with a token, including those performed by AI agents, are treated as operations by the owner of the token
- Use by AI agents is permitted, and we set out the responsibility for passing content to external AI services
- We set out the scope in which you may handle pages and member information obtained through the API
- We set out what creators of OAuth apps must comply with
- We set out the display of the Wikino name and logo, rate limits, and prohibited acts
- When we stop providing a version of the API, we will announce it at least one year in advance
These Terms are newly established, and there is no previous version.
The operator (the "Operator") of "Wikino" (the "Service"), a wiki where you create pages in spaces and connect them with links, sets out the conditions for using the API of the Service as these API Terms of Use (these "Terms") as follows. These Terms apply in addition to the Terms of Service.
This English version is a translation of the Japanese original. If there is any discrepancy in interpretation between the Japanese version and the English version, the Japanese version prevails. These Terms are governed by the laws of Japan.
Article 1 (Scope)
These Terms apply to everyone ("Users of the API") who uses any of the following (collectively, the "API"):
- The public API (operations on URLs starting with
https://wikino.app/api/v1) - App authorization through OAuth (including authorization from devices that cannot open a browser)
- Personal access tokens
- Wikino CLI (the official tool that uses the public API)
- The remote MCP server (
https://wikino.app/mcp) - Other APIs we provide in the future
These Terms also apply when you use the remote MCP server from MCP clients such as Claude and ChatGPT.
Matters not set out in these Terms are governed by the Terms of Service. If these Terms and the Terms of Service differ regarding the use of the API, these Terms prevail. The handling of personal information through the API is governed by the Privacy Policy.
Article 2 (Definitions)
The terms used in these Terms have the following meanings:
- Token: a personal access token, or a token that an OAuth app or an MCP client receives through authorization
- Owner of a token: the member who issued a personal access token, or the member who authorized an OAuth app or an MCP client
- App: an app, script, tool, AI agent, or the like that Users of the API build or use to use the API
- MCP client: an AI app or the like that connects to and uses the remote MCP server (such as Claude, ChatGPT, and Visual Studio Code)
- Creator of an OAuth app: the member who registered an OAuth app in a space
Article 3 (Fees and Commercial Use)
Using the API is free of charge. As long as Users of the API comply with these Terms, they can use the API without individual permission, whether for commercial or non-commercial purposes.
Article 4 (Management of Tokens)
Users of the API must keep tokens and the client secrets of OAuth apps secret, just like passwords. You must not do the following:
- Share tokens or client secrets with others
- Embed tokens or client secrets in apps, scripts, configuration files, or the like that you distribute
- Write tokens or client secrets in places others can see, such as public repositories, websites, or social media
When you want others to use the API, have them authorize an OAuth app or an MCP client, or have them issue their own personal access tokens.
If a token or client secret becomes known to others, or may have become known, immediately revoke the token or regenerate the client secret. Choose the scopes and expiration dates of tokens within the range necessary for their use.
Article 5 (Attribution of Operations Performed with Tokens)
Operations performed with a token are treated as operations by the owner of the token. Operations performed with a token of an OAuth app or an MCP client are also treated as operations by the member who authorized the app. The same applies when you let an AI agent, a script, or the like use a token.
The owner of a token is responsible for complying with the Terms of Service regarding operations performed with the token (such as creating and updating pages), just as if they had performed them on the screen themselves.
Article 6 (Use by AI Agents)
Users of the API may let AI agents use the API. Authorizing an MCP client to use the remote MCP server is one way of doing so. The content of a space that an MCP client obtains is passed to the AI service of that MCP client.
Whether to pass the content of a space to an agent or an external AI service is for Users of the API to decide at their own discretion and responsibility. The terms of that AI service apply to the handling of the content you pass. When passing pages in private topics or drafts, check that doing so is within the scope permitted in the space.
Article 7 (Handling of Obtained Content)
Users of the API may handle pages and member information obtained through the API to the extent necessary for their own work or for providing the features of their apps. Pages written by other members, and the usernames and names of members, may also be handled within this scope.
You must not do the following:
- Make content that is not public on the Service, such as pages in private topics or drafts, public beyond the scope permitted in the space
- Collect information about other members beyond the extent necessary for your own work or for providing the features of your apps
Article 8 (What Creators of OAuth Apps Must Comply With)
Creators of OAuth apps must comply with the following:
- Request only the scopes necessary for the features of the app
- Show users of the app the data the app obtains and how it uses the data
- Use the obtained data only to the extent necessary to provide the features of the app, and do not sell it or provide it to third parties
- Delete the data obtained by the app when an authorization is revoked and when you delete the app
- Delete data remaining in backups once the normal retention period has passed
Article 9 (Display of the Name and Logo)
You may use the Wikino name and logo to describe what your app connects to (such as "a tool for reading and writing Wikino pages").
On the other hand, you must not display anything that may lead people to mistake your app for an official app of Wikino or one of its partners. This includes putting the Wikino name or logo in the name or icon of your app. The only official app of Wikino is the one provided by the Operator (Wikino CLI).
Article 10 (Rate Limits)
Requests to the API are subject to rate limits separately set by the Operator. The rate limits are listed in the section "呼び出せる回数の上限" (rate limits) of 公開API (in Japanese). We may revise the rate limits, and the latest rate limits always apply.
Users of the API must not circumvent the rate limits, such as by splitting requests across multiple tokens or accounts.
Article 11 (Prohibited Acts)
When using the API, in addition to the acts prohibited by the Terms of Service, Users of the API must not do the following:
- Attempt to access spaces, topics, pages, or the like without permission
- Exploit vulnerabilities of the API or the Service
- Place an excessive load on the Service
If you find a vulnerability of the API or the Service, report it to the vulnerability reporting contact.
Article 12 (Disclaimer of Warranties and Changes to Specifications)
The Operator notifies Users of the API of the following:
- We may make compatible changes to the specifications of the API (such as adding fields or operations) without notice
- We make incompatible changes in a new version of the API
- However, changes necessary for security or to comply with laws and regulations may be made within the same version
- When we stop providing a version of the API, we will announce it in the announcements on the Service at least one year before the end date
- The same applies when we stop providing the entire API
- When we stop providing the Service itself, the Terms of Service apply
- The Operator does not guarantee that the information provided by the API is accurate or that the API is always available
- The Operator does not provide support for apps made by others
- Creators of apps handle any trouble that arises between their apps and their users
The scope of the Operator's liability is governed by the Terms of Service.
Article 13 (Measures Against Violations)
If a User of the API violates these Terms or the Terms of Service, or uses the API in a way that interferes with the operation of the Service, the Operator may take the following measures without prior notice:
- Revoke tokens
- Delete the registration of OAuth apps
- Block access to the API
We may also take measures set out in the Terms of Service (such as suspending the use of the Service).
Article 14 (Changes to These Terms)
The Operator may change these Terms through the same procedure as for changing the Terms of Service. We also change these Terms when a newly provided API needs its own conditions.
Article 15 (Contact)
Please send questions about these Terms to the following email address:
- Email address: [email protected]
Supplementary Provisions
- Established: November 3, 2026
- Effective: December 3, 2026