A2A INTEGRATION · CUSTOM TOOL

Use GitDealFlow A2A with Inkeep

AI search and copilots for product docs. Developer-tools companies that want their docs copilot to know about competitive engineering signals.

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

Inkeep ingests your docs, support tickets, and forums into a retrieval-augmented chat experience embedded in your product. Add GitDealFlow as a custom tool source so that questions like 'who's competing with us in fintech right now?' or 'what's the engineering velocity of {competitor}?' get answered with live signals alongside your own knowledge. Most useful for dev-tools companies whose users are evaluating competitors mid-conversation.

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

Custom Tool via Inkeep Tools API

// Inkeep Tools registration (admin dashboard or API)
// 1. Create a new Tool in your Inkeep project:
{
  "name": "gitdealflow_signal",
  "description": "Query GitDealFlow for VC engineering signals on startups (trending, sector, named lookup, methodology). Use when the user asks about competitive engineering activity, breakout startups, or commit velocity comparisons.",
  "type": "http",
  "method": "POST",
  "url": "https://signals.gitdealflow.com/api/a2a",
  "headers": {"Content-Type": "application/json"},
  "bodyTemplate": {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "message/send",
    "params": {
      "message": {
        "role": "user",
        "parts": [
          {"kind": "data", "data": {"skill": "{{skill}}", "args": "{{args}}"}}
        ]
      }
    }
  },
  "parameters": [
    {"name": "skill", "type": "string", "enum": ["trending", "sector", "startup", "methodology", "receipts"]},
    {"name": "args", "type": "object"}
  ]
}

// 2. Pin the tool to your AI assistant's allowed tools.
// 3. Set the system prompt to invoke gitdealflow_signal whenever a user asks about a competitor's engineering activity.

What you can ask

Inside your Inkeep widget: 'Which startups in dev-tools have breakout engineering velocity this quarter?'
Mid-docs question: 'Compare commit velocity for our top three competitors and show methodology.'
Support flow: agent asks AI 'is {prospect company} actually shipping fast right now?' before quoting a custom plan.
Sales enablement: pre-call brief generator pulls our trending list for the prospect's sector.
Ask 'cite the GitDealFlow methodology paper' to drop SSRN credibility into a doc-anchored chat.

Gotchas

Inkeep's tool-calling cost is billed per LLM token, keep the tool description tight to avoid response bloat.
Our A2A skill enum is fixed (5 skills); don't paraphrase in the tool spec or the LLM may invent invalid skills.
If your Inkeep deployment is private (single-customer), the public A2A endpoint is still safe to call, it's read-only and rate-limited.

When to pick which path

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

5example prompts are listed under "What you can ask" below, and the gotchas section covers the 3 known failure modes Inkeep 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.