curl --request POST \
--url https://mcp.echozero.app/api/v1/agents/{id}/telegram/verify \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'x-signature: <x-signature>' \
--header 'x-timestamp: <x-timestamp>' \
--data '
{
"channel": "@MySignalsChannel"
}
'{
"success": true,
"data": {
"verificationResult": "verified",
"channelId": "<string>",
"channelName": "<string>",
"channelIconUrl": "<string>",
"memberCount": 123,
"message": "<string>"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}Verify Telegram signal channel (bot membership)
Resolves the channel via Telegram Bot API, checks the EchoZero bot is present with read access, and persists connectedChannels + signalSourceKind on the agent.
curl --request POST \
--url https://mcp.echozero.app/api/v1/agents/{id}/telegram/verify \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'x-signature: <x-signature>' \
--header 'x-timestamp: <x-timestamp>' \
--data '
{
"channel": "@MySignalsChannel"
}
'{
"success": true,
"data": {
"verificationResult": "verified",
"channelId": "<string>",
"channelName": "<string>",
"channelIconUrl": "<string>",
"memberCount": 123,
"message": "<string>"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}{
"success": false,
"error": {
"code": "NOT_FOUND",
"message": "Resource not found"
}
}Authorizations
User JWT access token issued by POST /api/auth/verify or POST /api/auth/social/verify. Routes that accept both auth modes declare api-key and bearer-jwt security schemes.
Headers
Required for API-key authenticated requests. HMAC-SHA256(secretKey, timestamp + METHOD + path + body) as lowercase hex. Omit only for JWT/OAuth session tokens or public routes.
Required with x-signature. Epoch milliseconds; rejected if drift exceeds 5 minutes. Omit only for JWT/OAuth session tokens or public routes.
Path Parameters
Body
Telegram public channel @username, t.me/slug, https://t.me/slug, or numeric chat id (-100…).
1 - 256"@MySignalsChannel"