> ## Documentation Index
> Fetch the complete documentation index at: https://artemis.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Equities

> Quarterly revenue, earnings and valuation ratios: EV multiples, earnings yield, and FCF yield for public equities

Public equities use the same request shape as everything else in the API (`symbol`, `metric`, date range) behind an `eq-` prefix. Coverage is large both wide and deep: 2,985 assets carry an `eq-` symbol, and a single company's vocabulary runs deep too. `eq-coin` alone exposes 2,366 metrics, from segment KPIs to trading volumes. The fourteen metrics below are a **comparable core** for cross-company analysis, not the coverage; call [`GET /supported-metrics/?symbol=eq-coin`](/docs/artemis-api/discovery) (swap in any `eq-` symbol) to see everything a given company actually reports.

## Metrics

| Metric | Label | Unit | Aggregation |
| - | - | - | - |
| `TOTAL_REVENUE` | Total Revenue | Currency | `LAST` |
| `NET_INCOME` | Net Income | Currency | `LAST` |
| `EBITDA` | EBITDA | Currency | `LAST` |
| `OPERATING_INCOME` | Operating Income | Currency | `LAST` |
| `FREE_CASH_FLOW` | Free Cash Flow | Currency | `LAST` |
| `BASIC_EPS` | Basic EPS | Currency | `LAST` |
| `DILUTED_EPS` | Diluted EPS | Currency | `LAST` |
| `ENTERPRISE_VALUE_DIVIDE_TOTAL_REVENUE` | EV / Revenue | Multiple | `LAST` |
| `ENTERPRISE_VALUE_DIVIDE_NET_INCOME` | EV / Earnings | Multiple | `LAST` |
| `ENTERPRISE_VALUE_DIVIDE_EBITDA` | EV / EBITDA | Multiple | `LAST` |
| `ENTERPRISE_VALUE_DIVIDE_FREE_CASH_FLOW` | EV / FCF | Multiple | `LAST` |
| `MARKET_CAP_DIVIDE_FREE_CASH_FLOW` | Price / FCF | Multiple | `LAST` |
| `EARNINGS_YIELD` | Earnings Yield | Percentage | `LAST` |
| `FCF_YIELD` | FCF Yield | Percentage | `LAST` |

`Multiple` doesn't appear on any other page in this section. An EV / Revenue of 20 means enterprise value is twenty times trailing revenue, not a percentage or a dollar figure. Every metric above is `LAST`: a call returns the most recently reported fiscal quarter's figure, not a rolling total. See [Quarter labelling](#quarter-labelling) below.

## Covered companies

Artemis covers 2,985 public companies, from mega-caps to micro-caps, each under an `eq-` prefix. The fourteen metrics above are the comparable *core*; which line items a given company reports varies with its own filings. Free cash flow is a good illustration:

| Company | Symbol | `FREE_CASH_FLOW` |
| - | - | - |
| Nvidia | `eq-nvda` | \$48.59B (period end 2026-04-26) |
| Meta | `eq-meta` | \$1.75B (period end 2026-06-30) |
| Coinbase | `eq-coin` | `"Metric not available for asset."` |
| Robinhood | `eq-hood` | `"Metric not available for asset."` |

Coinbase and Robinhood simply don't report a `FREE_CASH_FLOW` line. Robinhood's income statement has a similar substitution: it reports `ADJUSTED_EBITDA` rather than plain `EBITDA`, so `EBITDA` on `eq-hood` also comes back `"Metric not available for asset."` while `ADJUSTED_EBITDA` resolves with real numbers.

Check [`GET /supported-metrics/?symbol=eq-<ticker>`](/docs/artemis-api/discovery) per company before assuming a comparable-core name is what that company actually reports. For the full set of `eq-` assets, list [`GET /asset/`](/docs/artemis-api/discovery) and match on the symbol prefix rather than assuming this page's two examples are exhaustive.

## Example: Coinbase's Q2 2026 income statement

```bash theme={null}
curl -s "https://data-svc.artemisxyz.com/v2/data/TOTAL_REVENUE,NET_INCOME,EBITDA,OPERATING_INCOME,BASIC_EPS,DILUTED_EPS?symbols=eq-coin&startDate=2026-04-01&endDate=2026-08-01&granularity=QUARTER&APIKey=$ARTEMIS_API_KEY"
```

| Line item | Q2 2026 (period end 2026-06-30) |
| - | - |
| Total Revenue | \$1.22B |
| Net Income | -\$359.47M |
| EBITDA | -\$49.09M |
| Operating Income | -\$113.49M |
| Basic EPS | -\$1.36 |
| Diluted EPS | -\$1.36 |

Coinbase was loss-making in Q2 2026 despite \$1.22B of revenue. `FREE_CASH_FLOW` isn't in this table because it isn't in `eq-coin`'s vocabulary at all (see [Covered companies](#covered-companies) above). The loss carries through to the valuation ratios below.

## Valuation ratios: a clean case and a realistic one

```bash theme={null}
curl -s "https://data-svc.artemisxyz.com/v2/data/ENTERPRISE_VALUE_DIVIDE_TOTAL_REVENUE,ENTERPRISE_VALUE_DIVIDE_NET_INCOME,ENTERPRISE_VALUE_DIVIDE_EBITDA,ENTERPRISE_VALUE_DIVIDE_FREE_CASH_FLOW,MARKET_CAP_DIVIDE_FREE_CASH_FLOW,EARNINGS_YIELD,FCF_YIELD?symbols=eq-nvda,eq-coin&startDate=2026-08-01&endDate=2026-08-01&APIKey=$ARTEMIS_API_KEY"
```

| Ratio | Nvidia (`eq-nvda`) | Coinbase (`eq-coin`) |
| - | - | - |
| EV / Revenue | 20.042x | 5.629x |
| EV / Earnings | 30.647x | -36.628x |
| EV / EBITDA | 29.555x | 41.074x |
| EV / FCF | 41.080x | null |
| Price / FCF | 41.120x | null |
| Earnings Yield | 3.260% | -2.541% |
| FCF Yield | 2.432% | null |

Nvidia is the clean case: consistently profitable, every ratio resolves to a normal positive multiple. Coinbase is the realistic one. The Q2 2026 loss shown above sends `EV / Earnings` and `EARNINGS_YIELD` negative rather than producing an error, and the three FCF-based ratios return `null` because the `FREE_CASH_FLOW` line they divide by doesn't exist for this company. That `null` sits inside a normal data array, not the `"Metric not available for asset."` string. The ratio metric itself is supported, it just has nothing to divide. See [Core concepts](/docs/artemis-api/core-concepts) for the general distinction between an error string and a null value.

## Quarter labelling

Every metric on this page follows the company's fiscal calendar and is labelled by period **end** (Coinbase's figures above are dated `2026-06-30`, Nvidia's `2026-04-26`), and both snap to fiscal periods regardless of the `granularity` you request. Ordinary time series, including equity `PRICE`, label by period **start** instead. The two conventions look interchangeable in a mixed table and aren't. See [Core concepts](/docs/artemis-api/core-concepts#granularity) and [Crypto and equities in one call](/docs/artemis-api/recipes/equities) for the full walkthrough.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.