Skip to content
synpute

Get started

Data model

Five core records carry a Synpute ID and follow the Synpute Standard. Everything else attaches to one of them, so a check, a payment or a transfer always lands on the same record a lender is reading.

  1. 01 · SYN-OP · BY · LN · PLEntityEvery other record names an entity as owner, party or lender.
    • role
    • legal_name
    • beneficial_owners
    • verification
  2. 02 · SYN-STSiteOccupied by an operator. Clusters run in a site.
    • address
    • lease
    • power
    • tier
  3. 03 · SYN-CLClusterRuns in a site; owned and operated by entities; made of units.
    • hardware
    • serials
    • liens
    • status
  4. 04 · SYN-CTContractSells a cluster's capacity to a buyer. Payments accrue against it.
    • buyer
    • rate
    • term_months
    • step_in
  5. 05 · SYN-FCFacilityA lender's loan, secured by clusters and the contracts behind them.
    • lender
    • collateral
    • contracts
    • principal

What attaches to them

ObjectAttaches to
VerificationEntity · Site · Cluster
LienCluster
Credit ProfileContract
Telemetry · PerformanceCluster
PaymentContract
Covenant · Alert · ReportFacility
Transfer program · TransferFacility · Cluster
GrantAny record

Conventions

  • Core records use Synpute IDs (SYN-XX-XXXX); attached objects use prefixed IDs (ver_, pay_, alr_).
  • Money is an integer in minor units with an ISO currency: { amount: 387000000, currency: "USD" }.
  • Dates are ISO 8601; date-only fields end in _on, timestamps in _at.
  • Values that aren't published yet are null, never omitted, so the shape is stable.
  • Lists return { object: "list", data, has_more, next_cursor } and page by cursor.
  • Risk is reported as indicators, flagged or clear with a reason. There is no score.