Maker (MKR)

Maker’s protocol is called MakerDAO, which stands for Maker Decentralized Autonomous Organization. Maker’s token MKR, is the governance token used to stabilize their stablecoin, DAI and keep it pegged to the dollar. Through this dual crypto approach, Maker reduces uncertainty and volatility.

Asset type Token
Name Maker
Symbol MKR
Standard ERC-20
Supported Protocols Ethereum
Manage your Maker assets

MKR details

MKR tokens are minted or burned depending on price fluctuations. They also allow their holders to participate directly in the process of governing DAI. Each person who holds Maker tokens can vote on a number of changes that can be made to the Maker Protocol. Their voting power depends on the size of their MKR stake.

Reading Maker with Crypto APIs

Maker is issued on ERC-20 and settles on Ethereum. Crypto APIs reads it the same way it reads every other token on those networks — one REST call for balances, transfers and contract metadata, with no node to run and no separate integration per chain.

Token transfers

List full Maker token transfer history for any token contract or address, with pagination and real-time updates.

Token balances

Read current Maker token holdings for any address in a single call.

Contract metadata

Get token contract details — symbol, name, decimals, and total supply — for any supported token.

Frequently Asked Questions

Which blockchain does Maker run on?

Maker settles on Ethereum. Reading its balances and transfers means calling the ERC-20 contract rather than the address endpoint you would use for the chain's native coin.

What kind of token is Maker?

It is a token on the ERC-20 standard.

Can I test Maker without spending real funds?

Yes — the same endpoints serve Ethereum's Sepolia testnet, so you can build and verify an integration end to end before you touch mainnet.

How do I read Maker balances and transfers?

Use Address Latest for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, Address History requires the address to be synced first, which then bills per address per day for as long as it stays synced.

What does reading Maker data cost?

It depends on the endpoint family rather than on Maker itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The pricing calculator has the current per-chain figures.