# Compliant Agent Operations

This guide covers how agents can present ProofPacks with selective claims (e.g. nationality, AML status) so regulated APIs can verify the agent is operating for a compliant user.

**Scenario:** A financial or regulated API needs to verify that an agent is authorized and that the user meets compliance requirements. The agent presents a ProofPack with the necessary claims; the API verifies via ProofPack without seeing full identity data.

For implementation, use Path 2 (JWS with claims) and the compliance pattern:

* [Path 2: JWS with claims (JavaScript)](https://docs.zipwire.io/tools-and-integrations/proofpack-agent-delegation/path2-jws-claims-javascript) — verify JWS and read claims (e.g. nationality, AML)
* [Common use cases → Compliance (KYC/AML)](https://docs.zipwire.io/tools-and-integrations/proofpack-agent-delegation/common-use-cases#5-compliance-kycaml-and-regulated-transactions) — KYC/AML transaction verification
* [ProofPack & Agent Delegation](https://docs.zipwire.io/tools-and-integrations/proofpack-agent-delegation) — full guide
* [ProofPack on GitHub](https://github.com/zipwireapp/ProofPack) — SDKs