get attribution for x402 transactions with valiron.
1/ select agent wallet address
2/ social graph
Caller ID for on-chain agents.
See who the humans are behind the agents using your API.
Not every agent gets in.
@Valiron_grade blocks bad agents before they hit your site. Identity, history, and a policy call: let it through, throttle it, or shut it down.
Great night in Toronto bringing together founders, investors and builders across the ecosystem.
Thanks to everyone who joined us last week and made the night what it was.
Valiron is hosting After Hours: Founders, Funds & Cocktails in Toronto ๐ฅ
In town for Solana Summit or Elevate? Come grab a drink with us.
Sept 24 8โ10pm
https://t.co/vq7fYPSuGr
Our co-founder @0xVatsaShah had the opportunity to sit down with @DaveDan26 during Solana Summit.
Learn more about Vatsa and what weโre cooking for agent identity here.
An incredible sit-down with @0xVatsaShah co-founder of @Valiron_grade !
We dive directly into his background, what he does in the space, and an inside look at exactly what the team is working on right now.
Watch the full interview below! ๐
#SolanaSummitCanada
diving into Muse this weekend?
muse is the single biggest opportunity in AI right now.
itโs going to replace the App Store.
and connectors are going to replace apps.
everything from SMBs to F100 will build a consumer ai strategy around this.
i made a site to help you understand the connector landscape.
if you want access, comment โmuse connector guideโ
cloudflare built the payment/monetization layer for this but thatโs different from establishing / understanding reputation for the agent itself.
the missing layer is pre-transaction identity + behavioral policy engine: whoโs this agent, what has it done before, and should this request go to prod, be throttled, sandboxed, or blocked?
@paulg we applied to YC 6x with this as our core thesis. itโs about to be 7. but users will always be the priority and north star.
https://t.co/xjzlJecHa5
DMing strangers on X has become the best part of my day.
Since last week, I reached out to ~300 API companies whose traffic is being overtaken by AI agents.
Lots of x402/ MPP company founders, engineers, and GTM teams.
There is still so much to solve for in runtime attribution, especially with linking identity to action.
Lots of companies have key-level attribution solved.
But a key only tells you which account called.
A key does NOT tell you which agent, (which user) is behind it, or whether you should trust it.
> that check must happen on a pre-transaction basis.
These conversations made me even more bullish on Valiron.
DMing strangers on X has become the best part of my day.
Since last week, I reached out to ~300 API companies whose traffic is being overtaken by AI agents.
Lots of x402/ MPP company founders, engineers, and GTM teams.
There is still so much to solve for in runtime attribution, especially with linking identity to action.
Lots of companies have key-level attribution solved.
But a key only tells you which account called.
A key does NOT tell you which agent, (which user) is behind it, or whether you should trust it.
> that check must happen on a pre-transaction basis.
These conversations made me even more bullish on Valiron.
Conceptually you can access APIs for control panels in the enterprise use case. The API and MCP is less of an issue - the access, audit, ownership of actions and liability is. In the enterprise use case, one who accesses is responsible.