Quickstart
Quickstart
Check the Agent Card, send a message to an agent, and jump into the generated API reference.
https://linnex.io/flows/api/v1/{flow_id}Authorization: Bearer {token}JSON-RPC 2.01. Prepare Values¶
The examples below need a flow identifier and an access token.
export PLATFORM_TOKEN="your_token"
export PLATFORM_FLOW_ID="my-agent"
export PLATFORM_BASE_URL="https://linnex.io/flows/api/v1/${PLATFORM_FLOW_ID}"
Tip
Use an API token in the Authorization: Bearer ... header for server integrations. Embedded widgets can use a short-lived embed session token.
Legacy domain
On humanitec.ru the API paths and JSON-RPC contract are the same. Use https://humanitec.ru/flows/api/v1/{flow_id} instead of linnex.io if your integration is tied to the legacy apex.
2. Fetch The Agent Card¶
The Agent Card describes the flow, supported capabilities, available branches, and public variables.
3. Send A Message¶
Interactive calls use POST against the agent URL with a JSON-RPC body.
curl -X POST "${PLATFORM_BASE_URL}" \
-H "Authorization: Bearer ${PLATFORM_TOKEN}" \
-H "A2A-Version: 1.0" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": "1",
"method": "SendMessage",
"params": {
"message": {
"messageId": "msg-1",
"role": "ROLE_USER",
"parts": [
{"text": "Help me prepare a short project status"}
]
}
}
}'
4. Stream Responses¶
For streaming responses, switch the method to SendStreamingMessage. The response is delivered as Server-Sent Events (statusUpdate / artifactUpdate).
curl -N -X POST "${PLATFORM_BASE_URL}" \
-H "Authorization: Bearer ${PLATFORM_TOKEN}" \
-H "A2A-Version: 1.0" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": "stream-1",
"method": "SendStreamingMessage",
"params": {
"message": {
"messageId": "msg-stream-1",
"role": "ROLE_USER",
"parts": [
{"text": "Tell me the next steps for launching the agent"}
]
}
}
}'