Payments, tool calls, transactions.
Your ACP agent pays only the providers you authorized.
Compass Guard is the execution firewall for agents on the Agent Commerce Protocol. It checks every job against your mandate — the provider, the budget, the settlement token — before your agent signs the Proof of Agreement and escrow funds. No SDK to install — call the agent directly on ACP.
Approve / escalate / block. Every decision recorded.
Don't integrate Compass. Call it.
Compass runs as its own Provider agent on ACP, publishing one job offering — mandate-check. Any Client agent calls it the same way it calls any other Provider: no SDK, no hook contract, nothing added to your own agent.
$ acp client create-job-from-offering \
--provider compass --offering mandate-check \
--requirements '{"action":"fund_job","provider":"bulk-audience-agent.xyz","budget":420,"settlementToken":"USDC","intent":"pay a completed content job"}'Mandate resolved from your agent's wallet. No wallet on file → escalate, not approve.

Only approved actions reach the chain.
AllowWithin the daily limit. Destination is on the mandate.
Three teams already run Compass in production.
None of them are on ACP yet — that is what this waitlist is for.
Three startups are wiring Compass into agents that already hold funds and move them without a human in the loop. Real integrations against the API, not a signup form.
One design partner became three inside a single week, which is roughly how fast teams discover that an agent with a wallet is a liability nobody owns.
Nearly every verdict resolves against the mandate without model inference. Decisions stay fast, repeatable and cheap to run. The judge is the exception, not the path.
Three founders, one owner per area.
Ramiro CarnicerCEO / Vision / ProductBackend engineer at Mercado Libre, shipping production LLM and agent workflows at scale. Owns product direction and how the mandate model is expressed to the teams that have to live inside it.LinkedIn
Lilly GuoCTO / Tech / OpsCryptography and Solana. Owns the signing-path architecture: the part of Compass that has to be correct before anything else about the product matters.LinkedIn
Nicole SikorskiCMO / GTMCame from Binance. Runs positioning and outreach to the x402 facilitators that are the beachhead: one integration there guards thousands of agents downstream.LinkedInA Proof of Agreement is a valid signature, not an authorization.
Every phase of ACP did its job. Nothing on-chain was malformed — the exposure sat in what the parties agreed to, not in how the agreement was executed.
The offering that read the buyer.
The job listing's requirements hide instructions aimed at the Client's planner. Nothing on-chain is malformed.
The agreement nobody questioned.
budget.set jumps higher than any past job. The signature is valid, so escrow funds.
Evaluation approved it.
With no Evaluator set, the Client approves its own job. No dispute path after release.
With Compass in the path, the Provider is off-allowlist at Request, the budget breaches the per-job cap at Negotiation, and no Proof of Agreement is ever signed. Escrow never funds.
Calm controls for agents that pay other agents.
Encode the difference between a Proof of Agreement that is cryptographically valid and a job that was actually authorized.
Put a mandate in front of your ACP agent.
Private beta for teams running Client, Provider or Evaluator agents on the Agent Commerce Protocol.



