API contract
Use the documented API schemas and versioned request/response shapes. Validate inputs, handle non-success responses and treat timeout or cancellation as explicit states.
DEVELOPER CENTER
Build around traceable sources.
Integrate only against published, supported contracts. The developer experience should make authentication, authorization, provenance and failure states explicit.
Authentication
Authentication and authorization are governed by the deployed identity and Tinlance Platform configuration. Never embed privileged credentials in browser code or public runtime configuration.
Evidence handling
Preserve returned source references and integrity metadata. Validate export schema and hash where provided; do not manufacture timestamps or provenance for missing fields.
Agent integration
Tool registration, operation-level policy, approvals and audit belong to the authoritative Platform. Tinlyt does not replace TSIC or establish its own parallel execution authority.
Before connecting a production client
- Confirm the target API base URL and supported contract revision.
- Use the approved OAuth/session flow and server-side authorization.
- Test tenant separation, timeouts, retries and cancellation.
- Verify current Platform MCP registration and TSIC conformance for deployed revisions.
Live integration and private-beta readiness remain unverified until target-environment evidence is recorded.