feat: add AgentPay — payment infrastructure for AI agents

[lfp22092002-ops]

AgentPay

Description: Payment layer for autonomous AI agents. Fund via Telegram Stars or USDC, set spending limits, and let agents operate independently.

Features:

• Multi-chain USDC wallets (Base, Polygon, BNB Chain, Solana)
• Telegram Stars funding (instant, in-app)
• x402 protocol support (HTTP-native micropayments)
• Agent identity (KYA) with trust scoring
• Budget governance + approval workflows
• Python & TypeScript SDKs

Links:

• GitHub: https://github.com/lfp22092002-ops/agentpay
• Website: https://leofundmybot.dev
• API Docs: https://leofundmybot.dev/docs
• Telegram Bot: https://t.me/FundmyAIbot

License: MIT

Summary by Sourcery

New Features:

• Introduce AgentPay configuration JSON to support funding and payment settings for autonomous AI agents.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Introduces AgentPay integration by adding a new configuration/metadata file defining the AgentPay payment layer (multi-chain USDC wallets, Telegram Stars funding, x402 micropayments, agent identity and governance, and SDK references).

File-Level Changes

Change	Details	Files
Add AgentPay configuration/metadata file to describe and wire up the AgentPay payment infrastructure.	Define AgentPay as a payment layer for autonomous AI agents, including funding via Telegram Stars and USDC. Document support for multi-chain USDC wallets (Base, Polygon, BNB Chain, Solana) and x402 HTTP-native micropayments. Describe agent identity (KYA) and trust scoring, budget governance, and approval workflows. Reference available Python and TypeScript SDKs and external resources (GitHub repo, website, API docs, Telegram bot).	src/agentpay.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since this feature is configured entirely via a large JSON file, consider defining and validating it against a JSON Schema or typed interface in code to catch misconfigurations early and make future edits safer.
• Double-check that no secrets, API keys, or environment-specific values are hard-coded in agentpay.json; if any are present, move them to environment variables or a secure configuration mechanism.
• If agentpay.json includes values that differ between environments (dev/staging/prod), consider splitting environment-specific configuration or adding a clear mechanism for overriding these values per deployment.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since this feature is configured entirely via a large JSON file, consider defining and validating it against a JSON Schema or typed interface in code to catch misconfigurations early and make future edits safer.
- Double-check that no secrets, API keys, or environment-specific values are hard-coded in `agentpay.json`; if any are present, move them to environment variables or a secure configuration mechanism.
- If `agentpay.json` includes values that differ between environments (dev/staging/prod), consider splitting environment-specific configuration or adding a clear mechanism for overriding these values per deployment.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}