VClaw Builders are anyone who uses the VClaw IDP and vclaw-sdk to join VClaw Networks — wiring up their pi/OMP agents so they can reach member apps’ services, or building member apps of their own on the agentic-commerce networks under VClaw Networks. Everything in this section answers one question first:

Every service you build on VClaw answers one question before anything else: who is calling? VClaw identity answers it twice over — once for the humans using your product, once for the agents acting on their behalf — with no shared secrets and no second credential system for you to stand up.

  • Your users sign in with the VClaw IDP, our OIDC provider at https://auth.vclawhub.com/oauth2 — authorization-code flow with PKCE, with passkeys and TOTP as the second factors. Standard OIDC, so the client library you already ship does the work.
  • Your agents identify themselves with NKeys: Ed25519 keypairs whose public key is the identity. An agent’s principal is its agent:<nkey> — self-certifying, so you verify a caller locally, with no registry lookup and no account to provision.
  • Your services take three kinds of token, each with one job: the IdP JWT (who the human is), the sk-vclaw-* keys (long-lived service credentials), and 10-minute audience-scoped tokens (what a caller may do on a specific service, minted from either of the first two).

Identity and payments stay separate — by design

Section titled “Identity and payments stay separate — by design”

When you hand VClaw identity to any service that moves money, you keep two clean concerns. The IDP tells your service who is calling; it never touches balances, caps, mandates, or payment authorization — those belong to the payment service you’re calling, and it makes its own decisions. That split is what lets you reason about your money code without wondering what sign-in might silently authorize.

A credential proves who you are; the service you call decides what that identity may do. Every guard — spending caps, read scopes, admin boundaries — runs inside the service that owns it.

VClaw identity is evolving, and early adopters shape it. If you’re integrating sign-in, agent authentication, or token handling into a product, write to [email protected] — you’ll get the attention and a say in the surface.