Optionalauth_Optionaloauth_OAuth tokens for dynamic authentication The client will automatically refresh tokens when they expire
Optionaloauth_OAuth client registration info Stored after dynamic client registration
Optionaloauth_OAuth 2.0 client credentials grant configuration (M2M).
When present, tokens in oauth_tokens are refreshed by re-exchanging
these credentials against token_endpoint — there is no user-facing
authorization flow.
OptionalheadersAdditional HTTP headers to include in every request to this agent. Useful for sending API keys, org IDs, or other vendor-specific headers alongside the standard authorization token.
Example:
headers: {
'x-api-key': 'quota-key',
'x-org-id': 'org-123'
}
Optionalrequest_Optional — when set, outbound requests to this agent are signed per
RFC 9421 for operations the agent advertises in its request_signing
capability block (fetched once via get_adcp_capabilities and cached
by the client). See AgentRequestSigningConfig.
Static authentication token Use this for API keys or pre-issued bearer tokens