SDKs

Install the SDK. Generate the agent project.

Use the SDK for your runtime, or let Builder generate a ready-to-run Python or Swift project with the manifest, context scopes, and sandbox checks already wired in.

Generate agent project Install SDKs

Available now

Pick the SDK that matches where your agent or user surface runs. SDK downloads are available to signed-in builders.

Python SDK

Available

Use this for Python agents, Google ADK, MLX, BYOC services, and cloud BYOK runtimes.

Download, unzip, then pip install -e .

HusshKit

Available

Use this for Apple app surfaces, typed platform calls, auth/session handoff, and Agent One sandbox testing.

Download, unzip, then add the package in Xcode

HusshMessagesKit

Available

Use this for iMessage request payloads, broker authorization, and consent proof flows.

Download Swift SDK, then import HusshMessagesKit

HusshKit Quickstart

Start with a platform-backed call.

HusshKit does not mock consent, PKM, or Agent One locally. Your app provides the user session, then HusshKit makes typed calls to the Hussh platform. For agent testing, download a Swift package from Builder or Registry and run it through Agent One/Nav sandbox.

Download HusshKit

SwiftPKM manifest

import Foundation
import HusshKit

let platform = husshPlatform(
    endpoint: URL(string: "https://dev.hushh.ai/api")!
)
let client = HusshPlatformClient(configuration: platform)

let session = StaticHusshAuthSessionProvider(
    session: HusshAuthSession(
        userID: "user_123",
        accessToken: "short-lived-hussh-token",
        expiresAt: nil,
        tokenKind: "firebase_id"
    )
)

let services = HusshPlatformServices(
    platformClient: client,
    authSessionProvider: session
)

let manifest = try await services.pkm.manifest(
    domain: "financial"
)

Swift sandbox and production boundary

HusshKit is usable today for platform-backed sandbox work. Production distribution still goes through the same agent review, runtime registration, and consent checks as every other Hussh runtime.

Sandbox today

Download Swift agent packages, run Agent One/Nav conversations, approve consent, and execute local Swift business logic through platform jobs.

App surfaces today

Use HusshKit for typed platform requests, auth/session handoff, PKM metadata reads, iMessage payloads, and broker authorization helpers.

Production later

Marketplace certification, production runtime registration, production consent policy review, and app-store-ready native handoff remain review-gated work.

Download agent code from Builder.

Builder turns your idea into a Python or Swift project zip. It includes the generated agent, manifest, Hussh config, project metadata, README, validation report, and sandbox run command.

Open Builder

Describe the agent

Add context domains

Run sandbox checks

Package and download

Use Hussh MCP from your coding tool.

After you sign in, Builder exposes the Hussh build workflow to MCP-capable tools. Your coding tool can scaffold, scope, validate, test, package, and register the agent.

Codex

Cursor

Claude Code

Windsurf

Antigravity

Any MCP-capable tool

What every SDK protects

The point is not just calling an API. The SDK keeps consent behavior close to the agent code.

Ask Nav for approved context.

Stay useful when a user limits access.

Respect consent receipt TTL, purpose, retention, and revocation.

Record what happened for review and trust.

Planned SDKs

TypeScript SDK

Planned

Web shells and typed consent helpers.

npm install @hussh/sdk

Kotlin SDK

Planned

Android consent surfaces and mobile integrations.

implementation("ai.hussh:sdk")