A pretrained if a document is edited classifier that sorts an image into one of 2 categories. Use the if a document is edited API immediately, no training required, then adapt it to your own data when you need more.
Drop in a photo 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.
Once you've added this classifier to your console, you get your own copy of it behind your own endpoint. Invoke it with any HTTP client:
curl
curl -X POST "https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke" \
-H "Authorization: Bearer $NYCKEL_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data": "https://example.com/photo.jpg"}'
Python
import requests
# Get an access token: https://www.nyckel.com/docs/api/overview/authentication/
token = "YOUR_ACCESS_TOKEN"
response = requests.post(
"https://www.nyckel.com/v1/functions/YOUR_FUNCTION_ID/invoke",
headers={"Authorization": "Bearer " + token},
json={"data": "https://example.com/photo.jpg"},
)
print(response.json())
Example response
{
"labelName": "Edited Document",
"labelId": "label_...",
"confidence": 0.92
}
Trained on a Nyckel-curated dataset covering 2 if a document is edited categories, served on Nyckel's own infrastructure — your image stays on Nyckel.
Send an image URL or file 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 the identifier to manage version histories of documents effectively. By recognizing when a document has been edited, teams can ensure that they are always working with the most current and relevant information, thus minimizing errors.
Companies can employ the identifier to ensure compliance with regulatory standards that require document integrity. By flagging edited documents, businesses can track changes and maintain audit trails for legal and compliance purposes.
The identifier can be integrated into content management systems to trigger approval workflows for edited documents. When a document is modified, it can automatically notify stakeholders for review, helping to streamline collaboration and maintain quality control.
Researchers and analysts can utilize the identifier to analyze changes made to important documents over time. This feature allows for retrospective insights into edits, helping organizations understand decision-making processes and trends.
The document edited identifier can be used as part of a security framework to monitor unauthorized changes. By detecting edits, organizations can safeguard sensitive information and enforce access controls more effectively.
Marketing teams can leverage the identifier to tailor content strategies by analyzing which documents were frequently edited. This can provide insights into customer preferences, enabling more effective targeting and engagement.
Educational institutions can use the identifier to track edits in training materials or coursework. By doing so, they can evaluate the effectiveness of learning resources and improve training programs based on the frequency and nature of document edits.
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 images 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 a document is edited 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.