Proto is not affiliated with SIB, EMBL-EBI, and PIR. This toolkit is open source and builds on the implementations produced by these organizations. Product names, logos, and trademarks are the property of their respective owners.
Background
UniProt (The UniProt Consortium, 2025) is the central, freely accessible resource for protein sequence and functional annotation, maintained by SIB, EMBL-EBI, and PIR. Its core database, UniProtKB, has two sections: Swiss-Prot, whose entries are manually reviewed and curated from the literature, and TrEMBL, whose entries are automatically annotated. As of release 2026_01 (January 2026), Swiss-Prot contains 574,627 reviewed entries, alongside hundreds of millions of unreviewed TrEMBL entries; current counts are published on the UniProt statistics page. Internally, the tool calls the UniProt REST API atrest.uniprot.org. Given an accession it fetches that UniProtKB entry directly; given a protein or gene name and an organism it runs a UniProt search and selects one entry deterministically, preferring an exact gene-name match, then optionally entries with linked PDB structures, then reviewed Swiss-Prot status. It extracts the sequence, length, review status, gene symbols, and PDB cross-references, and also returns the complete entry JSON; the fields option narrows the API response. Results reflect the live database at query time rather than a fixed release snapshot.
Records and their provenance come directly from UniProt’s official REST API, maintained by the UniProt consortium.
Learning Resources
- UniProt help and documentation (UniProt) - official documentation covering accessions, query syntax, return fields, and the REST API.
- Exploring protein sequence and functional information (EMBL-EBI Training) - a guided introduction to UniProt’s data and how to query it.
Tools
UniProt Fetch (uniprot-fetch)
Retrieves a single UniProtKB entry, either by accession or by a ranked name-and-organism search, and returns its sequence, length, gene names, review status, PDB cross-references, source URL, and the full entry JSON.API Reference
Input: UniProtFetchInput
Input: UniProtFetchInput
Config: UniProtFetchConfig
Config: UniProtFetchConfig
fields= query parameter — if set, restrict the API response to these fields. None (default) returns the full entry (~880 KB for human TP53); a targeted selection can shrink it ~1000x. Caveat: typed Output fields are only populated when the corresponding API field is included, so callers using accession / sequence / entry_type / gene_names / pdb_crossrefs must include "accession" / "sequence" / "reviewed" / "gene_names" / "xref_pdb". Search-mode ranking reads reviewed / gene_names / xref_pdb. Full list:True is coerced to 1 and False to 0.None waits indefinitely.BaseToolOutput.approx_equal), and the seed participates in cache keys. When None, cacheable seed-sensitive tools skip cache until seeded.Output: UniProtFetchOutput
Output: UniProtFetchOutput
Applications
Use this to pull a reference protein sequence and its annotation into a pipeline: fetch a target by accession before sequence design or optimization, resolve a gene symbol plus organism to a canonical reviewed entry, or discover which experimental structures are linked to a protein before structure-based work. The returned PDB identifiers feed directly into the PDB and AlphaFold DB tools.Usage Tips
- Provide either
uniprot_idor bothtarget_nameandorganism. An accession does a direct lookup; a name requires the organism to disambiguate, and the search returns the single best-ranked entry, not a list. prefer_pdb_crossrefonly affects search ranking. It biases the name-and-organism search toward entries with linked PDB structures; it has no effect on a direct accession lookup and never filters out entries that lack structures.fieldsnarrows the response but can blank typed outputs. Restrictingfieldsshrinks large entries substantially, but the typed outputs are only populated when their source fields are kept, so includeaccession,sequence,reviewed,gene_names, andxref_pdbif you read those.- Results track the live database. The same call can return updated annotation as UniProt releases change; it is not pinned to a fixed release.
Toolkit Notes
These apply to every UniProt tool in this toolkit (uniprot-fetch).
- Requires network access. The tool calls the live UniProt REST API; it does not run offline and keeps no local copy of the database.
- Subject to UniProt rate limits. Large or rapid batches may be throttled by the UniProt API; space out high-volume requests.
- Runs on CPU. There is no model and no GPU; latency is dominated by the network round-trip.

SIB
EMBL-EBI
PIR