Skip to content

Add CrowPay payment tool for AI agents#8

Open
streacy wants to merge 2 commits intoMervinPraison:mainfrom
streacy:add-crowpay-tool
Open

Add CrowPay payment tool for AI agents#8
streacy wants to merge 2 commits intoMervinPraison:mainfrom
streacy:add-crowpay-tool

Conversation

@streacy
Copy link

@streacy streacy commented Mar 6, 2026

CrowPay Tool

Adds crowpay_tool.py — a payment tool enabling AI agents to manage wallets and authorize payments via CrowPay.

Actions

  • setup — Create an agent wallet
  • authorize — Handle x402 payment authorization
  • authorize_card — Credit card payments
  • poll_status — Check pending approval status
  • settle — Report transaction settlement

Usage

from praisonai_tools import CrowPayTool

tool = CrowPayTool()
wallet = tool.run(action="setup")

Environment variable: CROWPAY_API_KEY


Requested by @MervinPraison in PraisonAI#1112 (comment).

@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates the CrowPay payment system into the PraisonAI framework by adding a dedicated CrowPayTool. This enhancement provides AI agents with robust financial capabilities, allowing them to perform various payment-related operations such as setting up wallets, authorizing different payment types, checking approval statuses, and settling transactions. The addition significantly expands the agents' ability to interact with external services requiring payment.

Highlights

  • New CrowPay Tool: Introduced a new CrowPayTool to enable AI agents to manage wallets and process payments via the CrowPay platform.
  • Payment Actions: The tool supports several key payment actions: wallet setup, x402 payment authorization, credit card payments, approval status polling, and transaction settlement.
  • API Key Requirement: The tool requires the CROWPAY_API_KEY environment variable for authentication with the CrowPay API.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • praisonai_tools/tools/crowpay_tool.py
    • Added a new CrowPayTool class inheriting from BaseTool.
    • Implemented setup method for creating agent wallets.
    • Included authorize method for handling x402 payment authorizations.
    • Provided authorize_card method for processing credit card payments.
    • Added poll_status method to check the status of pending approvals.
    • Implemented settle method for reporting transaction settlements.
    • Incorporated internal helper methods for API key validation and dynamic requests package import.
Activity
  • No activity has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a CrowPayTool for AI agent payments. The overall implementation is sound, but I have identified a few areas for improvement. My main feedback concerns significant code duplication across the various action methods, which could be refactored into a helper method to improve maintainability. I've also noted a minor style issue with an import statement.

Most importantly, the new CrowPayTool and its helper function crowpay_setup are not registered in praisonai_tools/tools/__init__.py. Without this change, the tool will not be importable or usable by the agents. This is a critical omission that needs to be addressed.

- Add _make_request() to centralize key check, requests import, HTTP call, and error handling
- Replace all duplicated boilerplate in action methods with _make_request() calls
- Move urllib.parse.quote to top-level import (PEP 8)
- Replace broad Exception catches with specific RequestException + ValueError
- Fix return type hint: remove str from Union
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant