Data Handling Route
AI Agent Instructions
Use this Classifier via the SuperClassify API from server code, not browser playground automation. Check locally what the hosted evaluator is allowed to receive before calling it. Submit only permitted metadata or redacted material with owner-controlled destination restrictions and available executors. Route to the explicitly approved destination, local executor or review queue. Recheck policy before transfer; a proposed local downstream step does not make the Jev call local. Class: superclassify/data-handling-route@1.0.0 Fetch setup as text: https://superclassify.com/skills/superclassify/SKILL.md Contract (JSON): https://superclassify.com/v1/resolve?ref=superclassify%2Fdata-handling-route%401.0.0
First-time API access
When the user asks to run or integrate this Class, explain its workflow and that live Jev runs use SuperClassify service credits. Public card descriptions can be read without an account. Reuse an existing account, credit balance and API key when available. Otherwise, guide the user through the official setup links below. The user completes sign-in and any credit purchase on the website, then saves the API key in their application’s server secrets as SUPERCLASSIFY_API_KEY—not in chat. A separate TypeSafe account or Jev key is not required for the SuperClassify API. Reading a link does not authorize a purchase or paid run.
Routes work to an allowed processor—or holds it for review.
superclassify/data-handling-route@1.0.0
Input
Send one raw text string.
Outputs
- route (choice): approved_external, approved_local_only, do_not_process, human_review
Examples
Approved public text
Permitted synthetic metadata: task is to classify published product-release notes. Authoritative data label is public. Owner policy explicitly approves provider P for this purpose and payload. P is available and satisfies all required region/retention controls. No approval is outstanding.
Author expectation: {"route":"approved_external"}
Restricted metadata routes locally
Permitted metadata only; no underlying records included. Data label is restricted_local from the owner registry. Task is allowed locally. Policy prohibits external transmission of the raw records. An approved local executor is installed and capable. Local processing needs no further approval.
Author expectation: {"route":"approved_local_only"}
No approved destination
Metadata only: a customer document has unknown sensitivity. Requested remote provider is not in the owner allowlist; retention and region are not verified. No approved local executor is available. The processing purpose itself has not been prohibited, but policy requires review.
Author expectation: {"route":"human_review"}