# GeneaRoute

> Evidence-first genealogy routing for humans, developers, and agents.

GeneaRoute combines private family trees, review-first GEDCOM onboarding, public genealogy and archive routing, source-aware research, human-reviewed identity decisions, and guarded agent workflows. It is operated by Flygon LC.

## Primary machine interfaces

- [Developer documentation](https://genearoute.flygonlc.com/docs)
- [Markdown documentation](https://genearoute.flygonlc.com/docs.md)
- [OpenAPI 3.1 contract](https://genearoute.flygonlc.com/api/v1/openapi.json)
- [Hosted MCP endpoint](https://genearoute.flygonlc.com/api/mcp)
- [Provider capability catalog](https://genearoute.flygonlc.com/api/v1/providers)
- [Cross-workflow Research Pulse](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/research-pulse)
- [Evidence-aware Research Itinerary](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/research-itinerary)
- [Historical Jurisdiction Lens](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/place-audit)
- [Community Reconstruction Lab](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/community-reconstruction)
- [Lineage Proof Lab](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/lineage-proof)
- [Proof Narrative Copilot](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/lineage-proof/narrative)
- [Living Person Privacy Firewall](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/privacy-preflight)
- [Professional Engagement Ledger](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/professional-engagement)
- [GEDCOM X JSON export](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/exports/gedcomx?privacy=deceased_shareable)
- [GEDCOM Portability Report](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/gedcom-imports/{importId}/portability)
- [GEDCOM Delta Lab](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/gedcom-delta?from={fromImportId}&to={toImportId})
- [GEDCOM Update Planner](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/gedcom-update-plan?from={fromImportId}&to={toImportId})
- [Citation interoperability exports](https://genearoute.flygonlc.com/api/v1/projects/{projectId}/citations?format=csl-json)
- [Connector contract JSON Schemas](https://genearoute.flygonlc.com/api/v1/connectors/schema)
- [Service health and launch gate](https://genearoute.flygonlc.com/api/health)
- [Public agent policy](https://genearoute.flygonlc.com/AGENTS.md)
- [Privacy policy](https://genearoute.flygonlc.com/privacy)
- [Terms of use](https://genearoute.flygonlc.com/terms)

## Agent rules

- Authenticate HTTP and MCP requests with a customer-created, revocable GeneaRoute API key.
- Use a separate key for each agent so proposals and usage remain attributable.
- API keys may search, inspect, export, and propose structured change sets within their account permissions.
- API keys cannot accept or reject their own change sets. A signed-in owner or editor must review the exact fields, citation gaps, content seal, and reason statement.
- Treat provider matches, AI output, connection paths, and identity comparisons as research leads, not historical proof.
- Set acknowledgePrivateAiProcessing to true only after the user explicitly agrees to the described private AI workflow. An agent must not infer consent from possession of an API key.
- Tree Triage deterministic commands work with acknowledgePrivateAiProcessing false. Deceased-person source scans also work without AI. Living-person scans stay inside private GEDCOM and GeneaRoute's internal Commons index. Set the acknowledgment true only for the current optional AI synthesis or ambiguous chat request after explicit consent. GeneaRoute blocks living focus people from AI, withholds private matches and candidate names, and returns a metadata-only processing receipt.
- Never infer that two same-name profiles are the same person without a current human-reviewed identity conclusion.
- Do not submit living-person details, raw genotype data, passwords, session cookies, payment-card data, or another service's secrets.
- Preserve source URLs, quotations, repositories, locators, and uncertainty. Do not strip citations from a claim.
- Use CSL-JSON, RIS, or BibTeX when moving saved source metadata into compatible reference managers or research systems. GeneaRoute does not invent missing authors or dates.
- Respect provider terms, licenses, access controls, and rate limits.
- For Genealogy Event Hooks, verify the exact-body signature and timestamp, deduplicate the event ID, and never treat a delivery as permission to fetch unrelated private data. Professional events contain workflow IDs and bounded status or time metadata, never client labels, objectives, references, or descriptions.
- Use a separate project-bound key for each agent and keep its monthly route and AI-action caps below the account allowance. A zero cap disables that cost channel for the key; a blank cap shares the account ceiling.
- Treat Professional Engagement Ledger scope, time, and billable flags as researcher-entered workflow metadata, not an invoice, contract, time clock, or proof of work. Never submit payment-card data.

## Public and private boundaries

Public exploration is limited to records that the provider exposes and GeneaRoute is allowed to route. Private projects, GEDCOM files, living people, DNA match metadata, media, notes, and research history require account authorization. GeneaRoute does not publish an unavailable connector as live.