Skip to content

Products

Profile

Your account hub and the system of record for organizations — across Forge, Market, and Auto, hosted and self-host.

AgentKitProfile (profile.agentkitproject.com) is two things: your account hub and the system of record for organizations. One account works across Forge, Forge, Market, and Auto — on hosted and self-hosted installs alike.

Your account

  • Display name — your public-facing name, used as the publisher identity when you submit kits to the Market.
  • Handle — a unique username; your public profile lives at /u/<handle>.
  • Security — manage your sign-in and sessions.
  • Connected apps — an overview of your access across Forge, Market, and Auto.
  • Avatar initials and a verified flag.

Organizations

Profile is where organizations live: create a team, manage members and roles (owner / admin / member), invite people by email, set the org's shared Anthropic API key, and govern spend with a per-run budget override and monthly usage limits. Market still owns kit ownership and visibility, but resolves org membership from Profile. See the Organizations guide for the full picture.

Why it matters for Market

The Market uses your Profile display name as the publisher identity. When you submit a kit, your publisher snapshot (display name, handle, avatar initials, verified) is frozen into the submission and onto the published kit. A display name is required to submit — set it in your profile before submitting.

Privacy boundaries

  • Public browsing of the hosted Market is open; downloads require an account.
  • Email addresses are private.
  • Raw user IDs are never used as public display names.

Sign in

The web apps use WorkOS AuthKit cookie sessions in the browser (or your own OIDC IdP on self-host); Forge and the CLI use device authorization. See Signing in and the architecture overview for how the auth paths stay separate.