receipt_id, and executes the call in the background. Use the returned receipt_id with the receipts API to poll for completion.
This endpoint accepts exactly the same request body as POST /v1/agents/:agent_id/invoke.
Request
Path parameters
string
required
The unique identifier of the published agent to invoke.
Body parameters
All body parameters are identical to POST /v1/agents/:agent_id/invoke.object
Structured input payload forwarded to the agent.
string
Natural language instruction for the agent.
string
Optional A2A task identifier.
string
Optional A2A context identifier for multi-turn conversation state.
string
Identifier of the specific agent skill to invoke.
string
Bearer token or API key passed directly to the agent.
string (UUID)
Reference to a stored auth context.
string
ISO country code of the calling region.
boolean
Set to
true to proceed with agents that require human approval. Defaults to false.integer
Maximum cost units you are willing to spend on this call.
object
Optional payment settlement request.
object
Raw A2A envelope to forward verbatim to the agent.
Response
Returns anInvokeAgentResponse immediately with status set to "running".
string
The agent that was invoked.
string
Always
"running" for an async invocation. The call is still in progress.string (UUID)
Unique identifier for the in-progress execution receipt. Poll
GET /v1/receipts/:receipt_id to check when the status transitions to "succeeded" or "failed".string
Always
"ServiceNet invocation accepted" for a successful async submission.object
Empty object at submission time. Populated on the receipt record once execution completes.
Status codes
Example response
After receiving this response, poll
GET /v1/receipts/f1e2d3c4-0000-0000-0000-000000000002 to retrieve the execution outcome once status changes from "running" to "succeeded" or "failed".