Agent connections
Connect an Agent to SUVENRA
Give an Agent one encrypted task channel for signed authorizations. SUVENRA delivers the task without giving the server the decryption key.End-to-end encryptedTasks, room capabilities, and delivery keys remain encrypted
Quick start
New here? Follow these steps
01
What to do now
Sign inSign in
Sign inThe Agent name plus DID or HTTPS URL identifies the intended recipient. It does not connect the Agent by itself; the Agent must still install the connector configuration.Read full guidanceSign in before creating a persistent Agent connection
First connection · once only
- 01You do this
Create a connection
Create a connectionThe Agent name plus DID or HTTPS URL identifies the intended recipient. It does not connect the Agent by itself; the Agent must still install the connector configuration.Read full guidanceSign in before creating a persistent Agent connection
Done whenAgent setup - 02You do this
Agent setup
Agent setupAn encrypted pull endpoint for signed tasks. The Agent must install its credentials and check this endpoint; creating a SUVENRA connection alone does not make the Agent receive anything.Read full guidanceGive this setup link or configuration file to the Agent once. It contains the Agent capability and task-channel key.
Done whenActive - 03You do this
Send test
Send testChecks the signature, controller, service namespace, scope, expiry, required fields, and revocation status. It does not prove that an Agent's factual claims are true.Read full guidanceSend and open a test to verify this connector
Done whenAgent connector verified
For every task
- 04You do this
Authorize
AuthorizeAn explicit allowlist for the Agent. Any action that is not selected remains outside the authorization.Read full guidanceDescribe the task, allowed actions, required evidence, and expiry, then sign the authorization
Done whenDelivered to Agent - 05Agent does this
Open authorized task
Open authorized taskThe handoff space where an Agent accepts, requests changes, declines, or returns evidence. Owner, Agent, and verification links have different permissions.Read full guidanceWork only within this signed authorization. Return the result and supporting evidence for human review; the authorization is not final approval.
Done whenAn Agent result is ready for review - 06You do this
Review returned work
Review returned workA person accepts or rejects the returned work. SUVENRA binds that decision, the original authorization, and the evidence into a signed outcome receipt.Read full guidanceCompare the returned work with the signed task and required evidence, then record your decision.
Done whenA result decision was recorded
Connected Agents
0 Agent · 0 Deliveries
SUVENRA Agent Protocol 1.4
One integration, reusable authorization
One integration, reusable authorizationAn encrypted pull endpoint for signed tasks. The Agent must install its credentials and check this endpoint; creating a SUVENRA connection alone does not make the Agent receive anything.Read full guidance- 1Create a connectionCreate a connectionThe Agent name plus DID or HTTPS URL identifies the intended recipient. It does not connect the Agent by itself; the Agent must still install the connector configuration.Read full guidance
- 2Agent task channelAgent task channelAn encrypted pull endpoint for signed tasks. The Agent must install its credentials and check this endpoint; creating a SUVENRA connection alone does not make the Agent receive anything.Read full guidance
- 3VerifyVerifyChecks the signature, controller, service namespace, scope, expiry, required fields, and revocation status. It does not prove that an Agent's factual claims are true.Read full guidance
- 4Open authorized taskOpen authorized taskThe handoff space where an Agent accepts, requests changes, declines, or returns evidence. Owner, Agent, and verification links have different permissions.Read full guidance