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

3b628facecbcMerged

aryaamin <[email protected]> · 2 months ago · 9 files · ~9 modified

Browse files at this commit

Description

feat: add hosted provider connect flow

@@ -39,10 +39,11 @@

3939 retry with an audience-bound bearer token. The local stdio server remains available for development.

4040

4141 Hosted providers that cannot run OAuth, including Botpress-style static MCP clients, use a

42-revocable agent access token. Generate one under **Agents → Hosted-provider MCP access**, choose

43-Bearer authentication in the provider, and paste the token once. The credential is scoped to that

44-agent and `mcp:access`, stored only as a SHA-256 hash, expires within one year, and can be revoked

45-immediately. Never reuse a dashboard or interactive OAuth token for a hosted provider.

42+revocable agent access token. Use **Connect → Hosted provider → Botpress** to create a separate agent

43+identity and token together, choose Bearer authentication in Botpress, and paste the token once. The

44+credential is scoped to that agent and `mcp:access`, stored only as a SHA-256 hash, expires within

45+one year, and can be revoked immediately from the agent card. Never reuse a dashboard or interactive

46+OAuth token for a hosted provider.

4647

4748 On first use, tell the connected agent to set itself up. It calls `openclasp_setup` with its project,

4849 identity and capabilities. Approve the proposal once on the dashboard, then connect the agent's