A pretrained if tax id is in an email classifier that sorts text into one of 2 categories. Use the if tax id is in an email API immediately, no training required, then adapt it to your own data when you need more.
Drop in some text and get the prediction back. No signup, no setup.
A sample of the 2 labels this pretrained classifier chooses between.
Need a label that isn't here? Clone the classifier into your Nyckel console and edit the label set to fit your data.
Get your own copy of this classifier behind your own endpoint — callable from any HTTP client:
curl -X POST "https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data": "The text you want to classify"}'import requests
response = requests.post(
"https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke",
headers={"Authorization": "Bearer YOUR_ACCESS_TOKEN"},
json={"data": "The text you want to classify"},
)
print(response.json())const response = await fetch("https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke", {
method: "POST",
headers: {
"Authorization": "Bearer YOUR_ACCESS_TOKEN",
"Content-Type": "application/json",
},
body: JSON.stringify({ data: "The text you want to classify" }),
});
console.log(await response.json());$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, '{"data": "The text you want to classify"}');
$headers = array();
$headers[] = 'Authorization: Bearer YOUR_ACCESS_TOKEN';
$headers[] = 'Content-Type: application/json';
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
$result = curl_exec($ch);
curl_close($ch);
echo $result;Example response
{
"labelName": "Tax Id Absent",
"labelId": "label_...",
"confidence": 0.92
}Trained on a Nyckel-curated dataset covering 2 if tax id is in an email categories, served on Nyckel's own infrastructure — your text snippet stays on Nyckel.
Send raw text to the invoke endpoint; the response is a label with a confidence score.
Clone it, then correct predictions and add your own samples in the console — Nyckel retrains automatically, turning this into a custom model tuned to your data.
Organizations can use this text classification function to automatically identify emails containing potential fraudulent tax IDs. By flagging these emails, companies can enhance their security protocols and prevent tax-related identity theft before it occurs.
Financial departments can implement this function to expedite the processing of invoices and tax-related documents by automatically extracting relevant tax IDs. This reduces manual effort, increases efficiency, and minimizes the chances of errors in data entry.
Companies in regulated industries can utilize this function to monitor communications for compliance with tax regulations. By ensuring that tax IDs are included and correctly handled in emails, businesses can maintain better compliance with relevant laws.
Customer support teams can integrate this classification function to quickly identify customer inquiries related to tax ID issues. By automating this identification process, support agents can provide faster and more accurate responses to customer concerns.
Businesses that conduct regular audits can use this function to identify relevant emails containing tax IDs for integration into datasets. This aids in consolidating and organizing tax-related information, making it easier for data analysis and reporting.
Marketing teams can leverage this function to ensure that any outreach or campaign communications comply with privacy regulations involving tax IDs. By filtering out emails that contain sensitive information, companies can protect themselves from potential legal issues.
Risk management teams can use this classification function to monitor emails for tax IDs as part of their overall risk assessment strategies. By proactively identifying and reviewing interactions involving sensitive tax information, organizations can better mitigate risks associated with data breaches and fraud.
A zero-shot classifier uses a large foundation model's general knowledge to pick between your labels — no task-specific training, so new or edited labels work immediately. A Nyckel-trained classifier has been trained on labeled examples and runs on Nyckel's own infrastructure, which typically makes it faster, cheaper per call, and more accurate on data that resembles its training set. The "Under the hood" section on this page shows which kind this classifier is, and any classifier can be adapted into a trained one by adding your own examples.
Honestly: we can't know in advance — it depends on your data stream and how closely it resembles what this classifier has seen. The reliable way to find out is to measure it on your own data: start invoking the classifier with real traffic, or upload and annotate a set of text samples in the console — make sure they look like your production data, not idealized examples. Nyckel's evaluation metrics then show you exactly how it performs on that data before you rely on it.
No classifier is perfect, so Nyckel is built around the correction loop: invokes can be captured for review, you confirm or correct predictions in the console, and corrections become training data. Over time the model adapts to your data distribution — accuracy on your traffic improves with use rather than staying fixed.
No. This if tax id is in an email classifier works out of the box — clone it into your console and you'll have your own API endpoint in under a minute. Training data only enters the picture when you want to adapt it: your corrected predictions and uploaded samples improve the model, and you can also edit the label set to match your needs.
Trying the classifier on this page is free with no signup. Cloning it requires a free account, and the free tier covers your first API calls each month — see nyckel.com/pricing for current limits and paid tiers.
Add this pretrained classifier to your Nyckel console — you'll get a live API endpoint in under a minute, and a path to a custom model when you need one.