Search entities (people, companies, documents, ...) across every Aleph dataset you can read. This is the main entry point. Returns compact summaries with entity IDs to pass to the other tools. Request facets to see which countries or datasets the matches cluster in.

Fetch one entity by ID, with every populated property. Use after aleph_search to see the full record behind a hit.

List the entities connected to this one, grouped by relationship type (directorships, ownerships, addresses, family, document mentions). This is how you walk a network: relationships in Aleph are entities, so they do not appear as plain fields on the record itself.

Find entities that may be the same real-world person or company as this one, across other datasets. Use it to link a subject between a leak and a company registry. Results are ranked candidates, not confirmed matches — verify with birth dates, addresses or registration numbers.

List or search the datasets (collections) available to you — leaks, company registries, sanctions lists, court archives. Use it to discover what sources exist, then pass collection IDs to aleph_search to scope a query.

Full metadata for one dataset: publisher, source URL, coverage, update frequency and a breakdown of what entity types it contains. Use it to judge how far a source can be trusted and how current it is.

Read the cross-reference results already computed for a dataset: entities in it that resemble entities elsewhere in Aleph, scored and ranked. Useful for finding overlaps between your own casefile and public registries. Read-only — this does not start a new cross-reference run.

Size and shape of the Aleph instance: how many datasets and entities it holds, broken down by entity type, category and country. Use it to gauge coverage before concluding something is absent.

Reference for the followthemoney data model this instance uses. Call with no argument for the list of schemata; call with a name (Person, Company, Ownership, ...) for its properties and how it links to other schemata. Use it to pick the right schema filter or expand property.

Read the extracted text of a document entity (PDF page, email, article) so you can quote or verify what it actually says. Pass the entity ID of a Document, Pages, Email or similar entity from a search result.