Platform identity
Platform name, provider or developer, official website, and a concise description of what it does.
Integration review
Can’t find your software?
Tell us which platform you use, and we’ll assess whether it can connect securely with OneChat. An API or MCP server helps the review, but it does not guarantee approval.
No credentials in this requestCapabilities reviewed before publicationScope and limits documented
Request an integration reviewDo not send passwords, tokens, API keys, private keys, production credentials, or sensitive customer data through this request.Start with the essentials
The initial request will be brief.
Start with the business need and basic platform details. Complete technical documentation comes later, if the review can move forward.
Request an integration review
Tell us which software you use and what you need OneChat to do. Technical documentation comes later.
What we need to review
What we review in the technical follow-up.
If the initial request is a potential fit, the next review covers the items below. Complete technical documentation is not required for the first contact.
Technical surface
Official documentation, available API, MCP server if one exists, authentication method, and test or sandbox environment.
Permissions and limits
Available operations, permission model, rate or usage limits, and any API licensing or commercial conditions.
Desired outcomes
The business questions or tasks the AI should support, plus sample data that contains no sensitive information.
Technical coordination
A technical contact who can clarify documentation and approve a safe test scope when the review advances.
How the review works
We verify the path before we describe the capability.
- 1
Receive the context
We organize the platform, documentation, and desired use cases.
- 2
Review documentation and security
We inspect the integration surface, authentication model, permissions, and constraints.
- 3
Identify possible capabilities
We translate supported operations into business outcomes without extending the evidence.
- 4
Validate limits and permissions
We record what can be read or written, under which configuration, and what remains unavailable.
- 5
Define scope and conditions
We determine the implementation path, dependencies, commercial availability, and review responsibilities.
- 6
Propose implementation when viable
A proposal follows only when the evidence supports a useful and controlled integration.
Request an integration review
Send the initial context securely. Do not include credentials, private keys, or sensitive information.