One source-preserving API for historical records, private family trees, world-tree routes, and review-first AI workflows.
Use the HTTP API directly or connect the hosted MCP server to a compatible agent.
Open Account, generate a key, and keep it somewhere secure.
Call GET /api/v1/providers to see what is ready.
Every result keeps its provider, identifier, and original record link.
Bearer authentication, JSON responses, explicit provider failures, and an OpenAPI contract.
curl -X POST https://genearoute.flygonlc.com/api/v1/search \
-H "Authorization: Bearer $GENEAROUTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "Samuel Clemens",
"providers": ["wikitree", "wikidata", "loc", "internetarchive"],
"limit": 5
}'/api/v1/providersList available providers, authentication requirements, and capabilities.
/api/v1/searchSearch connected sources and receive normalized, source-preserving records.
/api/v1/wikitree/people/:keyExplore the public deceased family around a WikiTree profile.
/api/v1/wikidata/people/:idExplore deceased relatives around a Wikidata human while excluding living and unknown-status people.
/api/v1/wikitree/connectionsTrace a provider-reported route between two public profiles.
/api/v1/wikitree/connections/explainTurn a route into a cited, plain-language verification plan.
Connect to /api/mcp with the same account key. Tools can search, inspect, analyze, and propose changes. Structural changes still require a signed-in human review.
{
"mcpServers": {
"genearoute": {
"url": "https://genearoute.flygonlc.com/api/mcp",
"headers": {
"Authorization": "Bearer gr_live_..."
}
}
}
}Project endpoints use /api/v1/projects/:id as their base path.
Turn exact evidence gaps into journal-aware connected and offline itineraries, plan repository coverage, run name-variant sweeps, watch searches, preserve useful negatives, and export citations without silently changing a tree or inventing metadata.
/research-itinerary/research-coverage/research-watches/source-integrity/source-captures/citationsPrioritize cross-workflow review, audit historical jurisdiction, reconstruct time-bounded communities, preflight living-person privacy, challenge one-sided hypotheses, draft consent-gated lineage narratives, map provenance, and export reviewable or signed research packets.
/research-pulse/place-audit/community-reconstruction/lineage-proof/lineage-proof/narrative/privacy-preflight/hypothesis-challenge/evidence-audit/evidence-quality/evidence-map/proof-standard/proof-dossier/family-group-sheet/evidence-bundleReview identities, kinship, lineage documentation, provider mappings, and public-tree routes with explicit human decisions.
/identity-reviews/provider-links/kinship/lineage-proof/dna-correlation/world-tree-bridgeKeep privacy-minimized client scope and contributor time beside the evidence, stage reversible imports and agent work, poll sanitized events, or push signed metadata-only changes into customer-owned HTTPS workflows.
/professional-engagement/gedcom-imports/tree-checkpoints/agent-change-sets/events/webhooks/share-suggestionsMutations support unique Idempotency-Key values. Keep the returned x-request-id for support and audit trails.
Status describes the current connector path. Some providers still require your own authorization.
Public collaborative world tree with a documented read API.
A worldwide CC0 knowledge graph routed as deceased-person research leads with direct item provenance.
The largest shared family tree. Production access requires app approval.
Human-only, signed-in workspace search through the member's own OAuth connection. Geni is excluded from agents, API keys, MCP, CLI, automation, and AI processing.
A private, open-source genealogy database with a full REST API.
European cultural-heritage records and digitized archival sources.
Public Library of Congress collections with source metadata and links.
Digitized genealogy books, county histories, directories, cemetery records, and local publications.
Keyless full-text discovery across millions of digitized historic U.S. newspaper pages from the Library of Congress.
U.S. federal archival descriptions and digital-object metadata through the read-only Catalog API. Production activation requires an approved key.
Portable local family-tree files that remain under the user's control.
GeneaRoute helps organize evidence. It does not turn an automated match into historical truth.
Provider IDs, citations, and record links survive normalization.
Public workflows fail closed when living status is unknown.
Agents can propose structural work, but cannot approve it themselves.
Possible matches do not become merges until the evidence supports them.
Connectors respect licenses, access controls, attribution, and rate limits.
Users can export private trees, evidence records, signed bundles, and interoperable CSL-JSON, RIS, or BibTeX citations.
Every plan includes private trees, API access, MCP, GEDCOM import, and review-first workflows. Professional includes commercial API use.
Compare full plan details50 searches
3 projects · 1 key
2,000 searches
25 projects · 5 keys
20,000 searches
200 projects · commercial use