{"agent_auth":{"access_token_ttl_seconds":21600,"assertion_ttl_seconds":3600,"claim_endpoint":"https://api.exchange.et/api/v1/agent/identity/claim","claim_ttl_seconds":1800,"events_supported":["agent_registered","agent_claimed","credential_revoked"],"identity_endpoint":"https://api.exchange.et/api/v1/agent/identity","identity_types_supported":["anonymous","identity_assertion","service_auth"],"signing":"HS256 self-issued (symmetric AGENT_AUTH_SECRET); no public JWKS keys"},"grant_types_supported":["urn:ietf:params:oauth:grant-type:jwt-bearer","urn:workos:agent-auth:grant-type:claim"],"issuer":"https://exchange.et","revocation_endpoint":"https://api.exchange.et/api/v1/oauth2/revoke","revocation_endpoint_auth_methods_supported":["none"],"scopes_supported":["rates:read"],"service_documentation":"https://exchange.et/auth.md","token_endpoint":"https://api.exchange.et/api/v1/oauth2/token","token_endpoint_auth_methods_supported":["none"],"x_standards_profile":"RFC 8414-style discovery for the exchange.et agent-auth JWT-bearer-only profile \u2014 not a full OAuth 2.0 authorization server. No authorization_endpoint and no authorization-code / implicit response_type flow exist; the jwt-bearer and claim grants are exchanged directly at the token endpoint, so response_types_supported is intentionally omitted."}