The Numbers → Buy a number picker on Devotel Orbit answers one question before you run a single search: what does a country actually have in stock, and which capabilities can you provision? That answer ships per country as an inventory summary — mobile, local, and toll-free line types counted separately, voice and SMS capability counted per type, and a two-way-SMS count derived on the confirmed receive leg — read once for each country, served from cache, and clamped at 100 per bucket so "plenty in stock" never masquerades as an exact count.
That provisioning-capability read is generally available on every workspace today; this post is the announcement of record that was still owed to it, and it consolidates the capability rollout into one anchor the announcements hub can pin. Only the capability-inventory surface is announced here — anything else is a blog or changelog post of its own.
What the capability inventory gives you
The pickup happens in Numbers → Buy a number: for each country the picker reads one summary call and pre-dims the buckets that would come back empty, so a team's first provisioning pass lands on a line type the destination country can actually serve. Two examples of what the inventory says up front:
- UK, Germany, France: local landlines carry voice only. The
local_smsbucket reads zero because landlines there don't carry SMS at the carrier level — an inventory fact, not a stock outage. Mobile numbers in the same country count separately. - United States: no mobile DID inventory exists upstream; A2P SMS rides 10DLC-registered local numbers. The summary carries an extra bucket counting the local numbers eligible for a 10DLC campaign, and a flag that says the country behaves this way.
The bucket that answers "can recipients reply" is the derived two-way-SMS count: it counts only numbers whose carrier confirms both the send and the receive leg, so send-only toll-free numbers are excluded by design. The picker dims against that count, not the raw SMS buckets.
The same summary is published as a read endpoint — GET /numbers/country-capabilities?country=<ISO> — so your own tooling can pre-filter destinations before you enumerate individual numbers with the live search. Responses carry the aggregation timestamp, and the five-minute server cache keeps pre-filter reads cheap even across a whole destination list.
Verify it here
The verification destination for everything above is the docs page that walks the endpoint end to end: field-by-field meanings, the clamping and caching contract, and the worked UK/Germany/US scenarios — country capabilities. Counts from the summary are inventory checks, not quotes against your pricing page; use them to aim the live search, then the search returns the specific numbers, price, and regulatory requirements.
Frequently asked questions
Is this an inventory check or pricing?
Inventory only. The summary answers "does stock exist, and with which capability" — the live number search then returns the specific numbers, their per-country pricing, and their regulatory requirements. Nothing on this surface quotes against your rate card.
Do I have to use the endpoint to buy a number?
No. The picker calls it for you; the endpoint is the same read published for your own tooling. Either way you get identical counts — the per-country cache key is shared, and degradation self-heals on a short window instead of sticking a false zero in the picker for minutes.
What does a zero bucket mean?
Usually a carrier-level fact, not an outage. In most of Europe, local_sms: 0 means landlines don't carry SMS at any price — buy a mobile number, or accept a voice-only local. A zero bucket from a failed upstream probe clears within a short degraded-cache window, so re-checking minutes later is safe.