Position values

Live NAV. Net-of-fees yield. One endpoint.

Position reads return the current NAV, the net-of-fees yield, and the last reconciliation timestamp for every Flo token — reconciled continuously against the prime broker's books.

SDK · Core primitive

The full Positions spec lives in the docs

Get one position, iterate every holding, response fields, stale-NAV flags, and the broker attestation URL for audit trails. Python and Node.js tabs, copy-ready. Free on every tier.

Open the Positions reference

How position values work

Every Flo token is backed 1:1 by a custodied underlying position. Reconciliation runs in the background so reads are always correct and always free.

01

Every mint creates a position

When you call mint, Flo creates a position record keyed by the token symbol. Position state lives in Flo's ledger plus the onchain supply.

02

Reconciliation runs continuously

A background worker reconciles the onchain token supply against the SPV's custodied underlying at Interactive Brokers and Alpaca Securities, logging every check.

03

Reads always return the latest state

Every position read returns the live NAV, net-of-fees yield, and the last successful reconciliation timestamp. No cache layer in between — always fresh.

Everything your frontend needs

Build portfolio UIs and yield aggregators without maintaining a pricing service or a reconciliation worker.

📊

Live NAV on every read

Every position read returns the current NAV per token, the total holding value, and the timestamp when it was last reconciled against the prime broker's books.

📈

Yield, net of all fees

The APY field is what your users actually earn — already net of Flo fees, broker spread, and any underlying fund expenses. No math on your side.

Streamed accruals

Subscribe to accrual events via webhooks. Every yield tick lands in your backend the moment it's booked, so your users see their position grow in real time.

🔁

Reconciled against the prime broker

Every position is reconciled continuously with Interactive Brokers and Alpaca Securities books. If the onchain supply diverges from the custodied underlying, the read fails loudly.

🧾

One endpoint across asset classes

The same read endpoint covers stocks, bonds, ETFs, and private credit. Clients don't have to branch on asset type.

🔓

Free + unlimited

Position reads are free. No rate limits on read endpoints — scrape them as hard as you want.

REST API · off-chain

Configure fees and stream NAV updates

Fee-schedule setup (management + performance bps, high-water marks) and NAV-tick webhooks are configured via REST, once per token. Request shape, payload schemas, and retry semantics in the docs.

Open the REST reference

Build portfolio UIs without a pricing service

Free, unlimited, reconciled with the prime broker. One endpoint for every asset class Flo supports.