Blog·Note·

The price belongs next to the product

The phone pages had the price too far down. Moving it beside the example made the first screen answer the obvious question.

The phone lookup pages had examples, explanations, and a price further down. Looking at them, my reaction was basically: why is the price hidden all the way down here?

It was on the page. That wasn't enough. If you're looking at a result and deciding whether the API fits your project, cost is part of that decision. You shouldn't have to scroll past the rest of the explanation to find it.

I put a short price line directly under the main example, then carried that across the lookups with separate usage charges. The larger pricing section still has a job, but you can see the starting allowance and rate while you're looking at what the endpoint returns.

The details still need to be available. Included usage and additional-usage rates can differ by plan, and a short line can't explain every case. That's what the pricing section and cost questions are for.

But the first screen should give you enough to decide whether to keep reading. On the carrier page, the result and the price now sit together. That's where I expected to find them when I was looking at the page myself.