SDKs

Meridias SDKs are intended to standardise authentication, request formatting, retries, and telemetry correlation across application stacks. Teams can also integrate directly over HTTP when they need a thinner dependency surface.

Supported environments

The initial SDK surface should cover the environments most commonly used by platform teams and backend services. Each SDK should preserve the same request model so policy behaviour is consistent across languages.

Common responsibilities

SDKs should handle credential injection, typed request construction, timeout defaults, and propagation of request identifiers. These primitives reduce duplication and make routed responses easier to audit downstream.

Error handling

Client libraries should expose transport failures, policy rejections, and provider execution outcomes separately. This makes it easier to distinguish client defects from routing or provider issues.

Versioning expectations

SDK releases should track API compatibility and keep breaking changes explicit. Teams adopting an SDK should pin major versions and review changelogs before rolling upgrades across production services.

Next step

Pair the SDK guidance with API Overview to understand the underlying public surface.