CORESign up

Glossary

The words CORE actually uses, sourced from the product itself - the API, a deal's own status page, the exchange rules. Each entry is something you can run into while using CORE, not a general crypto definition.

AML / KYT screening
Source-of-funds and sanctions checks on a deposit, run by the executor under its own rules - CORE does not run a second one of its own.
Asset and network
An asset is always a code plus a network, never a bare code, because USDT on TRON and USDT on Ethereum are different coins. Every quote, deal and address check in CORE carries both fields together.
comparedExecutors
How many executors answered a quote request. A count on the partner API response, so an integrator can say several were compared without being handed the list of who they were. The names are switched on per key for a partner that shows the comparison to its own users.
coreTrackRecord
CORE's own measured history with one executor: legs run, how many completed, how many failed or refunded, and the average time to finish. It reads null for an executor without a run yet, distinguishing an absent history from a bad one.
Deal
An accepted quote once it is being executed - CORE's own word for what other services call a swap or an order. It moves through six statuses from creation to a terminal outcome.
Deal status
Six words describe where a deal stands: DRAFT and ACTIVE are still moving; COMPLETED, FAILED, REFUNDED and EXPIRED are terminal and never change again. Each one's exact meaning is in the API reference and on the deal's own track page.
Deposit deadline
The time by which a deposit must arrive at the order an executor created. It starts only once the order exists, and is a different clock from the quote's own expiry.
Exchange confirmation
A downloadable record of one completed deal - its number, status, both amounts, both transaction hashes and the executor. It comes from the track link, with no separate request needed.
Executor
The company that actually performs a swap - holds the deposit, executes the exchange, sends the payout. CORE compares several executors and creates the order with the one it recommends, but the deposit goes to the executor's own address, not CORE's.
Floating rate
The amount shown before a deposit is an estimate; the exchange finalizes it once the deposit arrives. Every active executor today is float-only, so a quote never states a rate CORE can guarantee in advance.
Idempotency-Key
A header required on every deal-creation call. A retry that reuses the same key returns the original deal instead of creating a second one, which is what keeps a timed-out request from becoming a second charge to the client.
Memo (tag)
The extra identifier some networks need alongside an address to credit the right account - required for assets like XRP, XLM and TON, and checked before an order is created, because a missing one there means an unrecoverable payout.
Partner reference
A public token in a partner's link or embed whose only power is to assign credit for an exchange, unlike an API key, which can act on an account. A referral is remembered for 30 days, and the most recent click is the one that counts.
Payout address
Where the client receives the coins on the receiving side of a swap. CORE checks it against the receiving network before any order is created, so a mismatch is caught before a deposit, not after.
Provider Passport
What CORE actually knows about an executor, attached to a quote wherever that executor is named: who holds the deposit, which rate modes it supports, whether a refund address is fixed at creation, its terms version and URL, which networks need a memo, and CORE's own measured history running deals through it. A fact CORE cannot back up is left null, not guessed.
Quote expiry
How long a quote can still be accepted, set on the quote itself. It has nothing to do with the deposit deadline that appears after a deal is created - they are two different clocks.
Rate limit
60 requests per minute per API key, enforced independently for each key on an account. If the limiter itself fails, the default is to refuse requests, not allow them through.
Refund address
Where a deposit goes back if the swap cannot complete. Giving one at creation keeps the return inside CORE's own flow; without one, the executor decides how the coins come back.
REVIEW
The answer to a deal-creation call when the outcome at the executor is unknown. The response carries no deposit address, so the safe action is to wait: an operator checks with the executor and resolves it before anything is sent.

API documentation · Service rules