Screen up to 25 candidates in one request
POST /clearance/batch accepts a list of names and an optional shared Nice class. It is available with Launch and Scale keys. Try these known apparel marks to inspect the results before submitting your own candidates:
curl "https://api.markbase.co/clearance/batch" \
-H "Content-Type: application/json" \
-H "x-api-key: $MARKBASE_API_KEY" \
-d '{"marks":["JUST DO IT","NIKE","ADIDAS"],"class":"25","limit":10}'The results array follows your input order. Each entry has the same mark, class, highest-risk, and match fields as the single-name clearance endpoint. Use usage.names to see how many names the batch contained.
One name consumes one monthly request: a 25-name shortlist uses 25 requests. If the remaining quota cannot cover the whole shortlist, the API rejects the batch. After a batch is accepted, its names count even if a search fails; retrying uses additional quota. Keep your key on the server and return only the fields your interface needs.
Include sound-alike evidence in a shortlist
Set phonetic: true in the batch to check every submitted name for whole-name sound-alikes. Show signals.phonetic alongside the spelling score and keep unsupported comparisons labeled not_evaluated. Launch and Scale batches still use one monthly request per name.
Show a useful shortlist, with the evidence attached
- Generate candidates, remove duplicate names, and identify the goods or services the user has in mind.
- Split larger lists into batches of up to 25 names. Submit separate batches when the relevant classes differ.
- Show similarity scores beside the matched marks and their statuses. Let users inspect each source record.
- Keep the original input order or clearly explain any ranking you add. Use a review label rather than a legal availability badge.
For a candidate that needs more context, follow its serial number to the full record. Goods and services, ownership, and filing history give a reviewer information that a score alone cannot provide.
Keep trademark results separate from other checks
A name generator might also check domains, social handles, and company registers. Keep those results distinct: an available domain is not a trademark clearance result. Markbase covers indexed US federal records; it does not search every country, state register, or common-law use.
For the shortlist a user intends to adopt, provide a route to professional review. The USPTO explains that trademark rights can also arise through use, which is one reason a federal search alone cannot establish availability.
Start with one name, then integrate the batch
Evaluate the scoring and response fields with the keyless single-name endpoint. When you are ready to screen whole shortlists, use a Launch or Scale key with the batch endpoint. Rate and monthly quota headers make the remaining capacity visible to your backend.
curl "https://api.markbase.co/clearance?mark=just%20do%20it&class=25"Build a more informed naming workflow
Explore single-name screening with a free key. Batch clearance on Launch and Scale adds multiple candidates per request when your product is ready for it.
curl "https://api.markbase.co/search?q=your-brand"Frequently asked questions
Which plans include bulk clearance?
Launch and Scale API keys can call POST /clearance/batch. Open and Free users can try individual names with GET /clearance before integrating a paid batch workflow.
How does a batch count toward quota?
Each submitted name counts as one monthly request. A batch with 25 names uses 25 requests, and the API rejects the whole batch if the key does not have enough monthly quota remaining.
Does a low-risk result mean a name is available?
No. The score describes similarity to retrieved US federal records. It does not establish legal availability, cover every source of trademark rights, or predict whether the USPTO will register a name.
Can I combine this with domain or company-name checks?
Yes. Show trademark screening as a separate result alongside those checks. A domain or company name being available does not mean trademark rights are clear.
