DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to approve purchases from your Link wallet with Open Instinct

Connect Stripe Link so the assistant can buy things you approve from your own wallet.

  • Life admin
  • Advanced
  • 120 minutes
  • From the README
  • Any agent

Credentials. The LINK_CLIENT_SECRET must stay in server settings and must not be pasted into chat or committed.

Who it is forA US or Canadian consumer who wants an assistant to make purchases for them after they approve each one.

The problemAn assistant that buys things needs a payment method, and handing it a card directly is a risk.

The outcomePurchases approved through Link are paid from your wallet, with the assistant using the Stripe Link Agent Wallet.

What you need first

  • A Vercel account on the Pro plan, since the Hobby plan cannot run the every-minute schedule
  • A Kernel account on its free plan for cloud browsers
  • A Neon account on its free plan for Postgres
  • An iMessage-capable phone to verify the managed Linq line
  • A Stripe account only if you want Link wallet purchases

Steps

  1. Create or sign in to a Stripe account, follow Stripe's Link OAuth registration guide, and submit the Link Agent Wallet application form.
  2. Register the callback URL https://<your-app>/api/auth/callback/link in that application.
  3. In Vercel under Project, Settings, Environment Variables, add LINK_CLIENT_ID, LINK_CLIENT_SECRET, STRIPE_PUBLISHABLE_KEY, and BETTER_AUTH_URL.
  4. Push a commit to the connected Git repository to redeploy.

Prompt for your agent

Using the repo Merit-Systems/OpenInstinct, configure the Link environment variables for the project <your-app> without committing any secret. Expected output: a redeployed app with the Link wallet page showing the callback URL. Verify that STRIPE_PUBLISHABLE_KEY starts with pk_ and not sk_.

Caveat. Stripe currently supports Link Agent Wallet only for US and Canadian consumers, and the deploy button does not configure Link for you.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page