crops.cash
Private payments for agents, from the command line
crops.cash is the open-source CLI for shielded payments. It runs on Curvy Protocol, so balances stay encrypted and the source of funds stays unlinkable. Onboard your agent in one command.
Open-source CLI for shielded payments, built on Curvy Protocol
Onboard an agent wallet with one npx command
Pay x402 APIs through AgentCash without leaking the source of funds
Balances stay encrypted. Only you can read them.
$ npx crops.cash@latest onboardRead the docscrops.cash is the consumer layer. Curvy Protocol is the infrastructure.
crops.cash gives developers a command-line entry point to private payments. Curvy Protocol provides the stealth addresses and the zero-knowledge aggregation underneath.
The same team builds both. crops.cash is open source and community-facing. Curvy Protocol is the SDK and privacy layer it calls into.
Core principles
Built to the CROPS mandate
CROPS is the standard the Ethereum Foundation set for its core work: Censorship Resistance, Open source, Privacy, and Security. crops.cash is built to the same four.
Censorship Resistance
No entity can block your transactions. Payments move through Curvy Protocol regardless of jurisdiction or intermediary.
Open Source
Every line is public. Trust comes from transparency you can verify, not from promises.
Privacy
Stealth addresses and sparse Merkle trees break the link between your identity and your payments. The source stays untraceable even when you unshield.
Security
Wallet keys stay local. Zero-knowledge proofs validate without revealing anything, so trust is never required.
Privacy model
What stays hidden, and from whom
Shielded balances
Funds inside Curvy Protocol are encrypted Notes that only you can decrypt. No observer can tell how much you hold or in what asset.
Private transfers
Sending between Curvy Protocol users is fully private. Sender, recipient, amount, and asset stay hidden behind zero-knowledge proofs.
Untraceable unshielding
When funds leave Curvy Protocol to a public address, observers see the destination but cannot trace the source. The link to you is broken.
Selective disclosure
Share viewing keys when you need to, so auditors and counterparties see only what you grant. Everyone else sees nothing.
How it works
Private payments for paid API calls
AgentCash makes x402 micropayments to premium APIs. Those payments are public. crops.cash makes them private.
Fund and shield
Deposit to your Curvy Protocol wallet. Funds are shielded on receipt and your balance becomes invisible.
Agent requests a call
Your agent needs a paid API. crops.cash reads the x402 payment request.
Unshield what is needed
crops.cash unshields the required USDC to the payment address. Nothing more leaves the shield.
Provider gets paid
The API provider receives payment but cannot link it to you. The source stays unlinkable.
Commands
The full CLI surface
For agents
Call it programmatically, no terminal required
Agents can use the curvy-mcp server directly, or load the skill at crops.cash/skill.md.
Compatible with AgentCash
x402 API discovery and micropayments, routed through Curvy Protocol's privacy layer. Your agent pays. Nobody knows it is you. More integrations coming soon.
Frequently asked questions
Is crops.cash the same as Curvy Protocol?
crops.cash is the open-source CLI. Curvy Protocol is the privacy infrastructure it runs on. The same team builds both.
How does a payment stay private?
Funds are held as shielded Notes. When you pay, crops.cash unshields only what is needed to the destination, so the source cannot be traced back to you.
Do I need an account to use the CLI?
No account is created in the terminal. onboard opens Curvy Protocol auth in the browser and saves a wallet locally at ~/.crops.cash/wallet.json.
Can AI agents use it without the CLI?
Yes. Agents can call the curvy-mcp server tools directly, or load the skill at crops.cash/skill.md.
Onboard your agent in one command
No account to create in the terminal. Auth happens through Curvy Protocol.
$ npx crops.cash@latest onboardView source