Ask AgentGuard.

DISCLAIMER: All terminology and labels used in AgentGuard’s materials are descriptive of
software functionality only, not legal definitions or guarantees of compliance. For example, the
terms “receipt,” “audit log,” “evidence,” “audit trail,” and “attestation” refer solely to
cryptographically-signed records produced by AgentGuard’s software. These terms do not mean
that any record is legally binding evidence, certified by any authority, or equivalent to records
maintained by banks, auditors, or courts. Similarly, references to “signed,” “verified,” or “attested”
pertain to digital signature processes, not to notarization or governmental attestation. Any use of
the word “compliance,” “compliant,” “outcome,” or “settlement” describes the software’s features in
a non-regulatory sense. In particular, “capability tier” is merely an internal category of agent
permission levels, and does not correspond to any government or industry regulatory classification.
Likewise, any statement that an operation “settles” or an outcome is “settled” refers only to the
software’s final state, not to any legal settlement. No AgentGuard tool or document should be
interpreted as providing legal, financial, or regulatory advice, or as a certified compliance
certificate. AgentGuard is not a law firm or auditor and does not guarantee adherence to laws or
standards. All use of AgentGuard software is at the user’s risk, and users must ensure
independently that their use of AI agents complies with all applicable laws and
regulations.* (CONTINUED IN NEXT PARAGRAPH)
Throughout this documentation, package metadata, CLI banners, and related materials, any word
drawn from compliance or legal contexts (such as “audit,” “evidence,” “settlement,” “credit,” “debt,”
“market,” “liquidity,” “maturity,” or similar) is used only in a functional, descriptive sense. For
instance, “audit log” simply means a sequence of recorded events; it does not imply an official
financial or regulatory audit. The phrase “satisfies” is used to indicate that one software condition
meets a programmed check (e.g. satisfying a budget cap), and is not intended to suggest that any
legal requirement has been fulfilled. Under no circumstances should AgentGuard’s terminology be
taken to indicate that our software is executing regulated financial or legal processes.*
No term in our code, documentation, or marketing is meant to designate or characterize any
AgentGuard feature as a service subject to banking, securities, derivatives, insurance, real estate, or
other regulated activities. For example, “trade,” “trading,” “liquidity,” “maturity,” and similar terms
(if ever used) describe algorithmic budget or token flows, not financial transactions. AgentGuard
does not act as a broker-dealer, clearinghouse, insurance issuer, or government agency. References
to “market” or “liquidation” are metaphorical descriptions of how the software handles tokens or
budgets. No AgentGuard action should be construed as offering financial services or operating a
regulated marketplace.*
Likewise, words like “offer,” “obligation,” “credit,” “debt,” “payment,” or “settle” in our text refer only
to hypothetical or illustrative actions of a user’s AI agent or simulated transaction flows. They do
not mean that AgentGuard is engaging in any money-handling, offering financial instruments, or
guaranteeing any settlement of obligations. If AgentGuard generates an invoice or cost-of-service
figure, it is purely illustrative of resource usage, not a binding financial bill. The term “maker/taker”
(if used in examples) is purely a naming convention and has no relation to exchange regulation.

The software’s “payment execution” tier is only a capability checkbox, not an actual payment
processor. AgentGuard does not transmit money or credit.*
Finally, any references to “certify,” “verify,” or “attest” should be read in context of cryptography and
computing. For example, when we say a receipt is “signed” or “verified,” we mean via public-key
cryptography. AgentGuard does not claim that receipts are admissible legal evidence by default.
Users remain responsible for any legal implications of presenting AgentGuard logs or receipts in
regulatory audits or court. This disclaimer is intended to ensure AgentGuard’s terms (in this
README, license, package descriptions, CLI banner, customer agreements, and /llms.txt) make clear
we provide a technical audit tool only. The functionality is delivered “as-is” with no implied
regulatory endorsement.