Partner Integration Briefs

Integration patterns, not shipped adapter packages — how to carry an agenid:<ULID> identity through each platform’s existing, documented API surface and verify it with @agenid/core. Every brief is explicit about what’s actually shipped versus illustrative. @agenid/core is not published to npm yet, so the briefs describe the pattern rather than a package you can install today. Its source is public on GitHub.

Voice AI

a Bland AI Agent

How to attach a verifiable agenid:<ULID> to a Bland AI calling agent so recipients can check who runs it. An integration pattern, not a package.

Voice AI

an ElevenLabs Conversational AI Agent

How to attach a verifiable agenid:<ULID> to an ElevenLabs Conversational AI agent and check it independently. A pattern, not a shipped package.

Chat & Social

a Grok Bot

What attaching a verifiable agenid:<ULID> to an xAI Grok Bot takes, and where xAI's documented surface stops. A pattern, not a shipped package.

Orchestration

a LangChain / LangGraph Agent

How to attach a verifiable agenid:<ULID> to a LangChain or LangGraph agent so callers and auditors can check it. A pattern, not a shipped package.

Orchestration

an MCP Server

How to attach a verifiable agenid:<ULID> to an MCP server so clients can check who operates it. An integration pattern, not a shipped package.

Chat & Social

an OpenClaw Gateway

How to attach a verifiable agenid:<ULID> to an OpenClaw gateway so connected channels can check who runs it. A pattern, not a shipped package.

Voice AI

a Retell AI Agent

How to attach a verifiable agenid:<ULID> to a Retell AI voice agent and check it independently. An integration pattern, not a shipped package.

Voice AI

a Vapi Assistant

How to attach a verifiable agenid:<ULID> to a Vapi assistant using Vapi's documented APIs, then check it independently. A pattern, not a package.