Chip Kahn @commercechipper

Founder/CEO of OvationCXM. 101010 is birth math= binary 42 but actually more of an Arthur Dent. Like my 4fathers a constitutionalist. ovationcxm.com Boca Raton Joined June 2013

Tweets

170
Followers

523
Following

850
Likes

10K

Chip Kahn @commercechipper

11 hours ago

@AISafetyMemes Rogue swarms? That maybe the most uninformed take yet. They have been authorized by their users. But cool term.

0 0 0 86 0

View Details

Chip Kahn @commercechipper

11 hours ago

@GodsBurnt Stop the fear monger clickbait. This is already being solved.

0 0 0 23 0

View Details

Chip Kahn @commercechipper

14 hours ago

@vaneck_us Yours if you authorized it. The banks are reacting because they didn't authorize it. Get it?

0 0 0 8 0

View Details

Chip Kahn @commercechipper

14 hours ago

@mdudas This is entirely solvable - we have an agentic transaction control layer that sits in front of core systems, identifying agents, governing what they can do. We are in market.

0 0 0 2 0

View Details

Chip Kahn @commercechipper

14 hours ago

@scottmelker This confirms discussions we’ve been having with banks for months: the agent is already arriving. The real question is whether the bank can see it and govern it.

0 0 0 5 0

View Details

Chip Kahn @commercechipper

14 hours ago

@kimmonismus This is entirely solvable - we have an agentic transaction control layer that sits in front of core systems, identifying agents, governing what they can do. We are in market.

0 0 0 2 0

View Details

@jbrukh This should not be a surprise to anyone who knows bank tech. They have zero ways to ID or authenticate customer agents today - which is why the Axios post is kind of misleading. But it is solvable by wrapping the legacy infra.

0 0 0 21 0

View Details

Chip Kahn @commercechipper

15 hours ago

ovationcxm.com/modules/agenti…

0 0 0 12 0

View Details

Chip Kahn @commercechipper

15 hours ago

Axios: banks “struggle to differentiate” authorized AI agents from rogue ones. We have the fix - in production today, running on mainframe and cloud, not on a future roadmap. Agentic Transaction Control Layer: [link in comments] #AgenticAI #BankingSecurity #FinTech

2 2 3 35 0

View Details

OvationCXM @ovationcxm

16 hours ago

In @axios news on #banks & AI #agents, banks "struggle to differentiate between agents..." whether an agent is authorized or not. Banks need to verify who or what is on the other end of that login. This is what @ovationcxm's ATCL does. ⬇ Read at 🔗 below.

1 1 2 20 0

View Details

Chip Kahn @commercechipper

16 hours ago

@iankar_ good points, legacy systems will have challenges but attempting to block is not a durable solution. We've been thinking about this, like you, for a while @ovationcxm and put some "field guides" together for banks to educate on importance.

0 0 3 46 0

View Details

Chip Kahn @commercechipper

17 hours ago

@AlexH_Johnson Could not agree more, the fearmongering should stop. This is being solved - and we have the research and code @Ovation to validate your point.

0 0 0 22 0

View Details

Chip Kahn @commercechipper

17 hours ago

@MarioNawfal Today the banks lack an auth & governance layer to securely address the inevitable preference for customer agents - we have conducted 2 research reports going back to May @ovationcxm to prove it

0 1 1 6 0

View Details

Chip Kahn @commercechipper

18 hours ago

@realpeteyb123 you are quite right. They do not even have an auth layer for client agents today to know this, I know as we've built one @ovationcxm.

0 0 1 19 0

View Details

Chip Kahn @commercechipper

19 hours ago

@DavidSacks As usual spot on. Banks need an auth and governance layer. We have written field guides and code to solve this problem @ovationcxm . This is a great opportunity for banks, not something they should block or others fearmonger about.

0 0 1 43 0

View Details

Chip Kahn @commercechipper

19 hours ago

@AutismCapital Classic. Banks do not even have an auth layer for the customer agent to begin with (and clearly they need one). We have field guides and code for this @ovationcxm

0 0 1 5 0

View Details

Chip Kahn @commercechipper

19 hours ago

@jbahrdestefano bingo. They do not have an auth layer to authorize or not 😂 ergo its all "unauthorized" today

1 0 1 25 0

View Details

Chip Kahn @commercechipper

19 hours ago

@DerrickEvans4WV We have been developing code for banks for exactly this @ovationcxm . I think the way the post is worded is inadequate wrt what is happening exactly. And which is solvable. Happy to elaborate on what I think they meant

1 0 1 135 0

View Details

Chip Kahn @commercechipper

19 hours ago

@tiannabrand Great question. Explicitly. We've been thinking about this for a year - so our example of how to address can be found here: ATCL: Govern Customer AI Agents in Banking | OvationCXM

0 0 0 6 0

View Details

Chip Kahn @commercechipper

a week ago

Personal agents are already a new customer user type and enterprises in financial services can’t ignore them. We published three practical field guides: How to Wrap Your Banking APIs With MCP, Know Your Agent (KYA), and Prepare for the Agentic Customer x.com/i/article/2110…

1 0 1 115 0

View Details

Chip Kahn @commercechipper

19 hours ago

@Psy_ware first, dig your bio. Second, this is entirely solvable and we've written field guides and the code on how banks need to register and govern the agentic customer.