Generated banner for Ncats Arax
Generated logo for Ncats Arax

Ncats Arax

K-DenseCommunityCreated by neuroepithelialDistributed by K-Dense

  • Skill
  • Tool integration
  • Science and research
  • MIT
  • Low risk
  • Has scripts

From the author

Queries the NCATS Translator ARAX production API for bounded, typed, provenance-rich one-hop and endpoint-pinned two-hop biomedical knowledge-graph relationships. Use for Biolink-constrained RTX-KG2 lookup, explicit selected-provider ARAX federation, separate entity normalization, qualifier-aware graph traversal, and inspection of TRAPI edge bindings, publications, and knowledge-source provenance. Do not use for inference, ranking, open-ended pathfinding, clinical guidance, or sensitive queries.
— the description by neuroepithelial

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The ncats-arax skill provides a command-line interface to interact with the NCATS Translator ARAX production API. It enables researchers to perform bounded, typed knowledge-graph lookups, including one-hop queries and endpoint-pinned two-hop traversals. The tool emphasizes transparency by preserving TRAPI exchange data, providing provenance for edge bindings, and requiring explicit acknowledgment that queries and metadata may be publicly visible. It is designed for structured, constrained biomedical graph exploration rather than open-ended inference or clinical decision support.

What it does

  • Performs entity normalization to retrieve canonical identifiers and categories.
  • Executes typed one-hop knowledge-graph lookups with optional qualifier constraints.
  • Supports endpoint-pinned two-hop queries with configurable expansion order.
  • Enables federated queries across two to five specified knowledge providers.
  • Generates structured artifacts including request, response, and summary files.
  • Provides an inspection utility to rebuild bounded summaries from saved TRAPI responses.

When to use it

  • When you need to retrieve specific, typed biomedical relationships between known entities.
  • When you require provenance and source-record details for graph edges.
  • When you need to verify entity identifiers before performing graph traversals.
  • When you are conducting research that requires explicit control over knowledge providers.
  • When you need to inspect the raw TRAPI payload for a specific query.

Advantages

  • Provides clear, bounded query shapes to ensure predictable API interactions.
  • Maintains strict provenance by linking results to primary and upstream sources.
  • Supports qualified queries to refine relationship aspects and directions.
  • Ensures reproducibility by saving exact request and response bytes.
  • Operates without requiring API keys or complex authentication.

Usage examples

“Normalize the term ivacaftor to find its canonical CURIE and category.”
The tool returns the canonical identifier, name, category, and synonym preview for ivacaftor, saved to a specified output directory.
“Find one-hop relationships between CHEBI:31690 and NCBIGene:25 using the RTX-KG2 provider.”
The tool executes a typed one-hop query and generates a summary of bound edges, provenance, and the raw TRAPI response.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/k-dense-ai/ncats-arax/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip ncats-arax.zip -d .agents/skills

Documentation by neuroepithelial

NCATS ARAX

Use ARAX as a constrained knowledge-graph lookup service. Submit reviewed CURIEs and explicit Biolink types, preserve the exact TRAPI exchange, inspect query-edge bindings and provenance, and treat every returned path as a candidate for subsequent verification.

Read query-contract.md before constructing a query. Read output-schema.md when interpreting saved artifacts, warnings, provenance, or partial results.

Safety boundary

  • Use only public, nonsensitive research questions. ARAX status facilities may expose query and caller metadata even when store=false is requested.

  • Do not submit patient information, confidential research questions, unpublished compound programs, or proprietary target hypotheses.

  • Do not present a returned path as a validated mechanism or clinical recommendation.

  • Report a zero as "not returned under these constraints," never as evidence that no relationship exists.

  • Describe position as unscored response order, never rank.

  • Verify important candidates with literature and authoritative databases separately.

Workflow

  1. Normalize free text separately, then review and report the proposed CURIE and category.

  2. Choose a typed one-hop query or an exactly two-hop query with both endpoints pinned.

  3. Use default RTX-KG2 lookup unless the user explicitly names two to five providers.

  4. Acknowledge that the biomedical query is public and choose a new or empty output directory.

  5. Run the client once. Do not silently change provider selection or expansion order after a failure or empty result.

  6. Inspect summary.json for bounded bindings and provenance and response.json for the exact TRAPI payload.

  7. Verify scientifically important paths outside ARAX.

Preflight

Check the production OpenAPI without making a biomedical query:

python skills/ncats-arax/scripts/arax_client.py preflight

The client verifies that the service identifies itself as ARAX, exposes POST /query and GET /entity, and reports a supported TRAPI version. It reads info.x-trapi.version, falling back to the title for older OpenAPI documents. A nonproduction endpoint or untested TRAPI series requires an explicit override; neither override changes the fixed query shapes or operations.

Normalize an entity

Normalization is review-only and never triggers a graph query:

python skills/ncats-arax/scripts/arax_client.py normalize "ivacaftor" \
  --expected-category biolink:SmallMolecule \
  --max-synonyms 10 \
  --acknowledge-public-query \
  --output-dir outputs/normalize-ivacaftor

Review the canonical identifier, name, category, and synonym preview before using a CURIE. Report all CURIEs and categories regardless of query outcome. A category warning or zero result is a reason to curate the identifier, not to chain automatically to /query.

One-hop lookup

Pin at least one endpoint and type both nodes:

python skills/ncats-arax/scripts/arax_client.py one-hop \
  --subject-id CHEBI:31690 \
  --subject-category biolink:SmallMolecule \
  --predicate biolink:affects \
  --object-id NCBIGene:25 \
  --object-category biolink:Gene \
  --qualifier biolink:object_aspect_qualifier=activity_or_abundance \
  --qualifier biolink:object_direction_qualifier=decreased \
  --acknowledge-public-query \
  --output-dir outputs/imatinib-abl1

Lookup mode is the default and fixes expansion to infores:rtx-kg2. It defaults to 20 results. Use --result-limit N to request 1-50 results; 50 is the hard cap in either mode.

Endpoint-pinned two-hop lookup

Use exactly one typed, unpinned intermediate node:

python skills/ncats-arax/scripts/arax_client.py two-hop \
  --subject-id CHEBI:66901 \
  --subject-category biolink:SmallMolecule \
  --predicate-1 biolink:affects \
  --intermediate-category biolink:Gene \
  --predicate-2 biolink:associated_with \
  --object-id MONDO:0009061 \
  --object-category biolink:Disease \
  --qualifier-1 biolink:object_aspect_qualifier=activity_or_abundance \
  --qualifier-1 biolink:object_direction_qualifier=increased \
  --expand-order right-first \
  --acknowledge-public-query \
  --output-dir outputs/ivacaftor-cystic-fibrosis

Right-first expansion is the default. If an empty result merits another attempt, run a new query explicitly with --expand-order left-first and keep the runs separate.

Selected-provider federation

Federation is explicit and accepts two to five named providers:

python skills/ncats-arax/scripts/arax_client.py one-hop \
  --subject-id CHEBI:31690 \
  --subject-category biolink:SmallMolecule \
  --predicate biolink:affects \
  --object-id NCBIGene:25 \
  --object-category biolink:Gene \
  --mode federated \
  --kp infores:rtx-kg2 \
  --kp infores:molepro \
  --acknowledge-public-query \
  --output-dir outputs/federated-imatinib-abl1

Federation defaults to the hard maximum of 50 results. Provider errors may coexist with useful results; such a run exits 7 after retaining its artifacts and is marked partial. The same applies to a failed provider in lookup mode. An explicit non-success ARAX response status exits 6 with the raw response retained; it must not be reported as a successful zero-result query.

Inspect saved provenance

Rebuild a bounded summary without network access:

python skills/ncats-arax/scripts/arax_client.py summarize \
  --request outputs/ivacaftor-cystic-fibrosis/request.json \
  --response outputs/ivacaftor-cystic-fibrosis/response.json \
  --format text

The inspector accepts only the same constrained request shapes and fixed operations that the live commands generate. Use --format json for the normalized view on standard output.

Interpret results

  • Follow each analysis's query-edge bindings; do not summarize every knowledge-graph edge.

  • Preserve the physical edge subject, predicate, object, and qualifier values returned by ARAX. Returned predicates or qualifier aspects may be more specific than the query constraint.

  • Inspect all source objects, including primary, aggregator, supporting-data, upstream-resource, and source-record URL fields.

  • Trace aggregator edges to their primary/upstream sources and publications before claiming corroboration. Multiple providers can redistribute the same record; report distinct primary evidence, not provider count as confidence or independent replication.

  • Treat publication_availability: not_returned as missing metadata, not evidence that no publications exist.

  • Treat missing auxiliary-graph references and provider failures as explicit warnings.

  • Consult the raw response whenever the bounded summary omits detail or the service response is partial, unfamiliar, or scientifically surprising.

Deliberate exclusions

The client has no raw-query, workflow, operation, overlay, ranking, inference, link-prediction, Pathfinder, ARS, batch, all-provider, three-hop, cache, daemon, SDK, MCP, or natural-language-to-TRAPI surface. Do not work around those limits with direct HTTP calls under this skill.

Official references

Reviewed on 2026-09-30 against production ARAX 1.5.4 / TRAPI 1.5.0 (the URL still contains v1.4). Live public smoke tests passed for preflight, normalization, qualified one-hop and endpoint-pinned two-hop lookups, and RTX-KG2/MolePro federation. Results and provider availability can change. The official introductory guide contains older response examples; use the deployed schema and current ARAX source for field and operation contracts. No Python SDK is used by this client.

Files

references/query-contract.md

ARAX query contract

Contents

  • Service boundary

  • Supported query shapes

  • Validation

  • Fixed operations

  • Limits and retries

  • Version and endpoint policy

  • Excluded escape hatches

Service boundary

Use https://arax.transltr.io/api/arax/v1.4 by default. A networked command first retrieves /openapi.json, verifies an ARAX title, POST /query, and GET /entity, and records the advertised ARAX and TRAPI versions. Normalization uses /entity; graph lookup uses /query.

EndpointRequest and response contract
GET /openapi.jsonOpenAPI object; ARAX version is info.version, TRAPI version is info.x-trapi.version (title fallback). No biomedical term is submitted.
GET /entity?q=<term>URL-encoded q; the API permits repeated q but this client submits one. Response is keyed by input term, with id.identifier, id.name, id.category, categories, nodes, and total_synonyms. Unknown terms may have no usable record.
POST /queryJSON message.query_graph, ARAX-specific operations.actions, stream_progress: false, and submitter. Response is a TRAPI envelope with message, optional status, description, logs, and version fields.

Entity synonym entries use label for their display name; the client also accepts older name entries. The canonical display name remains id.name. This is ARAX's entity response contract, not the SRI Node Normalizer's direct response schema.

These routes require no API key in the deployed OpenAPI. The fixed result limit is an ARAXi filter, not pagination: the client does not follow pages or promise a complete enumeration of all matching graph paths. The API's broader pagination and asynchronous fields are not used.

Every normalization or graph request requires --acknowledge-public-query. This is an explicit acknowledgment that query and caller metadata may be visible through service facilities. The store=false operation reduces intentional response storage but is not a privacy guarantee.

Supported query shapes

One hop

Use two qnodes (n0, n1) and one qedge (e0). Require one category on each qnode, one to five predicates, and at least one pinned endpoint. Each qnode has at most one CURIE. Omit ids from an unpinned qnode.

Two hops

Use three qnodes (n0, n1, n2) and two qedges (e0, e1). Pin n0 and n2 with exactly one CURIE each. Type every qnode. Keep n1 unpinned. Each edge has one to five predicates.

For either shape, an edge may have zero to six qualifiers. Combine them in one qualifier_constraints entry containing one AND-conjoined qualifier_set. Omit the whole field when no qualifier is supplied. Do not repeat a qualifier type on the same edge.

Validation

CURIEs follow this conservative form:

^[A-Za-z][A-Za-z0-9._-]*:[^\s]+$

They must be no more than 200 characters and contain no controls, NUL, tabs, or newlines.

Categories, predicates, and qualifier types follow:

^biolink:[A-Za-z][A-Za-z0-9._-]*$

Provider identifiers are interpolated into an ARAXi action and therefore use the stricter form:

^infores:[A-Za-z0-9._-]+$

Do not maintain a local Biolink model or provider registry. Shape validation is local; ARAX remains the semantic authority. Reject duplicate predicates, qualifier types, provider IDs, and repeated scalar endpoint options.

Fixed operations

Lookup mode fixes the provider to infores:rtx-kg2. Federated mode requires two to five explicit, distinct provider identifiers and emits them in one list-valued kp= argument. Never omit kp and never generate duplicate kp= arguments.

One hop expands e0. Two-hop right-first expands e1 and then e0; left-first reverses only those two actions. Append exactly:

scoreless_resultify(ignore_edge_direction=true)
filter_results(action=limit_number_of_results,max_results=<1-50>,prune_kg=true)
return(response=true,store=false)

Each expansion fixes:

kp_timeout=30,return_minimal_metadata=false

Always send stream_progress: false and the constant submitter scientific-agent-skills-ncats-arax. Never put a user name, project name, or query term into the submitter or User-Agent.

Limits and retries

ControlValue
OpenAPI/entity HTTP timeout30 seconds
Lookup query HTTP timeout120 seconds
Federated query HTTP timeout180 seconds
ARAX KP timeout30 seconds
Lookup default result limit20
Federated default result limit50
Hard result limit50
Provider count2-5 in federation
Predicates per edge1-5
Qualifiers per edge0-6
Raw response limit25 MiB (26,214,400 bytes)

Retry OpenAPI and entity GET requests once after HTTP 429, 502, 503, 504, or a transport timeout. Honor Retry-After for at most 10 seconds; otherwise wait one second. Never retry POST /query. A failed POST may have been processed and must be rerun only by an explicit user decision.

The client requires strict JSON. On 2026-09-30, /entity?q=primary+myelofibrosis returned NaN inside auxiliary knowledge-graph attributes and was correctly retained as a malformed response (exit 6). The worked example uses a successfully tested entity. If this happens for another term, inspect the raw artifact and curate the CURIE independently; do not treat it as no match.

Use these headers:

Accept: application/json
Accept-Encoding: identity
Content-Type: application/json        # POST only
User-Agent: scientific-agent-skills-ncats-arax/1.1

Version and endpoint policy

Production OpenAPI and all eight live smoke tests were verified on 2026-09-30 against ARAX 1.5.4 with TRAPI 1.5.0. The /v1.4 URL component is not the advertised TRAPI version. Parse the common response fields for TRAPI 1.5 and 1.6, warning whenever the version is not the tested value. Refuse an unknown or missing TRAPI series unless --allow-untested-version is explicit. Record biolink_version from each query response rather than assuming it.

Accept only HTTPS base URLs without credentials, query strings, or fragments. Reject localhost and literal private, loopback, link-local, or reserved addresses. A URL other than the production base requires --allow-nonproduction-endpoint, must still identify ARAX through OpenAPI, and receives a warning. Reject cross-origin and protocol-downgrade redirects. Never fall back automatically to arax.ncats.io or another ARA.

The operations were checked against the deployed OpenAPI, ARAX query execution, expander, and result filter. scoreless_resultify is supported by the query dispatcher even though the DSL guide documents resultify more prominently; resultify additionally triggers ranking and is not interchangeable. Provider availability is chosen from ARAX's current registry by version and maturity; the MolePro example is a tested selection, not a permanently available provider list.

Excluded escape hatches

Expose no raw JSON submission, query-file, generic node/edge list, workflow, operations, action, overlay, ranking, inference, creative-query, link-prediction, Pathfinder, ARS, all-provider, batching, stdin-list, cache, database, daemon, server, SDK, MCP, or third-hop option.

The offline summarizer validates the saved request against this same topology and operation contract. It refuses unsupported requests rather than becoming a back door for broader ARAX use.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Needs Python, Needs Node.js

The author says: Requires Python 3.10+ and outbound HTTPS access to arax.transltr.io. The client uses only the Python standard library and needs no API key. Queries and caller metadata may be publicly visible; never submit sensitive or patient-specific content.

Security

What our scanner noticed· Low risk

  • Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
neuroepithelial
Publisher
K-Dense (Community)
Distributed by
K-Dense
Source
K-Dense-AI/scientific-agent-skills · skills/ncats-arax · commit a25cf9e
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE.md)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by neuroepithelial or K-Dense.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ncats-arax.zip