Skip to main content
POST
/
v1
/
trpc
/
v2.workflows.*
tRPC v2 Workflows API
curl --request POST \
  --url 'https://api.glider.fi/v1/trpc/v2.workflows.*' \
  --header 'X-API-KEY: <api-key>'
The v2.workflows.* namespace is the staged workflow authoring surface for agentic workflow drafts.
  • Base endpoint: POST /v1/trpc
  • Namespace: v2.workflows.*
  • Auth: wallet session or API key
  • Rollout: gated behind the agentic_workflows_v1 feature flag

​
Enabled Procedure Groups

  • v2.workflows.list
  • v2.workflows.get
  • v2.workflows.drafts.*
    • list
    • start
    • startFromWorkflow
    • get
    • answer
    • cancel
  • v2.workflows.authoring.*
    • validate
    • preview
    • commit
  • v2.workflows.drafts.commit
  • v2.workflows.create
  • v2.workflows.update
  • v2.workflows.pause
  • v2.workflows.resume
  • v2.workflows.runNow
  • v2.workflows.archive
  • v2.workflows.monitor.*
    • tick
    • record
  • v2.workflows.proposals.*
    • list
    • get
    • approve
    • dismiss
  • v2.workflows.executions.*
    • list
    • get
    • getByWorkflow
    • getByProposal
  • v2.workflows.ask
  • v2.workflows.memorySearch

​
Rollout Notes

  • The namespace is exposed only when agentic_workflows_v1=true for the caller.
  • authored_agent_sdk still independently gates authored-source validation, preview, and commit flows.
  • bounded_multi_asset_buys still independently gates authored preview support for bounded multi-asset buy programs.

​
Lifecycle Notes

The current public lifecycle supports:
  1. Starting and iterating on workflow drafts from free text or existing workflows. Authored drafts can now include a source-derived graph preview on the draft plan before commit.
  2. Validating, previewing, and committing authored workflow modules when the authored SDK flag is enabled.
  3. Creating, updating, listing, and inspecting canonical workflows.
  4. Pausing, resuming, running, archiving, and monitoring workflows.
  5. Reading workflow execution history and proposal history, including proposal-linked execution lookup.
  6. Approving or dismissing workflow proposals.
  7. Asking workflow-scoped questions and searching workflow memory.
Direct create/update currently target the canonical workflow rail for:
  • rebalance_portfolio
  • buy_asset
  • sell_asset
  • cash_sweep
  • recurring_deposit
  • withdraw_funds
Other schema-valid workflow kinds may still return unsupported-operation errors from the facade until later slices land. v2.workflows.list supports workflow-kind filtering via kind and trigger-kind filtering via triggerKind. Monitor discovery should use triggerKind for trigger semantics such as price_condition and authored_sdk. This keeps the rollout centered on the top-level workflow surface flag, with additional authored-SDK gating only for authored-module flows.