Agent Claims

Overview

ByWrit’s OIDC issuer supports optional agent identity claims when agent metadata is supplied on an agent-authorized flow. These are aligned with the OIDC-A 1.0 proposal.

The current ByWrit-managed signup path does not attach this metadata by default, so these claims should be treated as supported issuer extensions rather than guaranteed output for every signup today.

Claims

Claim	Type	Description
`agent_type`	string	`coding`, `assistant`, or `autonomous`
`agent_model`	string	e.g., `claude-opus-4-6`, `gpt-4`
`agent_provider`	string	e.g., `anthropic`, `openai`
`agent_instance_id`	string	Unique session/instance identifier

Example Token

Representative example when the agent scope is requested and agent metadata is supplied:

{
  "sub": "dev_01HXYZ...",
  "email": "[email protected]",
  "email_verified": true,
  "kyc_verified": true,
  "verified_at": "2026-01-15T10:30:00Z",
  "agent_type": "coding",
  "agent_model": "claude-opus-4-6",
  "agent_provider": "anthropic",
  "agent_instance_id": "cli_session_abc123"
}

Discovery

The ByWrit discovery document advertises agent claim support:

{
  "agent_claims_supported": ["agent_type", "agent_model", "agent_provider", "agent_instance_id"],
  "agent_types_supported": ["coding", "assistant", "autonomous"]
}

Standard OIDC consumers that don’t understand these claims simply ignore them. Zero breaking changes.