Validate a UniProt accession
Exactbiotech_protein_validateDeterministic and authoritative — the canonical answer for this input.
Validate a UniProt accession's format and confirm it exists in the bundled human Swiss-Prot reviewed set. confidence 1.0 = valid format and present; 0.5 = valid format but absent (may be a non-human or unreviewed accession outside the set); 0.0 = not a UniProt accession format (exists is null there — the set was never consulted; false means a real membership miss). Fully local. Charges 1 cost_unit. Processing multiple inputs? Use `biotech_protein_validate_batch` to do up to 500 in one call.
Parameters
accessionstringrequiredThe UniProt accession to validate (e.g. 'P04637').
Call it
curl -X POST https://api.snipget.ai/v1/biotech/protein/validate \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{"accession":"P04637"}'The Batch tab sends up to 1000 inputs in one call via /v1/biotech/protein/validate/batch.
Example response
{
"accession": "P04637",
"format_valid": true,
"exists": true,
"entry_name": "P53_HUMAN",
"reviewed": true,
"note": null
}FAQ
Why use this?
It checks both that a UniProt accession is well-formed and that it actually exists in the human reviewed set, so you can catch invented or mistyped accessions that still look valid.
What does 'valid format but not found' mean?
Confidence 0.5: the accession is shaped correctly but isn't in the bundled human Swiss-Prot reviewed set. It may be a non-human or unreviewed (TrEMBL) entry that's real elsewhere, so read the note. A correct, present accession scores 1.0 and a malformed one scores 0.0.
What does it not do?
It validates and confirms existence. It does not return the full protein record (use protein lookup for that), and scope is human reviewed proteins only. matchType is exact, so the check is deterministic and authoritative.
What if I pass something that isn't an accession?
You get confidence 0 with format_valid false and a note, not an error.