Assets and markets

Assetera's catalog has three levels: issuer, asset, and market. This keeps the legal instrument separate from the network and sale configuration used to distribute it.

Catalog model

• Issuer identifies the organization behind one or more instruments.
• Asset is the logical instrument and carries its descriptive, classification, document, and issuer relationship.
• Market is the customer-facing way that asset is offered. It carries the relevant network, token, settlement currency, lifecycle, sale mode, terms, and tenant entitlement.

One asset can have more than one market. Partners integrate against market IDs for trading and primary-sale actions, while customer pages can group markets under their parent asset.

Network identity

Network and token identifiers are part of the market contract. EVM markets use the chain and contract details returned by the API. Do not assume one network, copy an address from another environment, or assume all tokens use 18 decimals.

Assetera keeps settlement on the market's configured network. A market request is not an instruction to bridge assets between networks.

Lifecycle

Assets and markets use the same catalog lifecycle vocabulary:

Visibility also depends on tenant entitlement and any current market window or restriction. A partner must not infer availability from status alone. Use the customer-facing API response and handle write refusals.

Tenant entitlement

The catalog is canonical, but distribution is tenant-specific. An Assetera administrator assigns markets to partner tenants. GET /markets returns only the caller's visible slice; a caller cannot select another tenant with a header or query parameter.

For exact field names and response schemas, use the Marketplace OpenAPI contract.