fairdata.ai valid

FAIRdata.ai

Research data, prepared for the machines that use it. FAIRdata.ai turns public

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T18:43:31.758Z. Cached copy · Source on fairdata.ai

# FAIRdata.ai

> Research data, prepared for the machines that use it. FAIRdata.ai turns public
> academic datasets into evidence-checked, machine-readable records, collections
> and ingestion recipes, so models, agents and research workflows can find,
> understand and use them more responsibly.

## What this is

A public registry of research datasets, assessed for FAIR metadata quality and
curation evidence, with normalised licence signals and resolved file URLs. The
qualifying subset is organised into themed collections with versioned manifests.

Public read access requires no authentication. Rate limit: 240 requests per 60
seconds per client IP, reported in RateLimit-* headers.

## What "qualified" means here

A dataset is Machine-Ready when: source-record FAIR composite >= 75 AND curation-evidence proxy >= 50 AND an unambiguous permissive licence signal AND at least one declared file format AND a direct file URL resolved at assessment time.

Read the full ruleset — every criterion, threshold, evidence type and status —
at https://fairdata.ai/api/v1/qualification/ruleset.

## What it does NOT mean

Machine-readable does not mean permission to train. Qualification does not
establish that data are scientifically correct, representative, free of personal
or sensitive information, covered by appropriate consent, or legally available
for any particular use. Licence detection and discipline classification are
automated and can be wrong. File access is resolved point-in-time.

Every qualification response includes a "limits" array. If you relay a status,
relay the limits with it.

## Endpoints for agents (no key required)

- GET https://fairdata.ai/api/v1/meta — capabilities, collection version, ruleset, formats, error catalogue
- GET https://fairdata.ai/api/v1/health — service and data freshness
- GET https://fairdata.ai/api/v1/collections — collections with real aggregates
- GET https://fairdata.ai/api/v1/collections/{id} — one collection
- GET https://fairdata.ai/api/v1/collections/{id}/qualification — per-criterion evidence
- GET https://fairdata.ai/api/v1/collections/{id}/datasets — members, filtered and paginated
- GET https://fairdata.ai/api/v1/collections/{id}/manifest — versioned manifest with checksum
- GET https://fairdata.ai/api/v1/collections/{id}/croissant — Croissant 1.0 JSON-LD
- GET https://fairdata.ai/api/v1/collections/{id}/receipt — fairdata.lock.json
- GET https://fairdata.ai/api/v1/collections/versions — published versions and retention
- GET https://fairdata.ai/api/v1/datasets/resolve?doi={doi} — resolve a DOI
- GET https://fairdata.ai/api/v1/search?q={query} — substring search over qualifying datasets
- GET https://fairdata.ai/api/record/{doi} — the full enriched record (whole registry)
- GET https://fairdata.ai/api/record/{doi}/{schema.org|croissant|ro-crate|fdp|datacite|ai-readiness}
- GET https://fairdata.ai/api/record/{doi}/files — resolved file listing
- GET https://fairdata.ai/api/search/semantic?q={query} — meaning-base
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=fairdata.ai · GET /v1/domain/fairdata.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fairdata.ai:
1. POST https://agentwebmap.com/v1/sites/fairdata.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fairdata.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fairdata.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fairdata.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.