/api/agents/{connectionId}Poll, decrypt, verify, and acknowledge · Activation states
VSELFAI task controlVSELF Agent Protocol 1.2
Connect an Agent with proof, not guesswork
Use one encrypted pull inbox for reusable authorizations. VSELF reports setup, connection, and connector verification as separate states.Activation states
3
- Agent setup is not completeGive this setup link or configuration file to the Agent once. It contains the Agent capability and inbox key.
- ActiveSend and open a test to verify this connector
- Agent connector verifiedVerification proves possession of the connector capability. It does not prove legal identity or ownership of the stated DID.
Quickstart
- 1Download the private connector configurationDownload config
- 2Import the zero-dependency clientSDK
- 3Poll, decrypt, verify, and acknowledge
import { VSELFAgentClient } from "https://vself.com/vself-agent-client.mjs";
const client = new VSELFAgentClient(connectorConfig);
await client.watch(async (delivery, vself) => {
const payload = await vself.open(delivery);
if (payload.type === "VSELFTaskDelivery") {
console.log("Authorized task room:", payload.agentUrl);
}
});Security contract
- Give this setup link or configuration file to the Agent once. It contains the Agent capability and inbox key.
- Tasks, room capabilities, and delivery keys remain encrypted
- Verification proves possession of the connector capability. It does not prove legal identity or ownership of the stated DID.
- Signed tasks delivered through VSELF appear here. Receiving a task is not permission to exceed its signed scope.
HTTP
Endpoints
/api/agents/{connectionId}/deliveries/{deliveryId}Acknowledge/api/rooms/{roomId}One integration, reusable authorization/api/vself/protocolSecurity contractResources