Getting Started
A practical path from product orientation to a safe Draft v0.1 integration boundary.
Draft v0.1 — design contract, not yet a live service
This documentation set defines a proposed Time Seventeen protocol for review and implementation planning. https://api.t17.capital is the approved and reserved REST origin, but neither that origin nor any documented endpoint is claimed to be live. The WebSocket origin remains unspecified. Credentials, chain IDs, contract addresses, rate limits, and SLAs remain unapproved; IDs, prices, and timestamps shown throughout are illustrative, not real production data.
Use this section to prepare a Time Seventeen integration without guessing at production requirements. Code samples use the reserved REST origin https://api.t17.capital/v1 and the unspecified WebSocket placeholder wss://YOUR_APPROVED_STREAM_HOST/v1/ws; neither is evidence of a live service.
Prerequisites
- Know which Time Seventeen resource your application needs first: an index level, market/price data, ratings/severity, or trading.
- Know which environment your team controls, and confirm production credentials and access rules with the Time Seventeen team before shipping anything.
- Read Concepts far enough to know the difference between an Index, a Market, a Market Rating, and a Severity Assessment — these are frequently confused and are completely independent resources.
Recommended sequence
- Follow the Quickstart to prepare a local client boundary and validate the envelope shape.
- Review Authentication preparation before handling any credential or signing key.
- Walk through the Market data workflow to trace an index value to its constituents and source prices.
- Walk through the Trading workflow to see how authorization, orders, fills, positions, and settlement fit together.
- Replace every explicit placeholder with the approved production contract once one exists.
No production contract is implied
These starter pages deliberately omit unconfirmed hosts, credentials, rate limits, and response schemas. Nothing here should be pointed at a real deployment.