Clinicaltables Nlm Nih Gov NIH Clinical Table Search Service - NCBI Genes API
★ Only Publicly Available OpenAPI DocumentHealthcareClinical Datanone1 EndpointsREST
For Agents
Search NCBI's human gene dataset by name, symbol, or synonym. One unauthenticated GET endpoint returning gene IDs and official symbols.
Use for: Search NCBI for the gene symbol BRCA1, Find all synonyms recorded for the TP53 gene, Look up the NCBI gene ID for KRAS, Validate whether a given gene symbol exists in the NCBI dataset
Not supported: Does not handle non-human organisms, gene-variant interpretation, or other NLM clinical tables — use for human gene name and symbol lookup only.
Jentic publishes the only available OpenAPI specification for NIH Clinical Table Search Service - NCBI Genes API, keeping it validated and agent-ready. This public API from the US National Library of Medicine returns matching human gene records from NCBI's gene_info dataset. The single GET /api/ncbi_genes/v3/search endpoint accepts a query string and returns gene IDs, official symbols, and synonyms — useful for autocomplete on clinical forms, variant research tooling, and any agent that needs to resolve a gene name to a structured record. No API key is required.
Install Jentic One Beta
Connect the NIH Clinical Table Search Service - NCBI Genes API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NIH Clinical Table Search Service - NCBI Genes API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NIH Clinical Table Search Service - NCBI Genes API.
Search human gene records by official symbol, full name, or synonym
Resolve a free-text gene mention to a structured NCBI gene record
Power autocomplete and typeahead widgets for gene-name input fields
Validate that a candidate gene symbol exists in NCBI's curated dataset
Retrieve a list of matching gene IDs and symbols for a research query
Use Cases
Patterns agents use NIH Clinical Table Search Service - NCBI Genes API for, with concrete tasks.
★ Gene-Name Autocomplete in Clinical Forms
Clinical and research forms that ask users to enter a gene name need to validate and disambiguate the input. GET /api/ncbi_genes/v3/search returns matching gene records as the user types, so the form can show official symbols and offer completion. The endpoint is public and unauthenticated, which removes the credential plumbing usually required for clinical reference APIs.
GET /api/ncbi_genes/v3/search?terms=BRCA and return the top matching official symbols for typeahead display
Variant Research Mention Resolution
Variant research pipelines often ingest free text that mentions genes by inconsistent names (HER2, ERBB2). Querying NCBI's curated dataset resolves each mention to a single NCBI gene ID and official symbol so downstream analysis is consistent regardless of which synonym appeared in the source text.
For each gene mention in the input text, GET /api/ncbi_genes/v3/search?terms=<mention> and store the canonical official symbol and NCBI ID
Agent-Driven Gene Lookup
An AI agent answering biology questions uses Jentic to resolve gene names mentioned in a user query. Jentic returns the NCBI Genes search endpoint, the agent loads the schema, executes the unauthenticated GET, and uses the response to ground its answer in NCBI's curated gene record rather than relying on its training data.
Use Jentic to search for find gene by name, load the schema for GET /api/ncbi_genes/v3/search, and execute with the user-mentioned gene symbol
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for nih clinical table search service - ncbi genes api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/api/ncbi_genes/v3/search
Search human gene records by symbol, name, or synonym
GET
/api/ncbi_genes/v3/search
Search human gene records by symbol, name, or synonym
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The NCBI Genes API requires no credentials, so there is nothing to vault. Jentic still routes the request through the standard execution flow so logging, retries, and observability match other tools.
Intent-based discovery
Agents search by intent (for example find gene by name) and Jentic returns GET /api/ncbi_genes/v3/search with its query parameter schema, so the agent can call it correctly even though there are no official docs published.
Time to first call
Direct integration: under 30 minutes to discover the right endpoint and parameter (terms). Through Jentic: under 5 minutes since the schema is pre-validated and discoverable by intent.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NIH Clinical Table Search Service - NCBI Genes API through Jentic.
Why is there no official OpenAPI spec for NIH Clinical Table Search Service - NCBI Genes API?
The NIH Clinical Table Search Service does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NIH Clinical Table Search Service - NCBI Genes API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the NCBI Genes API require?
None. This is a public, unauthenticated API provided by the US National Library of Medicine. You can call GET /api/ncbi_genes/v3/search directly from a browser or any HTTP client without an API key. Through Jentic the request is still routed through the standard execution flow so observability and retries are uniform.
Can I search gene synonyms with this API?
Yes. The /api/ncbi_genes/v3/search endpoint matches against official symbols, full names, and synonyms in NCBI's gene_info dataset. A query for HER2 returns the canonical ERBB2 record, for example.
What are the rate limits for the NCBI Genes API?
The OpenAPI spec does not publish numeric rate limits. NLM operates this as a public service, so behave responsibly: cache responses, add a small delay between bulk lookups, and back off on transient errors rather than retrying immediately.
How do I look up a gene through Jentic?
Run pip install jentic, search Jentic for find gene by name, load the schema for GET /api/ncbi_genes/v3/search, and execute with the gene symbol or partial name. No credentials are needed because the API is public. Get started at https://app.jentic.com/sign-up.
Does this API include non-human genes?
No. The dataset is restricted to human genes from NCBI's gene_info.gz. For other organisms or non-gene clinical reference data, NLM offers separate Clinical Table Search Service endpoints that are not covered by this OpenAPI spec.
GET STARTED