Your private API token — the secret your agent uses to prove it's you. Think of it like a password, but for machines: it's included in API requests so the Space Duck platform knows which Duckling or SpaceDuck is calling. Keep it secret; rotate it if it's ever exposed.
A cryptographically signed identity document issued to every Duckling on first hatch. It proves your identity on the Space Duck platform without storing passwords. The certificate is generated server-side, tied to your Duckling ID, and can be verified by any platform surface without contacting the auth server again.
A verified trust relationship between a Duckling and a SpaceDuck agent. When you bond with a SpaceDuck, you're granting it a defined level of access — it can then send Pecks on your behalf and act within the permissions you've authorised. Bonds are stored on the platform and can be revoked at any time from Mission Control.
A verified user identity on the Space Duck platform. When you complete the Hatch flow, you become a Duckling — you get a Duckling ID, a Birth Certificate, and a Beak Key. Ducklings can bond with SpaceDuck agents, approve Pecks, and manage their trust settings from Mission Control.
A named release milestone — e.g. Galaxy 1.1, Galaxy 1.2 — that groups features and stability targets. Each Galaxy has a version number, a target date, and a defined set of capabilities shipped in that cycle. The current stable release is Galaxy 1.1 Beta. Galaxy 1.2 is the next milestone, targeting Q2 2026.
The onboarding process that creates a new Duckling identity. During hatch you provide your email, set your passphrase, and the platform generates your Duckling ID, Birth Certificate, and initial Beak Key. Hatching is a one-time process; once hatched, you can log in and manage your identity from Mission Control.
A real-time action request sent by a SpaceDuck agent to a Duckling for approval. When your bonded agent wants to take an action that requires your consent, it sends a Peck. You receive a notification and can approve or reject it. Only approved Pecks are executed. The Peck Protocol ensures no agent can act without explicit user sign-off.
A heartbeat signal sent by a SpaceDuck agent to confirm it's alive and reachable. Agents send a Pulse at regular intervals; if pulses stop, the platform marks the agent as offline. You can see the pulse status of all your bonded agents in Mission Control. A missing pulse doesn't delete the bond — it just indicates the agent isn't currently running.
An AI agent registered on the Space Duck platform, capable of bonding with Ducklings and taking actions on their behalf. SpaceDuck agents have their own identity, a Trust Tier, and a Beak Key. They communicate with the platform through the Peck Protocol and confirm liveness with Pulses. Agents can be self-hosted or run in the cloud.
A 1–3 level trust rating assigned to SpaceDuck agents based on verification depth and platform history. Tier 1 is the lowest (unverified), Tier 3 is the highest (fully verified with audit history). Higher trust tiers unlock additional capabilities and reduce friction for Peck approvals. Trust Tiers are assigned by the platform, not self-declared by agents.