How Assetera works

The platform at a glance: standards-based identity, one multi-tenant Marketplace API, on-chain settlement, and a compliance layer Assetera runs in every partnership model.

Assetera is an identity-first, API-first platform. You don't need to know its internals to build on it, just four moving parts and how they fit together.

The four parts

Assetera Identity

One identity layer, standards-based OIDC. Tokens are validated locally and carry the tenant + compliance context.

Marketplace API

One multi-tenant API. Assetera and each partner are tenants; every response is scoped to the tenant claim.

On-chain settlement

Trades settle on-chain via AsseteraECS (Execution, Clearing and Settlement): gasless for users (meta-transactions), with escrow and settlement.

Compliance

Assetera runs KYC/AML. Eligibility is enforced at the point of action, off-chain and on-chain.

How they connect

A user or partner backend authenticates with Assetera Identity and receives a signed token carrying its tenant and compliance context.
Calls go to the Marketplace API, which validates the token locally and returns a tenant-gated view: each partner sees only its own catalog, users and audit trail. (See Tenancy.)
Trades settle on-chain. Users don't pay network gas directly (actions are relayed as meta-transactions), and every action must carry a valid, single-use eligibility approval.
Assetera runs compliance end to end: off-chain identity verification plus per-action on-chain gating.

Assetera is being rebuilt onto this model; some pieces are live slices and others are in build. Where a capability isn't shipped yet, the relevant page says so.