Skip to content

Python: Add Agent Commerce Gateway to the Python community projects - #10368

Open
Dmitry Sergeev (SergeevDmitry) wants to merge 1 commit into
microsoft:mainfrom
SergeevDmitry:python-community-agent-commerce-gateway
Open

Dmitry Sergeev (SergeevDmitry) wants to merge 1 commit into
microsoft:mainfrom
SergeevDmitry:python-community-agent-commerce-gateway

Conversation

@SergeevDmitry

@SergeevDmitry Dmitry Sergeev (SergeevDmitry) commented Nov 14, 2026 •

Copy link
Copy Markdown

Motivation & Context

Adds Agent Commerce Gateway to the Tools section of the Python community projects catalog. I'm the CEO of DevLab, which builds Agent Commerce Gateway, so I'm affiliated with the project this row lists.

The integration is published for the Python SDK: pip install agent-framework-agent-commerce (PyPI, 0.1.0, requires agent-framework-core 1.x). Source and tests are in our Apache-2.0 repository: https://github.com/devlab-group/agent-commerce-clients/tree/master/python/agent-framework-agent-commerce

  • await agent_commerce_tools(...) discovers the resources a self-hosted gateway exposes and returns one FunctionTool per resource, with the resource's JSON Schema as input_model and its price in the description.
  • Paid tools are created with approval_mode="always_require", so the run stops for a person's decision before a paid call. Free tools use "never_require".
  • Payments use x402. Before a payment is signed, the client refuses it if the price exceeds the per-call or daily limit set in code, or if the network is not in the allowed list.

The package calls the gateway's HTTP API and does not use the MCP client, so it is not covered by the MCP exclusion in the catalog criteria. The docs page linked in the row has the setup, the approval loop and an end-to-end run on Base Sepolia.

Description & Review Guide

  • What are the major changes? One row in the Tools table of python/samples/community-projects.md, placed alphabetically before Engram.
  • What is the impact of these changes? Documentation only.
  • What do you want reviewers to focus on? Whether the row fits the catalog criteria.

Related Issue

N/A - trivial change: one catalog row in the format the catalog criteria define, no code.

AI Assistance

  • No material AI assistance was used.
  • This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: drafting the catalog row and this description.

Contribution Checklist

  • The code builds clean without any errors or warnings
  • All unit tests pass, and I have added new tests where possible
  • The PR follows the Contribution Guidelines
  • This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
  • This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔵 Needs a closer look

Local catalog checks pass, but the required Markdown link-check workflow result is missing, preventing confirmation of final catalog eligibility.

No open issues 🎉

What changed in this PR

Adds Agent Commerce Gateway to the Python community-project catalog as an external tools integration.

Changes:

  • Adds a Tools entry alphabetically before Engram, describing endpoint discovery, x402 payments, spending limits, and paid-call approval.
  • Links to integration documentation and the maintainer’s issue-creation page. No runtime code changes.
File Description
python/​samples/​community-projects.md Adds the Agent Commerce Gateway entry to the Tools table.

Review effort: Balanced

@surlymochan Nick (surlymochan) left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Checked the two links in the new row before reviewing: the Project link (acg.devlab.group/docs/integrations/microsoft-agent-framework) returns 200 and is a genuine Agent Framework integration page — pip install agent-framework-agent-commerce, tools that pay with x402 within spending limits, approval required for paid calls by default — and the Issues link resolves to the devlab-group/agent-commerce-clients repo.

One small inconsistency: the Issues column here links to .../issues/new, while the neighbouring rows (Engram and the others in this table) link to .../issues/new/choose. Is there no issue-template chooser on that repo, or should this match the new/choose form the rest of the table uses?

Otherwise the row follows the table format (name, description, scenarios, project, issues) and the description matches what the linked docs actually offer.

@SergeevDmitry

Copy link
Copy Markdown
Author

Thanks for checking the links. devlab-group/agent-commerce-clients has no issue templates, so there is no chooser page: /issues/new is where an issue is opened. The catalog criteria list both /issues/new and /issues/new/choose as expected forms, and both are already in the file (DXMT, Membase, Supermemory, ACGS and BotsRated use /issues/new).

This branch was successfully deployed

1 active deployment
github-app-auth — 17427489 Deployed Nov 14, 2026 by SergeevDmitry via add_label #27874
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Usage: [Issues, PRs], Target: documentation in the code base and learn docs python Usage: [Issues, PRs], Target: Python

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants