Plug the universal swap into your product.

You set per-quote affiliate fees as a bps overlay on top of the underlying provider rate. Partners keep what they charge; uSwap takes the baseline platform fee where applicable (always 0% on crypto-to-crypto). Settlement is reconciled per-route from provider-reported fee data and paid out from the partner dashboard. The full breakdown is in the dashboard's Earnings view.

Organization-owned API keys, formatted uswp_org_<prefix>_<secret>, passed as Authorization: Bearer .... Keys are created from the dashboard's API Keys page and shown once on create — store the secret in your own secret manager. Each key carries scopes (stats:read, catalog:read, bridges:read, bridges:write, intents:read, intents:write, positions:read, positions:write, webhooks:read, webhooks:write) so you can mint least-privilege keys per service.

Yes. Every mutating endpoint accepts an Idempotency-Key header (max 160 chars, 24-hour retention, organization-scoped). A successful replay returns the original JSON with Idempotency-Replayed: true; reusing a key with a different method/path/body returns 409 idempotency_key_conflict; reusing while the first request is still running returns 409 idempotency_key_in_progress.

Register a webhook endpoint via the dashboard or the /v1/webhooks API. uSwap signs each delivery with HMAC-SHA256 using your endpoint's secret and includes the timestamp + intent lifecycle event (created, matched, executing, completed, refunded, failed). Retries follow exponential backoff over 24 hours. Every delivery (including failures) shows up in the dashboard's Webhook Deliveries log for replay.

Yes — the recovery surface is part of the API, not a hidden support flow. If a user's deposit lands on the wrong network or amount, your integration can show them the same three buttons the uSwap.net UI shows: market-replace at the current rate, hold for manual review, or refund to a different address. The intent lifecycle webhook fires on every state transition so your UI stays in sync.

Not yet — by design. The OpenAPI 3.1 spec at /v1/openapi.json generates clean clients in every major language (openapi-typescript, openapi-python-client, oapi-codegen for Go, etc.). Most partners are running on generated clients within an afternoon. A first-party TypeScript SDK is on the roadmap once the surface stabilizes — we'd rather lock the spec than ship an SDK we have to deprecate.