# Elementus

> Blockchain intelligence company (New York, founded 2017) that attributes on-chain
> addresses to real-world entities across multiple chains and sells that attribution
> graph to compliance, investigations and market-intelligence teams. Its one public
> API is the Attribution API: send a batch of blockchain addresses, get back the
> beneficial owner, custodian, entity name and OFAC/SDN sanction status for each.

IMPORTANT — READ BEFORE USING ANY LINK BELOW. As of 2026-08-12 no Elementus web host
resolves. elementus.io publishes no address record at the apex, www.elementus.io is
NXDOMAIN, and both attribution-api.elementus.io and app.elementus.io are dangling
CNAMEs pointing at AWS resources that no longer exist. The DNS zone itself is alive
and still routes mail to Google Workspace, so the company has not released the domain,
but every developer-facing surface is currently unreachable. Do not attempt to
integrate against the endpoints below without first confirming the host is back.

This file was generated by API Evangelist from Elementus' own public GitHub
organization — the only first-party surface still reachable — not fetched from
Elementus. Elementus publishes no llms.txt.

## API

- [Elementus Attribution API](https://attribution-api.elementus.io): Base URL. Does
  not resolve as of 2026-08-12.
- [API definition (Swagger UI)](https://attribution-api.elementus.io/swagger-ui): The
  location Elementus' own example repository names as the API definition. Unreachable;
  no OpenAPI document has ever been captured from it, and none is archived.
- Authentication: API key in an `X-API-Key` request header. No OAuth2, no OIDC, no
  mTLS, no scopes.
- `POST /address-attributions` — resolve a batch of addresses. Request body carries an
  `addresses` array (minimum 1). Response is an object with a `data` map keyed by
  address; each value carries `beneficial_owner`, `custodian`, `entity`,
  `is_ofac_sanctioned` (0 = not sanctioned, 1 = sanctioned), `sdn_name`, `wallet_id`.
- `GET /health` — liveness check.
- Errors: any HTTP status >= 400, with a JSON body carrying a `message` field. Not
  RFC 9457. No error code registry is published.
- Rate limits: none published. No RateLimit-*, X-RateLimit-* or Retry-After headers
  are evidenced.
- Idempotency: none published.
- Pagination: none — batch in, batch out.
- Versioning: none. The base URL carries no version segment.

## First-party source

- [GitHub organization](https://github.com/elementus-io): Live. Six public
  repositories.
- [api-example](https://github.com/elementus-io/api-example): Elementus' own Attribution
  API example client, Python, last pushed 2025-03-05. The authoritative public
  description of the contract above.

## Not published

Elementus publishes none of the following, on any reachable surface: OpenAPI or any
other machine-readable specification, AsyncAPI or a webhook catalog, an MCP server, an
A2A agent card, a `/.well-known/` document of any kind, a security.txt, a trust center,
a status page, a changelog, a deprecation or versioning policy, a CLI, an SDK on any
public package registry, a sandbox, or a pricing page. Access was a
contact-sales/demo motion.

## Profile

- [API Evangelist profile](https://apis.io/provider/elementus): Independent third-party
  profile. Not operated by Elementus.