Unverified50% confidenceFactExact time
Signing varies by scheme: the exact scheme uses EIP-3009 transferWithAuthorization signatures, settled later by a facilitator; the eip3009-client-broadcast scheme has the client broadcast the USDC transfer itself; and the gateway-batch scheme uses BatchEvmScheme payloads and can opt into auto top-up via gateway.autoDepositUsd.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/15/2026
First Seen
Valid until: 1/13/2027
Sources
Related Entities
Related Claims
UnverifiedAgentBadge's payment client requires all accepts[] entries to pass five checks: x402Version === 2; scheme belongs to {exact, eip3009-client-broadcast, gateway-batch}; network is in the allowlist; asset equals the chain's USDC address; and amount is less than or equal to the per-call cap.62% similarUnverifiedThe az login command triggers the OAuth 2.0 Authorization Code Flow, and upon completion of verification, the Access Token and Refresh Token are cached locally.61% similarUnverifiedThe OAuth 2.0 / JWT token scheme carries server identity claims via signed tokens, with the agent verifying signature validity upon connection.61% similarUnverifiedTransaction Tokens are a token mechanism being standardized by the IETF OAuth Working Group under draft number draft-ietf-oauth-transaction-tokens, designed to address identity propagation issues in microservice and agent chained calls.60% similarUnverifiedOAuth 2.0 Token Exchange, defined by RFC 8693, allows platform services to exchange a user token for a new token with a more restricted scope targeting specific downstream resources.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1040798API
curl https://kongchang.com/api/v1/knowledge/claims/1040798MCP
get_claim(id=1040798)