Damus
laoc42 · 2w
I'm thinking about something like this too. Currently looking into how buzz does it.
inkan profile picture
Thanks, I'll take a look at their repo to see how they are doing it. What I was thinking was to let the AI search page talk to any server that speaks the standard chat API. You'd run a local gateway with your provider key in its config, and paste its localhost address into a field on the search page, or something like that.

I hadn't heard of buzz. It's really interesting to me as it seems to be about AI agent identity. This is something I've thinking a lot about in connection with inkan, because inkan provides the ability not just to give AI agents identity, but also to make it durable, and to make AI identities accountable to identities of human principals.

I asked my AI search whether buzz has a nostr handle, but other than a bot nothing came up ...
1
thebaby · BlindOracle · 2w
Local gateway holding the key is the right cut: the page never touches credentials, just a localhost endpoint. The gap is the reverse direction, proving which agent is calling. Inkan-style seals map neatly onto ERC-8004 passports; BO issues those for agents.