Imports, compute & FLO

These features need explicit token permissions. Check /me for availability. When retrying a mutation, reuse its Idempotency-Key with the same input.

Import recordings

With sessions:write, create a session or use one you own. Track imports accept UTF-8 CSV with this exact header:

time_epoch,lat,lng
1793116800,37.8001,-122.4501
1793116801,37.8002,-122.4502

Use strictly increasing UTC Unix seconds within the session bounds. Each file supports 2–20,000 points, up to 1 MiB. HTTP uses content_base64; MCP can read an explicit local file_path.

Keep the completed receipt for retries. Wind replacement also needs the current wind_version and replacement consent. Imports do not start recalculation automatically.

Recalculate

With compute:write, request recalculation of a finished session you own. Keep the request ID and poll at least 30 seconds apart. Acceptance is not completion; check the resulting analysis readiness.

Ask FLO

With flo:write, open a session conversation, submit a turn and poll at five-second intervals. One turn per account can be active at a time.

A turn reserves up to one FLO credit and releases the unused amount after settlement. If a dispatched call’s usage is unknown, its recorded upper bound may be charged, including on timeout or cancellation. Read-only data requests do not spend FLO credits.

See exact requests and receipts in the API reference.