i liked the 1-2 punch of bankr + @quidli so much that i bolted bankr tools onto Disco- & TeleCentaur 🤖🦑link your bankr + quidli keys so that your agent can swap/buy a token & send it to your contacts by their social handles, all from a single prompt on Discord or Telegramdefi taken care of by bankr, agentic payments on top of socials by quidli, all by a bot you host yourself

experimenting with social based agentic payments for invoices this morning - integrated this flow into our discord via discocentaur (of course, built on top of @quidli):operator receives invoice from vendor > operator uploads invoice + acknowledges services rendered to agent > agent reviews file, validates details w/ operator > upon confirmation (which isn't necessary but i included), agent executes payment in USDC to vendor tied to the email address provided on invoice (no wallets or web3 tutorials required)obviously the recipient needs to be ok with receiving payments onchain, but still pretty cool to stitch this all together end-to-end in less than an hour while drinking coffee

wired up bankr + @quidli on claude code - pretty fun to watch the agent use all the tools at its disposal to send some $BNKR to the most recent contributors to bankrbot's open 'skills' repo on githubmy prompt: "buy 2 USDC of BNKR and send 100 BNKR to everyone that's contributed to https://github.com/BankrBot/skills this past month"agent proceeds to use my bankr account to swap for BNKR, then resolves all the qualifying contributors on github to wallets generated for those users via quidli and sends BNKR to my quidli smart wallet to execute the payments directlyonly hitch was a miscalculation on the price of BNKR so the agent paused to ask me for permission to spend more (which it ended up not doing because it realized its error) 🤣

reminder that @quidli/connect-mcp is an mcp server that resolves social handles to evm & solana wallet addressesadd it to your app, client or agent and it can:- resolve social handles (farcaster, x, github, discord, telegram, linkedin, email and or phone number) to evm & solana addresses
- generate new wallets for social handles that have none configured
- run reputation checks on accounts before executing onchain txs
- autonomously send tokens to verified accountsopen repo:

fyi, you can build most of this very easily with @quidli connect, even self-host the whole thing if you'd rather not trust anyoneyour email/social handle of choice is just so you can authenticate + no banking details at allrun it hosted or locally, your keys, your wallets, try it out: `npx -y @quidli/connect-mcp`

btw, this means SOL & SPL sends are available on DiscoCentaur & TeleCentaur setups too! 🙌so you can now run your own locally hosted multiplayer agentic payments directly in discord & telegram group chats on select evm chains AND solana, all powered by @quidli connect 🦑🦑🦑feat. kimi via openrouter wired up on telegram via TeleCentaur

solana transactions are now native on @quidli/connect-mcp 🦑🤖🦑/lookup has always returned a SOL address next to the EVM one, but actually transacting on Solana was up to you to build yourself. now it takes one call from your agent to send SOL or SPL tokens, with nothing additional to wire up.try it: npx -y @quidli/connect-mcp

we updated the @quidli connect API + MCP so that the `connectme` & `connectlookup_exposed` tools return connect profiles, socials, wallets and reputations in a single call for all agents & operators whenever necessarythen i wired it into DiscoCentaur (& TeleCentaur too) so that all agents in our discord can identify who's who in the server by reading the MCP, while what i've kept private stays private

btw, with an api key no longer necessary to get started with https://mcp.connect.quid.li, @quidli connect is now also accessible from https://grok.com, albeit in limited form 🪐🤖🦑tools like /lookup & /score (reputation) work well so you can have grok research the social handles you come across and any publicly associated reputations they may have (peep my lens score 🤣)but no personal configurations or onchain txs can be performed because your agent is not linked to your own quidli account, which requires api key config for authentication

small but useful addition to the @quidli connect readme 🦑if you're running npx -y @quidli/connect-mcp from a background service (launchd, systemd, etc.), it can hang indefinitely with no output because npx's PATH resolution doesn't behave the same outside an interactive shellyou can now use bunx as a workaround, same job without that hangfull writeup + config example in the troubleshooting section: