COI reference sequences from BOLD DB

Open data API in a single place

Provided by Naturhistoriska riksmuseet

Get early access to COI reference sequences from BOLD DB API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.02.06 00:00
Created
2026.02.06
Available languages
English
Keywords
Ecology not elsewhere classified, Computational ecology and phylogenetics, Bioinformatics and computational biology not elsewhere classified
Quality scoring

Dataset description

Dataset descriptionThis item contains COI (mitochondrial cytochrome oxidase subunit I) sequences collected from the BOLD database. The dataset is based on the BOLD Data Package (https://boldsystems.org/data/data-packages/) from 30 January 2026 and was created on February 1 2026. The fasta file coidb.clustered.fasta.gz represents a non-redundant set of filtered sequences (clustered at 100% identity, see Methods) with record ids that can be queried in the Public Data Portal (https://portal.boldsystems.org/) . Each fasta header also contains the BIN ID assigned to the record (with the exception of prokaryotic records which instead have process ids as BIN IDs). The taxonomic information for all filtered records is given in the tab-separated file coidb.info.tsv.gz. Files compatible with specific tools for taxonomic assignments are found under the dada2/, sintax/, and qiime2/ folders. MethodsThis dataset was generated with the coidb (https://github.com/insect-biome-atlas/coidb) package (v0.6.0). Briefly, records from the BOLD Data Package are filtered to - keep only records assigned a proper BOLD BIN (e.g. `BOLD:AAA0008`), as well as records assigned to Bacteria or Archaea - keep only records with marker_code 'COI-5P' - remove records shorter than 500 bp - remove records containing non-standard DNA characters Remaining sequences are then clustered at 100% identity separately for each BOLD BIN using vsearch (Rognes et al. 2016) (records without BOLD BINs that are assigned to Bacteria/Archaea are not clustered). The taxonomic information for records is processed to handle missing data and non-unique parent lineages. A consensus taxonomy for each BOLD BIN is calculated by taking into account the taxonomic information given for records assigned to each BIN. This is done in two ways: - the `inclNA` method calculates a consensus based on all taxonomic labels, even the ones with missing data - the `exclNA` method excludes taxonomic labels with missing data when calculating the consensus Because these methods have their pros and cons (in short `exclNA` resolves more species but `inclNA` is more conservative) both versions of downstream files are available in this item and it is up to the user to decide which one to use. Description of files- coidb.clustered.fasta.gz This file contains nucleotide sequences of all filtered records, clustered at 100% identity within each BOLD BIN. The fasta headers have the format: >{processid} bin_uri:{BOLD BIN} where '{processid}' corresponds to the record identifier chosen as the cluster centroid and '{BOLD BIN}' shows which BOLD BIN the record belongs to. - coidb.info.tsv.gz This file contains taxonomic information (including BOLD BIN where applicable) as well as nucleotide sequences for all filtered records. - coidb.stats.exclNA.txt / coidb.stats.inclNA.txt These files contain summary statistics with number of total records, unique BINs, clustered sequences etc. The first seven lines are identical as they refer to general statistics of the database while the rest is specific to the method used to calculate the consensus taxonomy (see Methods). - timestamps.txt This file shows the name of the BOLD Data Package and the TSV file extracted andused as input to coidb. - logs/fix_nonunique.coidb.log This logfile shows how taxa with non-unique parent lineages were modified during database creation. - shasum.txt This file contains checksums and can be used to verify file integrity by running shasum -c shasum.txtTool-specific filesDADA2 The dada2/ folder contains fasta files that are compatible with the DADA2 assignTaxonomy and addSpecies functions. See more information at https://benjjneb.github.io/dada2/assign.html. The files wtih 'toGenus' and 'toSpecies' in their names have taxonomic information down to the genus and species level, respectively. The files with 'addSpecies' contain only the species name and should be used with the 'addSpecies' function. SINTAX The sintax/ folder contains fasta files that are compatible with taxonomic assignments using the SINTAX algorithm as implemented in `vsearch`. See more information in the vsearch manual (https://github.com/torognes/vsearch/releases/download/v2.30.4/vsearch_manual.pdf) . QIIME2 The qiime2/ folder contains info files that can be imported with QIIME2. For more information, see the README file at https://github.com/insect-biome-atlas/coidb.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks