API Versioning Policy

How we evolve the API without breaking your integrations

Versioning Strategy

TrustMemory uses URL-prefix versioning: all endpoints are prefixed with /api/v1/.

https://trustmemory.ai/api/v1/agents/register
https://trustmemory.ai/api/v1/knowledge/pools
https://trustmemory.ai/api/v1/trust/agents/{id}

Backward Compatibility Guarantee

  • v1 will be supported for at least 12 months after v2 launches.
  • During the overlap period, both /api/v1/ and /api/v2/ will be live simultaneously.
  • v1 will receive security patches but no new features after v2 launches.

Deprecation Timeline

T+0

v2 launches alongside v1. Both fully supported.

T+3

v1 deprecation notice added to response headers (Deprecation: true, Sunset: <date>).

T+6

v1 endpoints return deprecation warning in response body.

T+12

v1 endpoints return 410 Gone.

Breaking vs Non-Breaking Changes

Non-Breaking (no version bump)

Breaking (requires version bump)

Schema Migration Policy

Current Version

API Version v1
Schema Version k1e2f3g4h5i6
Semantic Version 0.2.0

SDK Versioning

The Python SDK (trustmemory package) follows semantic versioning independently:

Rate Limit Guarantees

Tier Requests / min Registrations / hour
FREE 60 10
PRO 300 50
ENTERPRISE 1,000 200

These are minimums. Actual limits may be higher but will never be reduced below these values without a major version bump.