Skip to content
Animiyo
Technology and data10 min readUpdated on July 22, 2026

The open data behind a product record: what it holds and what it is worth

Where the data on a food or drug record comes from, who maintains it, which limits it carries and how to check an open source in a few minutes.

Audience
Veterinarians, Pet shops, Pet owners
Species
All species
Scope
Valid everywhere, European Union

When an application shows the record of a food or of an active substance, that page does not come from a single official archive. It comes from several independent databases, each with its own history, collection method and level of completeness. Some are compiled by volunteers, some by a regulatory agency, others are chemical libraries built for research rather than for the clinic. Anyone working with those records, behind a counter or in a consulting room, needs to know which question each source can carry and which one sends it off the rails. Below are the open databases actually in use, the kind of data they hold and the checks that let you trust a line before making a decision about a living animal.

What makes a database open

A database is open when anyone can download it, read it with a machine and reuse it, with the sole duty of crediting it and keeping derived works open. Open does not mean verified: the licence describes what you may do with the data, not how correct that data is. The two properties must be kept apart, because a source that is very permissive about reuse can be very uneven in quality.

  • An explicit licence allowing reuse, usually with attribution and share alike conditions.
  • Access without a commercial key and without an individual contract: everyone queries the same service under the same rules.
  • A machine readable format, not only a page designed for human eyes.
  • Declared governance: you can tell who accepts changes, through which process and how long they take to appear.

The last point is the one that weighs most in daily use. A database run by a public agency publishes updates at regular intervals through a documented procedure. A collaborative database accepts contributions continuously, so it grows quickly but can hold a wrong line for days, entered in good faith.

The sources that feed a record

The databases listed below are the ones that genuinely underpin records of foods, drugs, substances and places. Each row states the kind of data, who maintains it and the limit you hit first when you try to push it beyond its purpose.

Open databases behind the records and the main limit of each
SourceKind of dataMain limit
Open Pet Food FactsFood products with barcode, ingredients and analytical constituents transcribed from the labelVery uneven completeness: a product may exist with a name only and no nutritional values
openFDAAdverse event reports for veterinary drugs collected by the United States agencyNo denominator: you cannot know how many animals received the drug without any problem
PubChemChemical records with structure, identifiers and hazard classificationBuilt for chemical research: it rarely holds toxic thresholds for companion species
OpenStreetMap with OverpassPlaces, opening hours and contact details entered by contributorsUneven coverage by area: hours and phone numbers can stay stale for months
Open-MeteoHourly weather forecasts and archives from public modelsIt describes a grid cell, not the microclimate of your yard or of the street you walk
WikipediaEncyclopaedic descriptions, used for breed profilesEditorial text without formal clinical review, with quality that varies between languages
frankfurter.appCurrency rates derived from the European Central Bank reference ratesUpdated on working days: at the weekend the last published figure remains in force

None of these sources requires a paid key. That is a verifiable choice rather than a statement of intent: the full list, saying which call leaves from the server and which from the device, sits on the integrations page and is kept aligned with the feature catalogue by an automated check.

Where the data holds and where it does not

The most frequent mistake is not picking the wrong source but asking it a question it cannot carry. A geographic database knows where a clinic is, not whether a vet is on duty right now. A chemical database knows what a molecule is, not how much of it will harm a small cat.

Questions asked of a record and the answer actually available
QuestionSource that answersWhat it does not say
How much protein does this food declareOpen Pet Food Facts, if someone transcribed the labelWhether the value matches the latest reformulation of the product
Is this substance classified as hazardousPubChem, with the harmonised hazard classificationThe amount that becomes relevant for a given species and body weight
Have reactions been reported with this active substanceopenFDA, with the reported reaction termsWhether the drug caused the event and at what real frequency
Where is the nearest dog parkOpenStreetMap queried through OverpassWhether the gate is open today and what state the ground is in
Will it be too hot for the four o'clock walkOpen-Meteo, with hourly temperature and humidityThe actual asphalt temperature under the paws at that spot

Rewriting the question into a form the source can carry is almost always possible and changes the value of the answer. Instead of asking whether a food is suitable, ask what the label declares and compare that figure with the energy requirement worked out separately. Instead of asking whether a substance is dangerous, ask whether it is classified as such and take the quantitative question to whoever holds the toxicological references.

Reports are not incidence

Pharmacovigilance archives are the most valuable and most misread open source. They collect spontaneous reports: someone observed an event after an administration and reported it. Neither causation nor frequency follows from that. A high number of reports may reflect a widely sold product, a press campaign or a particularly active reporting network.

  • The denominator is missing: you know the reported events, not the total administrations, so no rate can be computed.
  • Under reporting is the norm: mild and expected events are reported far less often than severe or unexpected ones.
  • Causation is not established: the same record may describe a drug reaction, disease progression or a coincidence.
  • Comparing products is not legitimate: two molecules with different sales volumes and populations are not comparable on raw counts.

Checking a record in a few minutes

Before basing a decision on a record it is worth spending the time of four checks. They are quick and they catch almost every error that matters, meaning the ones that would change the choice.

  1. Compare with the physical object

    If you have the pack in hand, read two values off the label and look for them in the record. A mismatch on an analytical constituent signals an old transcription, or one taken from a different pack size of the same product.

  2. Look at the date and the unit

    Every line should carry the date of the value and the unit it is expressed in. A figure without a unit or without a date is not data: it is a number, and it compares to nothing.

  3. Ask who wrote it

    In collaborative databases the edit history is public and shows how many people touched that entry. A record with a single contribution and no label photograph should be treated as a draft.

  4. Look for a second independent source

    If the value bears on a clinical decision or a repeat purchase, confirm it with a source that does not derive from the first. Two websites copying the same archive are not two confirmations.

When open data is not enough

Some information sits in no queryable archive and comes from guidelines and reference literature: vaccination protocols, recommended recalls, growth charts, interaction references between molecules, European regulatory documentation on veterinary medicines. In the product these sources are transcribed as references and generate no network call at all: no external provider is contacted when a recommendation is consulted.

  • International and national vaccination guidelines: they define core components, intervals and criteria for antibody titre testing.
  • Consensus statements from specialist societies: used for interaction checks inside treatment plans.
  • European regulatory documentation on veterinary medicines: the basis of authorised product information.
  • Reference growth charts: they support the puppy growth curve and comparison with the population.

The distinction between a queried source and a transcribed reference has a practical privacy consequence. A call leaving from the browser shows the provider the address of the user device; a call leaving from the server shows only the address of the infrastructure; a reference shows nothing to anyone, because no request exists.

How Animiyo declares its own sources

Features that rely on external data declare the source in the catalogue, and the integrations page collects the list with the host contacted and the place the call leaves from. An automated check prevents a feature from citing a source not described in the register, so the list cannot quietly go stale while the product changes.

  • Food records, label reading and product comparison in the nutrition area: they rely on Open Pet Food Facts.
  • Active substance records, adverse reaction reports and co reported reactions in the medicines area: they rely on openFDA.
  • Toxic plant and substance records in the toxicology area: they rely on PubChem for identifiers and chemical classification.
  • Useful places, parks, water points and clinics currently open: they rely on OpenStreetMap queried through Overpass.
  • Environmental indices such as parasite risk, heatstroke, air quality and the usable walking window: they rely on Open-Meteo.

Frequently asked questions

Is open data less reliable than commercial data?
Not by virtue of being open. A paid archive can be curated or neglected exactly like a free one. The difference lies in the review process and in the traceability of changes, and on that point open databases are often more transparent, because they publicly show who changed what and when. What is almost always missing is the contractual guarantee: nobody answers for the correctness of a line entered by a volunteer.
Why does a food record come out incomplete?
Because collaborative databases grow through single contributions. One person photographs the pack and enters the barcode, another transcribes the ingredients, a third adds the analytical constituents. If nobody completed the third step, the product exists without nutritional values. Photographing the label and uploading it is the quickest way to fill that gap, including for yourself at the next purchase.
Do reports tell you how risky a drug is?
No. They tell you which events someone observed and reported after an administration. The number of animals treated without any problem is missing, so no frequency can be derived, and causation has not been established. They serve to build a suspicion and to decide what to keep under observation, while risk assessment rests on the authorised product documentation and on the clinical history of the individual animal.
What happens if an external source stops working?
Features that depend on a queried source lose that data and say so. Features resting on references transcribed in the code, such as vaccination protocols or growth charts, keep working because they make no network call. This is why it is worth exporting the data you entered yourself from time to time: that data stays yours and depends on no external service.

What to do next

Before using a record, ask yourself which question the source can carry and look for the date of the value and its unit. If the decision concerns an administration or a repeat purchase, compare the physical label with the record and find a second independent source. The integrations page lists every database in use, the host contacted and the point the call leaves from: read it once and you will know what the pages you consult every day are made of.

Related content

The open data behind a product record: what it holds and what it is worth · Animiyo