Plug the universal swap into your product.

Partners can configure disclosed per-quote affiliate fees subject to current caps and program terms. For eligible standard crypto-to-crypto routes, uSwap’s platform fee is currently 0%. The amount received can still reflect provider pricing or spread, blockchain network costs, market movement, and any selected confidential, fast, fiat, or affiliate fee. The quote displays the modeled breakdown before funds are sent. Floating or expired quotes may be recalculated. Settlement and available payout details appear in the partner dashboard.

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.

The API exposes available recovery actions and lifecycle updates. uSwap automates common underpayment, overpayment, late-deposit, re-quote, and refund cases. Some wrong-asset, wrong-network, provider-ambiguous, already-broadcast, or unsupported-token cases may require provider or operator review and may not be recoverable. Timing and deductions depend on the route, provider, and network.

Not yet. The OpenAPI 3.1 spec at /v1/openapi.json can be used with standard client generators. A first-party TypeScript SDK is planned after the surface stabilizes.