canonical: https://jentic.com/apis/ideaconsult.net/ideaconsult-enanomapper

# Ideaconsult eNanoMapper federated search

eNanoMapper is a federated search service over a network of nanomaterial safety databases curated by IdeaConsult. The API exposes 13 endpoints covering free-text search, substance lookup, study and structural queries, similarity search via SMARTS patterns, and faceted browsing across the project corpus. It is designed for researchers building agent-driven literature reviews, regulatory dossiers, or hazard assessments that need consolidated access to nanomaterial data without scraping individual database websites.

## For AI agents

Run federated search and structural queries across the eNanoMapper nanomaterial database network, retrieving substances, studies, and similarity matches.

## Scope

Does not handle laboratory data ingestion, regulatory submission filing, or chemical synthesis planning - use for read-only federated search across nanomaterial databases only.

## Capabilities

- Run free-text search across federated nanomaterial databases via /select
- Retrieve substance records, including composition and structures, by UUID
- Pull study summaries attached to a specific substance for hazard assessment
- Run SMARTS substructure queries through `/enm/{db}/query/smarts`
- Find chemically similar substances via `/enm/{db}/query/similarity`
- Browse investigations and study collections within a specific database
- Use faceted filters to narrow large result sets by study type, endpoint, or organism

## Use cases

### Nanomaterial Literature Review

Researchers compile a literature review on a class of nanomaterials by running federated free-text searches across eNanoMapper databases via /select, then pulling study summaries for each matched substance. The API removes the need to manually search and reconcile records across separate database UIs.

Example prompt: Call GET /select with q=titanium+dioxide and aggregate matched substances, then for each call GET `/enm/{db}/substance/{uuid}/studySummary`

### Substructure-Based Substance Discovery

Find substances containing a specific functional group or structural motif using SMARTS pattern matching. The `/query/smarts` endpoint accepts a SMARTS string and returns matching substances, useful for grouping nanomaterials by surface chemistry or coating type before downstream analysis.

Example prompt: Call GET `/enm/{db}/query/smarts` with a SMARTS pattern and return all matching substances with their UUIDs

### Read-Across Similarity Lookup

Identify analog substances for a regulatory read-across argument by querying chemical similarity. The `/query/similarity` endpoint returns substances ranked by structural similarity to a reference compound, supporting hazard assessment when direct test data is sparse.

Example prompt: Submit a reference compound to GET `/enm/{db}/query/similarity` and rank the top 20 analogs by similarity score

### AI Agent Regulatory Dossier

A regulatory agent uses Jentic to find eNanoMapper operations matching 'gather nanomaterial study data', loads the substance and studySummary schemas, and assembles a structured dossier for a substance. The agent saves the regulator hours of manual database navigation.

Example prompt: Use Jentic search 'gather nanomaterial study data' to load the eNanoMapper studySummary schema, then execute it for a substance UUID

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/select` | Free-text federated search across the eNanoMapper corpus |
| GET | `/enm/{db}/substance` | List substances within a specific database |
| GET | `/enm/{db}/substance/{uuid}` | Retrieve a substance record by UUID |
| GET | `/enm/{db}/substance/{uuid}/study` | List studies attached to a substance |
| GET | `/enm/{db}/substance/{uuid}/studySummary` | Aggregated study summary for a substance |
| GET | `/enm/{db}/query/smarts` | Substructure search using SMARTS patterns |
| GET | `/enm/{db}/query/similarity` | Find structurally similar substances |

## Key resources

- **Search** — Free-text and faceted search across federated nanomaterial databases
- **Substances** — Retrieve substance records, composition, and structures by UUID
- **Studies** — Toxicology, ecotoxicology, and physicochemical study records
- **Structures** — Structural representations of substances and components
- **Data analysis** — Compound, similarity, and SMARTS substructure queries
- **Facets** — Filter aggregations over study type, endpoint, and organism
- **Task service** — Long-running query and analysis task management

## Why Jentic

- **Setup:** The eNanoMapper federated search takes no authentication, but wiring it by hand still means mapping its federated select and per-database substance routes and query encodings yourself. Through Jentic you install once, import the eNanoMapper federated search from the API Directory, and your agent calls it.
- **Permission scoping:** eNanoMapper puts the database and substance uuid in the URL path (`/enm/{db}/substance/{uuid}`), so a rule can pin your agent to reading substances and studies from one database. All of its endpoints are read-only searches, so you scope the agent to the queries it needs and nothing else.
- **Credential handling:** This API requires no credential, so there is nothing to store, and Jentic One runs the read-only search calls for your agent at execution time. No secret ever enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search nanomaterial substances' or 'find similar substances by structure', and Jentic returns the matching eNanoMapper operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **NANoREG federated search** — Sister API exposing the same federated search interface against the NANoREG nanomaterial dataset
- **EBI API** — European Bioinformatics Institute APIs covering molecular and chemical reference data
- **Clarivate API** — Scientific literature and citation data that pairs with eNanoMapper substance records

## FAQ

### What authentication does the eNanoMapper federated search API use?

The eNanoMapper federated search API does not declare an authentication scheme in its OpenAPI spec - endpoints are publicly readable for the project corpus. Through Jentic, requests are still routed and logged so agents can be governed centrally even on open APIs.

### Can I run substructure searches against eNanoMapper?

Yes. GET `/enm/{db}/query/smarts` accepts a SMARTS pattern and returns substances whose structures match the substructure. This is useful for grouping nanomaterials by functional group or coating before downstream similarity or hazard analysis.

### What are the rate limits for the eNanoMapper API?

The IdeaConsult-hosted eNanoMapper service does not publish hard rate limits in the OpenAPI spec. Federated queries can be expensive - design agents to back off on slow responses, prefer faceted filtering before deep result iteration, and use the task service endpoints for long-running similarity searches.

### How do I run a federated nanomaterial search through Jentic?

Run pip install jentic and import the SDK, then await client.search('search nanomaterial databases') to find the eNanoMapper /select operation. Load the schema and execute with a query string and any database filters. Run Jentic One, the self-hosted execution layer, for an API key.

### Which databases does eNanoMapper search?

eNanoMapper federates across the project's nanomaterial databases hosted at api.ideaconsult.net. The path parameter {db} selects which database to query - for the eNanoMapper main view, that is the eNanoMapper database; for NANoREG data, the sibling endpoint at /nanoreg1 is used. Both share the same query schema.

### Can I retrieve a study summary in one call?

Yes. GET `/enm/{db}/substance/{uuid}/studySummary` returns an aggregated summary of all studies attached to a substance, including endpoint outcomes and data sources. This is the recommended endpoint for dossier-building agents because it avoids fetching every individual study record.

### Can I limit what my agent is allowed to do with the eNanoMapper federated search API?

Yes. Because you run Jentic One self-hosted, your own rules decide which eNanoMapper operations the agent may call, and every endpoint is a read-only search, so you can grant only the queries the agent needs, such as free-text /select or a `/query/similarity` lookup. Since the database and substance UUID sit in the URL path (`/enm/{db}/substance/{uuid}`), a rule can pin the agent to reading substances and studies from a single database. The API takes no credentials, so scoping is purely about which operations you allow, and anything you do not permit stays out of reach.