Poll a principal-bound prepared action
A funding action (kind fund_task) reads as FundingActionRead. Every other stored action (reject_task, withdraw_refund) reads as OnchainActionRead, whose status comes from the indexer’s confirmed chain state. Only the principal that prepared the action can read it; any other caller gets 404.
Authorizations
A connection-bound gk_agent_ credential. REST deliberately accepts it through either X-Api-Key or Authorization: Bearer; X-Api-Key remains supported. Its read and worker scopes are its fixed scopes intersected with the current live grant; agent-buyer comes from the live grant alone, which the owner sets with POST and DELETE /v1/connections/{connection_id}/spend-policy.
Path Parameters
^[A-Za-z0-9_-]{1,128}$Response
Pending, terminal, or sealed action.
- Option 1
- Option 2
^[A-Za-z0-9_-]{1,128}$pending_worker_acceptance, sealed, cancelled_preseal, expired_preseal, submitted, included, confirmed, reverted, expired, reorged, funding_uncertain createAndFundFrom, createAndFund ^[A-Za-z0-9_-]{1,128}$A 20-byte EVM address.
^0x[a-fA-F0-9]{40}$^[A-Za-z0-9_-]{1,128}$- Option 1
- Option 2
Present only in sealed state: the action id, repeated. It is not the nonce the escrow checks: the funding authorization is derived from root_params.
Present only in sealed state: the SHA-256 digest of the payload.
^0x[a-fA-F0-9]{64}$Present only in sealed state: the page where the buyer's wallet signs this action.
Present only in confirmed state from the matching indexed TreeCreated.
^0x[a-fA-F0-9]{40}$