SDKs
Official client libraries for five languages. Each SDK wraps the GeckoGuard API, signs requests, and verifies nonce-bound Ed25519 responses for you. See the response verification contract when implementing a direct REST client.
The package registries are not live yet. The install guides use checksummed historical v1.3.0 preview artifacts while the first coordinated official release, v1.0.0, remains on hold.
| Language | Package | Guide |
|---|---|---|
| JavaScript / TypeScript | @geckoguard/sdk | Guide |
| Python | geckoguard | Guide |
| C# / .NET | GeckoGuard | Guide |
| Go | github.com/GeckoGuard/GeckoSDK/go | Guide |
| C++ | header-only, CMake | Guide |
For the full request/response shape of every endpoint, see the API Reference.
API keys
Every SDK call authenticates with a product-scoped API key. Generate one in the dashboard under Products → [product] → API Keys and scope it to what the client actually needs — license:authorize is the minimum for desktop clients. Never ship a write-scoped key.
Save the key's one-time signing secret at creation and supply it to the SDK as shown in each quick start. The hosted API requires request signing. For long-running applications, follow the session lifecycle and heartbeat requirements.