A2A INTEGRATION · CUSTOM TOOL

Use GitDealFlow A2A with Aider

AI pair-programmer in your terminal. Terminal-first developer-investors who prefer git-aware agentic editing.

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

Aider doesn't have native MCP, but its /run command + .aider.conf.yml command aliases make A2A trivial to wire. Drop a one-liner alias and any aider session can pull signals mid-edit ('aider, /signal trending fintech' returns the data inline so you can paste it into a doc the agent is editing).

Endpoint facts for Aider 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 Aider path	Aider has no native MCP client yet, so the custom-tool path below (a thin JSON-RPC call) is the way in.

Install

pip install aider-chat

Command alias in .aider.conf.yml

# .aider.conf.yml in your repo
# Then in aider: /signal trending
# Or: /signal sector ai-ml
shell-commands:
  signal: |
    curl -sS -X POST https://signals.gitdealflow.com/api/a2a \\
      -H 'Content-Type: application/json' \\
      -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"text","text":"'$1'"}]}}}' \\
      | jq -r '.result.artifacts[1].parts[0].text // .result.artifacts[0].parts[0].text'

Inline /run with curl

# In any aider session:
# /run curl -X POST https://signals.gitdealflow.com/api/a2a -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"text","text":"trending"}]}}}'

# Aider includes the output in its context, so the next prompt
# can reference the returned startups by name.

What you can ask

/signal trending, top 20 of the week, plaintext.
/signal sector fintech, sector watchlist.
/signal startup Roboflow, single-startup profile.
/signal methodology, full methodology text for citing in a doc.

Gotchas

Aider's /run output is appended to context, for big payloads, pipe through `head -20` to avoid context bloat.
If you're on Windows in PowerShell, the bash heredoc above won't work; use the inline /run with the JSON quoted as a single string.

When to pick which path

Because Aider 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 Aider 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.