The Oryn SDK is planned as the recommended integration layer for apps that do not want to hand-roll quote handling, secret generation, order creation, claim submission, and status polling. Until the SDK is released, use the API-first path:
  1. Developer Quickstart
  2. Integration Guide
  3. API Conventions
  4. Generated Orderbook and Relayer API references

​
Planned SDK responsibilities

ResponsibilityWhat the SDK should hide
Secret handlingGenerate secure secrets and commitment hashes.
Quote handlingValidate expiry, route, assets, and amount consistency.
Order creationBuild API payloads from typed intent inputs.
Wallet callsPrepare source initiation transactions.
ClaimSubmit direct or hop claim payloads.
PollingNormalize API fields into user-facing lifecycle states.

​
What the SDK should not hide

  • the amount the user is sending and receiving
  • the chain and token selected by the user
  • wallet prompts and approvals
  • transaction hashes
  • cancellation availability
The SDK should make integrations safer, but it should not make swaps feel opaque. Apps should still show route, amount, status, and transaction details.