Pricing & trust
Trust is the contract. This page does not invent a list price.
Sylphx project commercial policy — if and when a list price exists — lives in Commerce catalog facts, not in this paragraph. Independent developers integrate through the Product Contract. They do not buy a Data product key and they do not create a second store in the client.
How access is priced in practice
- Platform issues the project binding. Identity issues a short-lived plan-bound delegation. Data verifies both.
- Usage is emitted to Commerce and Observability. Callers do not author usage rows through the Data public API.
- This page will not copy a mutable live price into prose.
Trust rules
| Claim | Oracle |
|---|---|
| Binding is discovery | api_base comes from the Platform binding. Compiling api.data.sylphx.com as a sibling constant is a defect in a generated client. Residual dens data.api.sylphx.com is not dest. |
| No Data product key | A Lattice-style secret, LATTICE_API_KEY, or Data-minted key is not tenant authority. Binding substituted by a product key fails. |
| Dual-token customer path | Customer mutations and customer reads of customer data carry Binding + Delegation. Missing or confused claims are 401. |
| Replay-safe effects | Sylphx-Effect-Id plus delegation JTI is one immutable intent. Exact replay returns the stored terminal. |
| Byte integrity | Object put then get is the same bytes, size, and SHA-256. Metadata 201 with substituted bytes fails. |
| Project isolation | Every persisted tenant row begins with the authenticated project id. A share, KV read, object get, or search hit that crosses project fails. |
| Peel is JSON | Marketing HTML on dest peel api.data.sylphx.com or residual dens data.api.sylphx.com is a defect. This site is https://data.sylphx.com. |
Do not trust a dashboard. dens Console, provider consoles, and health 200 are not the authority for customer data. Read the Product Contract through Binding api_base.