Actions

The public API exposes the platform gateway action surfaces directly.

Actions

• GET /v1/actions
• POST /v1/actions/search

Action visibility is filtered by:

• connected integrations
• reconnect state
• permission grants
• workspace scope

Use actions when your app already knows which capability it wants and does not need model reasoning.

This is the deterministic side of AP. Sessions and runs are for model-driven work. Action invocations are for direct capability calls.

Action invocations

• POST /v1/action_invocations
• GET /v1/action_invocations

Example invocation:

curl https://api.agentplatform.cloud/v1/action_invocations \
  -H "Authorization: Bearer $AP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "linear.issues.list",
    "input": { "query": "priority:urgent" }
  }'

Example response:

{
  "invocation_id": "inv_123",
  "action": "linear.issues.list",
  "connection_id": "conn_123",
  "result": {
    "issues": []
  }
}

Use action invocations when you want direct access to gateway-backed capabilities without going through a session run.