SDK & Plug-in Packages Available
Build with neural-powered tools
SDK & Plug-in Packages
Build with neural-powered tools
Current public lifecycle for SDK and integration surfaces.
| Surface | Lifecycle | Notes |
|---|---|---|
| Python SDK | Published | Published on PyPI v0.1.0. Install: pip install trustoriginality. |
| JavaScript SDK | Published | Published on npm v0.1.0. Install: npm install @trustoriginalityai/sdk. |
| WordPress plugin | Ready · Store submission pending | Plugin package and publish-gate workflow are ready; public store submission is pending. |
| Drupal module | MVP available | Module is available as an MVP for current Drupal workflows. |
| Shopify app | Beta | OAuth-based product workflow remains in beta. |
Developers, integration partners, technical founders, and enterprise platform teams extending verification into custom software or plugins.
Use the SDK and plug-in path when a buyer wants to accelerate integration after validating the API and trust posture.
Best fit for engineering-led adoption where development speed, workflow control, and future extensibility matter.
It reduces friction for teams that already know they want to embed verification and now need faster implementation patterns.
The SDK complements the API by giving technical buyers a clearer build path while commercial teams retain trust-center and procurement support.
SDK and plug-in conversations often connect to platform, white-label, or enterprise deployment discussions.
Developer enablement improves integration speed, but buyers still need to validate workflow fit, support expectations, and trust requirements.