Skip to content
Eden Engine

CURIE Prefix Counts for a Biolink Type (Translator Node Normalizer)

rencinodenormalizer/curie-prefixes

Returns, for one Biolink semantic type such as biolink:Gene or biolink:ChemicalEntity, how many times each CURIE prefix (NCBIGene, HGNC, ENSEMBL, CHEBI and so on) appears among the equivalent identifiers of that type in the Translator Node Normalizer. Type names come from Node Normalizer Semantic Types. An unknown type returns the text Not found. Data from the Translator Node Normalizer (RENCI), served by Eden Engine; not an official RENCI product.

activeper callv1

Price

$0.0026 per call

You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $5.

Data source

Translator Node Normalizer (RENCI)

Source: Translator Consortium, RENCI Standards Reference Implementation team (infores:sri-node-normalizer). Served by Eden Engine; not an official RENCI product.

Use it

Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.

Connect once and your AI can find and run this tool, and any other it needs.

agent
// 1. search: find the tool
omnial_search({ query: "what you need" })

// 2. inspect: price and input schema
omnial_inspect({ tool: "rencinodenormalizer/curie-prefixes" })

// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "rencinodenormalizer/curie-prefixes" })

// 4. run: price the exact call first, then run it
omnial_execute({ tool: "rencinodenormalizer/curie-prefixes", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "rencinodenormalizer/curie-prefixes", input: { /* ... */ } })

// 5. settle: the call is charged when it finishes, nothing to do

Not connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.

Pricing

Every charge this tool can incur.

ChargePrice
Per call
$0.0026
Updated
Oct 21, 2026

Input and output schemas

Input schema
input_schema.json
{
  "type": "object",
  "required": [
    "semantic_type"
  ],
  "properties": {
    "semantic_type": {
      "type": "string",
      "pattern": "^biolink:[A-Za-z]+$",
      "maxLength": 100,
      "minLength": 8,
      "description": "A Biolink type from Node Normalizer Semantic Types, for example biolink:Gene or biolink:ChemicalEntity."
    }
  },
  "additionalProperties": false
}
Output schema
output_schema.json
{
  "type": "object",
  "description": "One key, the type asked for, mapped to `{curie_prefix: {PREFIX: count}}`.",
  "additionalProperties": {
    "type": "object",
    "properties": {
      "curie_prefix": {
        "type": "object",
        "description": "Prefix to count of occurrences (a numeric string). The value is the text Not found for an unknown type.",
        "additionalProperties": {
          "type": [
            "string",
            "integer"
          ]
        }
      }
    },
    "additionalProperties": true
  }
}