Classify a text with caller-defined checks
POST/v1/classify
Answers yes/no checks of one text with Jev, through the proxium loop: authentication, the budget, routing and cost. Each check gets a probability. The answer names the flagged check with the highest probability as classification, and lists every flagged check in flags. The checks are the presets of proxium (checks) and the caller's own questions (questions). The feature is granted by plan.
Request
Responses
- 200
- 400
- 401
- 403
- 429
- 503
The classification: classification, probability, flagged, flags, results, input_truncated and model.
A refused request, with its code: bad_request, no_questions, too_many_questions, unknown_check, invalid_question or duplicate_question. A route that does not start with a Jev model answers no_route. A request that Jev refused with a 4xx answers Jev's status with upstream_refused.
The bearer virtual key is missing (missing_key), or it is not valid or it is revoked (invalid_key).
The route of the project starts with the platform Jev and the project has no classify grant (jev_not_granted). A project with its own System One endpoint needs no grant. Or: A content rule of the project blocked the request (guardrail_blocked). The message names the class and the field. It never holds the matched value.
Jev answered 429 (rate_limited), with Jev's wait in retry-after. Or: The key or the source used its budget window (tenant_capped or source_capped, retry-after: 60), or the project reached a monthly cap (credits_exhausted, retry-after: 3600).
Response Headers
Seconds to wait before the next call.
Jev failed or did not answer (upstream_failed), its answer has no probability for each check (bad_upstream_response), or no Jev model of the route can take the call (upstream_failed). A failed call is sent again to the same Jev model as the retry setting of the project allows.
Response Headers
Seconds to wait before the next call.