A2A INTEGRATION · CUSTOM TOOL

Use GitDealFlow A2A with AutoGen

Microsoft's multi-agent conversation framework. Researchers and enterprise builders running multi-agent debates and tool-use loops.

Crunchbase API: $20K/yr. GitDealFlow A2A: free, no signup.

AutoGen's FunctionTool wraps any Python callable. Wrap our A2A endpoint as a FunctionTool and any AssistantAgent in a GroupChat can pull live signals as part of a multi-agent debate ('the scout argues for inclusion, the contrarian argues against, the methodology agent cites SSRN').

Endpoint facts for AutoGen users

Whatever wiring you choose, the target is the same single endpoint. These are the fixed facts; nothing on this page changes them:

Protocol	A2A JSON-RPC 2.0 (protocolVersion 0.3.0)
Endpoint URL	`https://signals.gitdealflow.com/api/a2a`
Skills exposed	5, mirrored 1:1 with the MCP server tools (trending, sector, lookup, summary, methodology)
Auth	None; free in perpetuity, read-only
Freshness	Recomputed weekly; responses carry the data-as-of date
Best AutoGen path	AutoGen has no native MCP client yet, so the custom-tool path below (a thin JSON-RPC call) is the way in.

Install

pip install autogen-agentchat autogen-ext requests

FunctionTool wrapper

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools import FunctionTool
from autogen_ext.models.openai import OpenAIChatCompletionClient
import requests

A2A_URL = "https://signals.gitdealflow.com/api/a2a"

def gitdealflow_query(skill: str, args: dict | None = None) -> dict:
    """Call GitDealFlow A2A for VC engineering signals.

    skill: get_trending_startups | search_startups_by_sector |
           get_startup_signal | get_signals_summary | get_methodology
    """
    body = {
        "jsonrpc": "2.0", "id": 1,
        "method": "message/send",
        "params": {"message": {"role": "user", "parts": [
            {"kind": "data", "data": {"skill": skill, "args": args or {}}},
        ]}},
    }
    return requests.post(A2A_URL, json=body, timeout=15).json()

scout_tool = FunctionTool(gitdealflow_query, description="VC engineering signals.")

scout = AssistantAgent(
    name="scout",
    model_client=OpenAIChatCompletionClient(model="gpt-4o-mini"),
    tools=[scout_tool],
    system_message="You surface live engineering signals via gitdealflow_query.",
)

What you can ask

GroupChat: scout + contrarian + memo-writer debate the top breakout.
Two-agent loop: planner asks scout for fintech trending, scout returns, planner picks top 3.
Critic agent challenges scout's pick by asking for methodology citation.
Reflection loop: scout proposes, critic checks, scout revises.

Gotchas

AutoGen v0.4+ uses async tools, wrap requests with asyncio.to_thread or use aiohttp instead.
GroupChat token cost compounds quickly; cap rounds with max_turns and have the scout summarize the A2A payload before passing it onward.

When to pick which path

Because AutoGen currently lacks a native MCP client, your two options are the custom tool below (a thin JSON-RPC wrapper you register once) or switching the session to an MCP-capable host when you need the richer tool surface. For scheduled jobs and pipelines, the raw endpoint is usually the sturdier dependency: no client versioning to track.

4example prompts are listed under "What you can ask" below, and the gotchas section covers the 2 known failure modes AutoGen users hit with this endpoint. If a prompt fails, check the gotchas first: most misses are shape mismatches, not endpoint outages.

References

Try it without setup

The interactive playground lets you send live JSON-RPC requests against the A2A endpoint with no install, no auth. Pick a skill, hit send, see the response.

Full launch story: I made my VC deal flow callable by Claude.