rubricaryalpha
ExploreValidatorDocsPricing
/
  • Validate a prompt
  • Health checks
  • API keys
API

Validate a prompt

POST /api/validate scores an arbitrary system prompt against the same rubric as /validate and the MCP server's validate_prompt tool — all three go through one guard chain and share one rate limit, so a status you get from curl matches what the page would show.

bash
1curl -X POST https://app.rubricary.com/api/validate \
2 -H "Content-Type: application/json" \
3 -d '{"text": "You are a support agent for Acme..."}'

A successful call returns the score, the criteria it was checked against, and how many free runs remain:

json
1{
2 "score": 78,
3 "band": "good",
4 "findings": [ /* one entry per rubric criterion */ ],
5 "freeRemaining": 1
6}

No key is required and none is accepted — the endpoint is anonymous by design, metered by IP and account instead:

StatusReasonMeaning
400—Request body is missing or empty text.
401sign_in_requiredThe 2 free anonymous validations are used up.
413too_longPrompt text is over 12,000 characters.
429ip_quota / user_quotaDaily quota reached — 10 per IP, 50 per signed-in account. Resets at midnight UTC.
503budget_exhaustedThe validator's model budget for the period is spent.
502—The configured provider could not be reached.

Full detail on what happens to the text you send — what's kept, what's hashed, what's never stored — is in What the validator does with your text.

PreviousWhat the validator does with your textNextHealth checks
© 2026 rubricarydocsapipricingsecuritystatustermsprivacyv0.9.3 · 9e073c4All systems operational