---
title: e
url: https://nexyron.tech/docs/cypher/functions/numeric/e
description: Returns Euler’s number for formulas that need the natural exponential base. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways p
---

# e

## Generic Description

Returns Euler’s number for formulas that need the natural-exponential base. It is documented separately because numeric transforms change ranking, thresholds, and buckets in ways planner tools must not guess.

Simple example:

```cypher
RETURN e() AS value
```

## Consumer-Level Explanation

Use it when spelling the constant is clearer than embedding a magic literal. Prefer this function when the transformation is a deliberate part of the model or report, and name the derived value in a `WITH` stage when it will be reused.

## More Detailed Explanation

`e` is scalar math, so it is evaluated per row after graph patterns, procedure output, or map projections have produced values. Keep it close to the query when thresholds, ranking, and derived fields need to be auditable and reproducible.

## Advanced Example

This example applies `e` to a named score component after matching graph data, making the derived metric reviewable before ordering.

```cypher
MATCH (d:Document)
WITH d, properties(d).prize / 10.0 AS small_priority_signal
RETURN d.title AS document,
       pow(e(), small_priority_signal) AS amplified_priority
ORDER BY amplified_priority DESC
```

## Real Use Cases

-   distance-from-target scoring
-   numeric bucketing and normalization before `ORDER BY` or aggregation
-   making scoring formulas visible to query review and assistant tooling

## Real Limitations And Tradeoffs

-   invalid numeric inputs produce null-like results rather than a repaired value
-   math functions do not fix poor feature scaling; choose transformations intentionally
-   nondeterministic functions such as random sampling are not appropriate for persisted decisions