A TypeScript client built to the published architecture: a single adapter seam so venue API churn touches one file, session-key signing identity, 256-bit client-side idempotency, and an explicit unknown result status your agent is forced to handle.
§1Capabilities
Gives an agent a signing identity that is time-boxed and delegated: a session key registered by the account owner with an expiry. The key can trade; it structurally cannot withdraw — custody movements execute only to attested recipients. Revocation is expiry.
Enforces idempotency at the client: every action carries a 256-bit key generated and validated before anything leaves the process, so retries and crashes cannot double-submit.
Refuses to pretend. Results are settled, rejected, or unknown — and unknown is a first-class status with a documented recovery path, because "the request timed out" is not the same as "the order failed."
§2Design
The adapter seam. Nothing outside a single adapter file knows the venue API’s shape. When the backend evolves — and it has, mid-build — one file changes, not your agent.
BYO signer. The SDK never holds raw keys. You inject a signer — a session key, an HSM, a KMS handle — and the client uses it. Key custody stays your decision.
Fail closed. While the v2 engine write path relocates, submitIntent throws WritePathUnavailableError rather than guessing at an endpoint. Reads and the chain heartbeat work today.
§3Availability by tier
| Open | Full source, non-commercial license. |
| Pro | Write path enabled at engine-API launch; priority fixes. |
| Institutional | Commercial license, dedicated support channel. |
Indicative until launch.
§4 · Stated plainly
Alpha. Order submission is intentionally disabled until the v2 engine API is stable — the write path exists behind the seam and fails closed.