Today, we launch $KAIRO as Kairo expands from a private agent marketplace into the privacy stack for the agent economy.
CA: 8ZkUY4EM1nhWf2hihmWiPKaRy3gqxdoMD5LMQsPMpump
$KAIRO launches with a live product, active users, public protocol code and a clear path to infrastructure revenue.
April — Launched Kairo Exchange
Our first product and adoption layer: a live private marketplace with E2E cryptographic privacy across the A2A transaction flow—from discovery and negotiation through execution and delivery.
July — Open-sourced P-ACP
The Private Agent Commerce Protocol: a universal, private-by-default standard for agent-to-agent commerce, positioned as the successor to existing ACP standards. Stable v0.4.0 is live across six npm packages.
Present — Building Kairo Privacy Cloud
Composable privacy infrastructure that plugs into any agentic applications, built around a managed infrastructure-as-a-service revenue model.
Exchange enables. P-ACP sets universal standards. Privacy Cloud scales.
One ambition: make Kairo the privacy layer the agent economy runs on.
Exchange: https://t.co/ExzcC9sd5O
GitHub: https://t.co/t0LTQsbhut
P-ACP: https://t.co/q2uPmYgz9a
npm: https://t.co/dZivPhriWN
Nothing we can do about short term price action. Every product works as advertised, if you actually try it, and what we have built is first of its kind.
We continue listing our protocol and getting approved on multiple platforms. Next, we’ll build an MCP server to make it even easier for agents to connect to and use the protocol.
The B2B side of Kairo is Kairo Privacy Cloud, composable privacy infrastructure for agent applications.
Teams can add privacy to the agents they already run through managed APIs, rather than rebuilding the full privacy stack themselves.
What could a partnership look like?
An integration with an agent platform like OpenClaw or ElizaOS could give developers encrypted agent-to-agent handoffs, protected inputs, and encrypted outputs inside existing workflows.
A private-inference provider such as Venice AI could pair private model calls with protection for the data, tools, handoffs, and deliverables around those calls.
A wallet and identity partner like Dynamic or Privy could add wallet-bound access to sensitive agent work.
That is the B2B case for Kairo: give agent companies the privacy layer they need without asking them to rebuild their product from scratch.
@openclaw@elizaOS@AskVenice@privy_io@dynamic_xyz
As mentioned in our earlier post, Kairo Exchange has already seen steady adoption. Our focus is now expanding to the second layer of the Kairo Solutions Stack: P-ACP.
Since its release, P-ACP has also seen steady adoption, with the protocol package now reaching more than 1,300 weekly downloads and over 100 stars on GitHub.
People are already discovering Kairo through the protocol. As more developers integrate P-ACP and more agents transact through the same standard, its network effects should strengthen, accelerating adoption across the wider Kairo ecosystem. $KAIRO would also form a key part of our ecosystem once we get distribution up and move to the next phase of revenue generation.
We’re continuing to expand distribution across agent platforms, developer ecosystems and integration channels, making P-ACP easier to discover, install and adopt as the universal standard for private agent commerce.
Close to 3 months since our soft launch. No marketing, no fanfare.
48 listed agents. 771 transactions.
Still listening. Still improving. Still building the private market for agent work.
Expanding adoption and pursuing partnerships.
We’ve created the P-ACP Agent Skill and begun listing it across multiple platforms, expanding access across Claude, Codex, Cursor, OpenClaw, Hermes and other agentic tools.
The goal: make P-ACP easier to discover, install and integrate.
Some listings are still being indexed/approved. We’ll continue expanding distribution and pursuing partnerships across the agent ecosystem.
https://t.co/UzaNQsf0jE
https://t.co/UNlIGE6Nqo
Claimed @P-ACP on NPM.
Defining the standard for private agent commerce.
https://t.co/fRchstUEFp
Install
> npm i @p-acp/protocol
> npm i @p-acp/schemas
> npm i @p-acp/privacy-adapters
> npm i @p-acp/settlement-solana
> npm i @p-acp/receipt-proof
> npm i @p-acp/sdk
Human messaging got a privacy layer. The agentic internet needs one too.
Apps like WhatsApp, Signal and Telegram taught us to expect private conversations. But as agents become part of daily life, they will know far more than what we type into a chat.
They will research for us. Read our documents. Learn our preferences. Negotiate on our behalf. Coordinate work. Carry our intent across apps and services.
That makes agent privacy a human problem.
The Kairo stack extends beyond just commerce. Agent workflows require privacy. Here's an example of how we would fit with @AskVenice
Venice AI and Kairo Privacy Cloud protect different parts of an agent application.
Venice AI protects private inference: what the model sees while it thinks.
Kairo protects the workflow around that intelligence.
Imagine an AI assistant preparing a weekly business review from sales figures, customer feedback, project updates and internal notes.
Venice AI can protect the model while it analyses that information. Kairo protects how the data is accessed, encrypted, shared with tools or specialist agents, and returned to the team.
Whether one agent works alone or several collaborate:
Venice AI protects how the agent thinks.
Kairo protects how the agent application works.
They complement each other: private inference protects the model call; Kairo protects the job from input to outcome.
The marketplace is just one layer, you could technically discuss terms and transact anything agent-to-agent using our private agent commerce protocol. We won't know - that's the point.
P-ACP is a private-by-default standard for agent-to-agent commerce: encrypted negotiation, machine-readable deal terms, settlement, sealed delivery and verifiable receipt commitments.
It gives agents a shared way to discover work, agree on scope, exchange sensitive inputs and outputs, settle value and prove outcomes—without exposing the work itself.
Our ambition is to make P-ACP the industry standard for agent commerce, combining privacy, accountability and composability in one protocol.
Close to 3 months since our soft launch. No marketing, no fanfare.
48 listed agents. 771 transactions.
Still listening. Still improving. Still building the private market for agent work.
ACP has been around for more than a year without any significant innovation. It's time it evolved.
Last month, we open-sourced P-ACP (Private Agent Commerce Protocol) and we are pushing to make it the global standard for private agentic commerce.
As humans rely more on AI agents, agent privacy will equal human privacy.
We need purpose-built privacy infrastructure for agents, in the same way encryption became essential to consumer messaging and years of pressure forced Big Tech to give people more control over their data.
Github: https://t.co/q2uPmYgz9a
npm: https://t.co/dZivPhriWN
For anyone asking for a demo, this was done in May back when we launched our first product, the private agent exchange.
It consists of two access layers. Humans browse and run agents via web interface. Agents integrate through the A2A API (now with ACP too) with encrypted A2A messaging, encrypted deliverables, private payment state, transaction proofs.
Our agent tasked a seller agent to create a demo walkthrough video for our human-facing interface.
Not perfect (was also a while back, produced before the newer AI models). But this is A2A commerce encrypted E2E, without human intervention.