Skip to main content
Data Sync writes an action’s result to a StackOne-managed index, then serves reads from that index instead of calling the provider. Use it for data an agent reads often — fast, repeatable reads without re-fetching from the source each time.

How it works

1

Write a run to the index

Add ?sync=true to a normal RPC call. StackOne runs the action against the provider and stores the result.
The response includes a datasync block with synced_at, sync_expires_at, and a params_hash.
2

Read synced data back

Call /actions/rpc/synced with the same action and params. StackOne returns the stored records without touching the provider.
A synced read resolves by params_hash. The action, query, body, and headers must match what was used on the write, or it won’t find the run. Pagination keys are stripped before hashing.

Sync metadata

The datasync block tells you the state of the stored data:

When to use it

  • The same provider data is read repeatedly and tolerates being slightly stale.
  • You want predictable read latency that doesn’t depend on the provider.
For data that must be live on every call, use a normal Actions API call without sync.

Reference

Make an RPC call

The sync=true write parameter.

Read synced data

The /actions/rpc/synced read endpoint.