BITCORE Public Chat

[iamcapote]

BITCORE Context Agent

---

Public read-only AI assistant for navigating the BITwiki + BIThub ecosystem.

Grounds answers in public BIThub topics, BITwiki pages, categories, tags, guides, publications, constructs, nodes, and workspace documentation.

Executes retrieval-first orchestration through native BIThub/BITwiki HTTP tools, optional MCP utility access, short conversation memory, and evidence checks before synthesis.

Primary use-cases: 1 Public onboarding & navigation, 2 Evidence-grounded ecosystem Q&A.

What You Can Ask

---

• Find your way around BIThub — categories, guides, publications, constructs, nodes, workspaces, and tags.
• Understand BITwiki concepts — definitions, system terms, pages, relationships, and public documentation.
• Get source-backed answers — BITCORE searches public BIThub + BITwiki material before answering.
• Summarize public topics — turn long posts, guides, or wiki pages into concise explanations.
• Compare ecosystem pieces — BITwiki vs BIThub, Constructs vs Nodes, Guides vs Publications, Workspaces vs Tools.
• Route next steps — tells you where to read, what page matters, and which public source supports the answer.

Usage Tips

---

• Ask for exact ecosystem objects: guides, constructs, nodes, publications, workspaces, tags, or BITwiki pages.
• Use short concrete queries for best retrieval: AI tool guide, constructs, nodes, workspace, cognitive capital.
• Ask for comparisons, summaries, navigation paths, or source lists when exploring the ecosystem.

Limits & Errors

---

• Public read-only — does not modify BIThub, BITwiki, repos, workflows, inboxes, calendars, or databases.
• Uses short conversation memory only; it is not canonical long-term memory. Assume 30 chat responses max before needed to restart chat.

---

Point your agents to talk to BITCORE via a2a.

Agent-to-Agent Access (A2A)

Agent-to-Agent Access (A2A)

---

Other agents can call BITCORE directly over JSON.

Endpoint: POST https://n8n.bitwiki.org/webhook/bitcore-a2a

Use this for: public onboarding, navigation, concept lookup, source-backed ecosystem Q&A, and routing to public BIThub / BITwiki material.

Public boundary: read-only. BITCORE does not modify BIThub, BITwiki, repos, workflows, calendars, inboxes, or private member content.

Preferred request shape

{
  "protocol": "a2a/1.0",
  "source_agent": "your-agent-name",
  "operation": "inspect",
  "trace_id": "uuid-1",
  "request_id": "uuid-2",
  "session_id": "shared-session-id",
  "payload": {
    "user_message": "Explain what BIThub is and where a new operator should start.",
    "context": {
      "intent": "onboard",
      "familiarity": "operator",
      "referenced_ids": ["3208"]
    }
  }
}

Example curl

curl -X POST "https://n8n.bitwiki.org/webhook/bitcore-a2a" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "protocol": "a2a/1.0",
    "source_agent": "hermes",
    "operation": "inspect",
    "trace_id": "11111111-1111-1111-1111-111111111111",
    "request_id": "22222222-2222-2222-2222-222222222222",
    "session_id": "demo-session",
    "payload": {
      "user_message": "Explain the difference between BITwiki and BIThub.",
      "context": {
        "intent": "compare",
        "familiarity": "operator",
        "referenced_ids": []
      }
    }
  }'

Response shape

{
  "protocol": "a2a/1.0",
  "type": "a2a.response",
  "operation": "inspect",
  "status": "completed",
  "ok": true,
  "from": "BITCORE",
  "to": "your-agent-name",
  "agent": "BITCORE",
  "sourceAgent": "your-agent-name",
  "sessionId": "demo-session",
  "trace_id": "uuid-1",
  "request_id": "uuid-2",
  "taskId": null,
  "body": {
    "role": "assistant",
    "content": "...BITCORE reply..."
  },
  "answer": "...same reply text...",
  "metadata": {
    "workflow": "BITCORE Context Agent · A2A Webhook",
    "responseMode": "json",
    "generatedAt": "2026-06-05T00:00:00.000Z"
  }
}

Recommended operations

• navigate — route to the right public topic, category, guide, or page.
• inspect — explain a public concept, topic, page, or system surface.
• compare — contrast tools, concepts, or ecosystem components.
• onboard — orient a new user and suggest the best next public reading path.

Compatibility notes

• Preferred input is nested payload.user_message.
• BITCORE also accepts simpler legacy top-level fields such as message, input, text, or query.
• Agent identity can be passed as source_agent, sourceAgent, agent, or from.
• Correlation fields supported: trace_id, request_id, session_id, task_id, operation, intent.

Usage tips

• Send short concrete prompts for best retrieval.
• Use trace_id and request_id on every call for debugging and replay.
• Reuse session_id across a conversation if you want short memory continuity.
• If a request touches member-only or private material, BITCORE will state the public boundary and route to the nearest safe public source or next step.

---

Permissions: Public

Workflow Details

Public BITCORE Chat v2 workflow: