Developer
Technical documentation routes for integration, authentication, APIs, and implementation guidance.
API · Postman · CLI · SDK
Postman collection, reference CLI, SDK installs, and API docs in one place
Beyond curl examples on /developers, import the public Postman collection, use the bash reference CLI for smoke tests, and install PyPI/npm SDKs v0.1.0. Interactive Swagger remains in the panel.
Resource Navigation
Audience Coverage
Enterprise Sales
Commercial materials that support buyer discovery, evaluation, and deal progression.
Key Takeaways
- OpenAPI 3.0: /docs/developers/trustoriginality-api.openapi.yaml
- Postman collection: /docs/developers/trustoriginality-api.postman_collection.json
- Reference CLI: /docs/developers/trustoriginality-cli.sh (bash smoke-test wrapper).
- SDKs: pip install trustoriginality · npm install @trustoriginalityai/sdk
- Narrative API reference: /developers/api-reference (from docs/API.md)
OpenAPI & Postman
Machine-readable and importable.
OpenAPI YAML
Download /docs/developers/trustoriginality-api.openapi.yaml — core analyze, KYC, and provenance paths.
Postman
Import /docs/developers/trustoriginality-api.postman_collection.json — set baseUrl and apiKey variables.
Panel Swagger
Interactive Swagger UI remains at panel /swagger for authenticated exploration.
CLI smoke tests
Terminal curl wrapper.
Download
Use /docs/developers/trustoriginality-cli.sh with TO_API_KEY and optional TO_BASE_URL.
Not a production SDK
Use PyPI/npm SDKs for application integration; CLI is smoke-test only.
SDK source
Package distribution.
PyPI
Python package trustoriginality 0.1.0 at pypi.org/project/trustoriginality/.
npm
JavaScript package @trustoriginalityai/sdk 0.1.0 on npm.
Public GitHub
No public github.com/trustoriginality org in repo — source ships inside published packages; enterprise source review via support@trustoriginality.ai.
Downloads
OpenAPI 3.0 spec
Open access. Core REST paths for analyze, KYC, and provenance.
Postman collection
Open access. Import into Postman — set variables baseUrl and apiKey.
Reference CLI
Open access. Bash smoke-test wrapper — TO_API_KEY required.
API reference (web)
Open access. Full endpoint documentation from docs/API.md.
FAQ
Yes — /docs/developers/trustoriginality-api.openapi.yaml. Full narrative reference is at /developers/api-reference.
No. CLI is a smoke-test helper; SDKs handle retries and typing for production.
Rendered publicly at /developers/api-reference; source copy in repository docs/API.md and wwwroot/docs/developers/api-reference.en.md.
Related Topics
Entity Links
Developers hub
Quick start curl and SDK install.
Open routeAPI reference route
Developer docs navigation.
Open routeTechnical documentation
Pipeline and limitations overview.
Open routeInternal Linking
Related Resources
Developer API Guide Template
Use this template when a developer, architect, or technical evaluator needs a structured path into APIs, authentication, examples, and implementation best practices.
Open resourceVideo Library
Honest video content index — no fabricated view counts or customer video testimonials.
Open resourceProduct Overview Catalog Brief
A concise product-catalog resource that explains the three security pillars, named products and statuses, integration surfaces, and how they align with public package tiers.
Open resourceRegulatory & Whitepaper Downloads
Index of publicly downloadable regulatory PDFs and markdown guides. Enterprise narrative whitepaper PDF remains request-gated.
Open resourceEnterprise CTA
Commercial routes stay grounded in approved TrustOriginality.ai sales, procurement, developer, and trust surfaces.
