Provider page specification
- Catalogue
- Models, endpoints and prices
- Measured traffic
- Performance observed through Navis
Navis
Lead Product Designer · FineLine / Navis
Make the source of each number visible.
The provider-page specification separates listed AI model capabilities from performance measured through Navis. It also defines what readers see when a measurement is absent, sparse or unavailable.
- Listed
- Models, endpoints and prices from the catalogue
- Measured
- Requests and performance observed through Navis
Separate listed and measured data
A catalogue can tell a visitor which models a provider offers and what its endpoints cost. To assess latency or reliability through Navis, a visitor needs data from actual Navis requests. The provider brief keeps the two sources in separate parts of the page.
The catalogue keeps its snapshot date visible. A measured result carries its period, scope, unit and sample size where applicable, so readers can judge how much that number tells them.
- No traffic
- Replace the measurement section with an explanation
- Sparse samples
- Show the sample size and leave a gap
- Unavailable data
- Give the reason the metric is unavailable
Design for missing measurements
When Navis has never served traffic through a provider, the page can still show the catalogue. The measurement section makes way for a short explanation instead of reserving space for charts.
With too few observations, the brief keeps the sample size visible and leaves gaps in the series. Error rates and uptime depend on backend attribution. Until that data exists, an explanation takes the place of a rate.
- Provider profile
- Models and endpoints
- Traffic through Navis, when available
- Availability and limits
Reflow the same evidence on mobile
The mobile specification stacks endpoint rows and metric cards. A model price keeps the same unit and source when its row becomes a card, and the conditions for showing measured traffic stay the same at each width.
The design repository records six page briefs: Home, Model, Provider, Blog, Article and Trust Center. This case covers the Provider specification, with desktop and mobile references. The diagrams illustrate the design rules.
Read the note on missing data