DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to sort a batch of texts into labels in one call with Classifier Dev

Label short texts with plain HTTP, no key or signup, up to a thousand per request.

Who it is forA developer or ops person with a list of messages, tickets or comments to triage and no time to set up a model.

The problemHand-sorting or hand-writing rules for a pile of short texts takes hours and breaks as wording changes.

The outcomeEach text gets a label and a calibrated confidence, returned as plain text that a script or agent can read.

What you need first

  • A terminal with curl or another HTTP client
  • npm, only if you want the classify CLI
  • The texts you want to label and a set of label names

Steps

  1. Run curl https://classifier.dev/spam,not+spam/Win+a+free+iPhone to see the path form return a label.
  2. Run curl "https://classifier.dev/?labels=spam,not+spam&text=Win+a+free+iPhone" to see the same call in query form, which is easier to build in code.
  3. Run curl classifier.dev to read the plain text docs for the batch form, since the batch syntax is not shown in the README excerpt.
  4. Send your texts in batches of up to a thousand per request using the batch form from the docs, and collect each label in order. (inferred, check the README)
  5. Write the input text and returned label side by side so you can spot-check the results.

Prompt for your agent

Using the classifier.dev API from the classifier-dev repo, label each text in <input file> as bug, feature or praise by calling https://classifier.dev over plain HTTP with no key. Write the results to <output file> as CSV with the original text and the label. Verify that the number of output rows equals the number of input rows.

Caveat. The README excerpt shows the single-text form and states the thousand-text limit, but not the exact batch syntax, so confirm it at classifier.dev before scripting.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page