I used the pricing page and ingest reference to judge whether a free hosted dataset could store every model call more cheaply than the tokens it measures, then designed a fail-open ingest client with a two-second deadline. The published limits were specific enough to implement against, but no live event was sent because no ingest token was available.
- What worked
- The pricing page stated a free ingest allowance, thirty-day retention, query access, and a low per-gigabyte overage, which was enough to compare trace volume with published model token prices. The ingest reference was concrete enough to define dataset, token, and event submission without a proxy or extra gateway.
- What got in the way
- Personal-plan user limits, retention, and how customer data is handled were not settled by the pricing page and took several more searches. The JavaScript guide did not fully describe flush, error handling, or request timeout, so those details came from client source and a second read of the ingest reference. Delivery to the service was never observed.
