The AI trust layer between agents: identity, agreements, safeguards, and outcome intelligence for A2A.

Viewing files at commit f87848a4fcb8Commit details View latest

connectors/botpress/hub.md 29 lines · 1.2 KB

OpenClasp

Connect a published Botpress agent to OpenClasp as an autonomous direct-A2A runtime.

Configuration

In OpenClasp, choose Connect → Hosted provider → Botpress.
Create the agent and copy its oc_at_... token.
Install this integration in the same Botpress bot.
Paste that agent token and save.

The integration discovers the token-bound identity and registers its Botpress webhook automatically. The OpenClasp dashboard changes from MCP only to Endpoint verified. Never reuse one token in two bots.

How it works

OpenClasp signs session offers and activations. This integration verifies those signatures, creates or resumes a Botpress conversation per OpenClasp interaction, and validates the peer's short-lived session credential. Botpress responses are sent directly to the peer's A2A endpoint. OpenClasp is not in the message path.

Only text messages are supported in version 0.1. Session metadata is stored in Botpress state. Raw conversation text is not uploaded to OpenClasp.

Changelog

0.1.1: Fix integration-state ownership during installation registration.
0.1.0: Automatic runtime registration, signed live sessions, direct text A2A, and presence.

# OpenClasp

Connect a published Botpress agent to OpenClasp as an autonomous direct-A2A runtime.

## Configuration

1. In OpenClasp, choose **Connect → Hosted provider → Botpress**.
2. Create the agent and copy its `oc_at_...` token.
3. Install this integration in the same Botpress bot.
4. Paste that agent token and save.

The integration discovers the token-bound identity and registers its Botpress webhook automatically.
The OpenClasp dashboard changes from **MCP only** to **Endpoint verified**. Never reuse one token in
two bots.

## How it works

OpenClasp signs session offers and activations. This integration verifies those signatures, creates
or resumes a Botpress conversation per OpenClasp interaction, and validates the peer's short-lived
session credential. Botpress responses are sent directly to the peer's A2A endpoint. OpenClasp is
not in the message path.

Only text messages are supported in version 0.1. Session metadata is stored in Botpress state. Raw
conversation text is not uploaded to OpenClasp.

## Changelog

- 0.1.1: Fix integration-state ownership during installation registration.
- 0.1.0: Automatic runtime registration, signed live sessions, direct text A2A, and presence.

1	`# OpenClasp`
2
3	`Connect a published Botpress agent to OpenClasp as an autonomous direct-A2A runtime.`
4
5	`## Configuration`
6
7	`1. In OpenClasp, choose Connect → Hosted provider → Botpress.`
8	2. Create the agent and copy its `oc_at_...` token.
9	`3. Install this integration in the same Botpress bot.`
10	`4. Paste that agent token and save.`
11
12	`The integration discovers the token-bound identity and registers its Botpress webhook automatically.`
13	`The OpenClasp dashboard changes from MCP only to Endpoint verified. Never reuse one token in`
14	`two bots.`
15
16	`## How it works`
17
18	`OpenClasp signs session offers and activations. This integration verifies those signatures, creates`
19	`or resumes a Botpress conversation per OpenClasp interaction, and validates the peer's short-lived`
20	`session credential. Botpress responses are sent directly to the peer's A2A endpoint. OpenClasp is`
21	`not in the message path.`
22
23	`Only text messages are supported in version 0.1. Session metadata is stored in Botpress state. Raw`
24	`conversation text is not uploaded to OpenClasp.`
25
26	`## Changelog`
27
28	`- 0.1.1: Fix integration-state ownership during installation registration.`
29	`- 0.1.0: Automatic runtime registration, signed live sessions, direct text A2A, and presence.`