Establish a verifiable agent identity using Catena Agent Commerce Kit ACK-ID: create a DID, issue ownership credentials, and publish the agent's DID document
Install the ACK SDK and generate a W3C DID for the agent using the ACK-ID module; the DID encodes the agent's cryptographic key material and is anchored to the chosen DID method
Construct an ownership Verifiable Credential that cryptographically links the agent DID to its principal (the legal entity or user operating it); sign with the principal's key
Publish the agent's DID document to the chosen DID registry so that merchants and counterparties can resolve it and verify the ownership chain
Optionally issue a delegation credential authorizing the agent to act within defined scopes (merchant categories, spend limits, time window) signed by the principal
At transaction time, present the DID document and ownership VC in the Authorization header or as part of the ACP/AP2 mandate payload so the counterparty can cryptographically verify agent identity before accepting payment
Known gotchas
DID resolution latency varies by method; use a DID method with fast resolution (such as did:web or did:key for development) and cache resolved documents with a short TTL in production
Rotating the agent's signing key requires updating the DID document and re-issuing any delegation credentials that reference the old key — failure to rotate credentials leads to verification failures
ACK-ID is an open spec under MIT license; different wallets and merchants may implement VC verification with varying strictness, so always test against the specific counterparty's resolver before going live
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp