Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Python: [Feature]: Crypto Payroll Agent — end-to-end sample with on-chain batch payments

オープン
  • 何か問題がありますか？
#8,881 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@eavanvalkenburg がすでに取り組んでいます。

2026年9月30日 から。

評価

この issue はまだ評価されていません。

説明

agents middleware python
Description
What problem does it solve?

The current sample set covers travel planning, content generation, M365, RAG, and workflows — but no sample demonstrates an agent handling irreversible financial operations with real side effects. Developers building payment or fintech agents don't have a reference for guardrail patterns (spend ceilings, recipient caps, confirmation gates) on actions that move real value.

What would the expected behavior be?

A self-contained sample in python/samples/05-end-to-end/crypto_payroll_agent/ where an AI agent accepts a natural-language payroll instruction (e.g. "Pay Alice 50 USDC and Bob 30 USDC on Base"), resolves it into structured recipient/amount data, calls a payment gateway's REST API to build the unsigned transaction, signs locally, broadcasts, and confirms settlement — all through MAF tool functions.

The sample would include:

  • 3–4 tool functions (estimate batch cost, get token info, execute batch, check transaction)
  • A guardrail callback enforcing recipient count ≤ 200, address format validation, and a configurable MAX_BATCH_USD spending ceiling
  • README with setup, walkthrough, and on-chain proof transactions from verification
  • Tests runnable without a funded wallet (mocked gateway responses)

The payment gateway used would be Spraay Protocol (gateway.spraay.app), operated by Plagtech LLC — my company. The gateway charges a 0.3% protocol fee on batches and $0.02 per API call. These fees would be documented in the sample README. The gateway is the only Spraay-specific dependency; the agent architecture, tool patterns, and guardrail approach are framework-general.

Are there any alternatives you've considered?

The sample could also fit in microsoft/Agent-Framework-Samples under 09.Cases/ if that's a better home for third-party integration demos.

Prior art

I've contributed similar payment-agent samples to other frameworks:

Questions for maintainers
  1. Is python/samples/05-end-to-end/ the right location?
  2. Any preference on LLM provider the sample should target (GitHub Models, Azure OpenAI, OpenAI)?
  3. Should tools use @tool or @kernel_function? I'll match whichever convention the existing samples follow.
Code Sample
from agent_framework import Agent

# Tool functions would call the Spraay gateway REST API
# Example: estimate a batch payment
@tool
async def estimate_batch(token: str, recipients: list[str], amounts: list[str]) -> str:
    """Estimate gas and fees for a batch payment on Base."""
    response = await httpx.AsyncClient().post(
        "https://gateway.spraay.app/api/v1/batch/estimate",
        json={"token": token, "recipients": recipients, "amounts": amounts}
    )
    return response.json()

agent = Agent(
    client=...,  # Azure OpenAI or GitHub Models
    name="PayrollAgent",
    instructions="You are a payroll agent that executes batch crypto payments on Base.",
    tools=[estimate_batch, execute_batch, get_token_info, check_transaction],
)
Language/SDK

Python

主要言語
Python
スター
13.6k
フォーク
2.3k
平均マージ
1日 15時間
マージ済み PR（30日）
442

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/agent-framework のほかの issue

microsoft/agent-framework の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。