I will keep on working, crash or not, because I like what I do.
60 karma · joined December 7, 2018
For quants and coders, we provide a free JSON API with 1 minute updates on http://cryptomarketplot.com/api.json The syntax is compatible with the now discontinued CoinMarketCap JSON API. But it's better, as we also have useful extra fields: Bid, Ask, and Last price. And it's fully free, No key or login required.
We keep rolling new features. Ask, and we will see what we can do!
I will keep on working, crash or not, because I like what I do.
But you would be surprised to know how many samples we have at any moment!
But after talking, I'm curious to see what kind of market data they have. I asked for a small sample.
I am still waiting for reply from electic.
But by the same login, I agree with you: .9eX and 9.0eY with |X - Y| = 1 may cause too much focus on what is a small difference.
Some hard choices were made. It is not perfect.
Personally, I would challenge the piggybacker to show me something.
Talk is cheap.
For your embedded devices, we can make something special just for you
Please get in touch by email if you need something special.
If you have hard constraints, we can provide you with a special API returning only the value(s) you need so you do not even have to parse anything.
And if you make embedded devices using our API, maybe you need more than the free API?
We sell access based on subscription for 0.1 BCH per month.
Or maybe you need our 'special services'?
From the FAQ: "I'm wealthy. I have very specific crazy needs!"
"For the right price, the above rules may not apply to you. Right price means at least 1 BTC. If you can pay that, we can do many crazy things just for you"
Ok, we'll fix that.
The fact is the price range vary too much, even in the same scale (say BTC/USD vs XRP/USD), so we decided to have 5 characters for every price.
That requires the use of scientific notation.
Most sites hide they API behind a login and require a key and signing a TOS. That's not public. Our public API is totally public.
I'll be happy to get in touch, because we are starting with the same goals as you: low latency, and stats.
To see what you have achieved there, can I get a sample of your raw data? Like the first 2 days of december, showing at least the bid/ask/last per exchange, per pair. More if you have more.
It should be stale enough and a small enough window to not cause problem extracting or be of much value. Any format you want is fine. You email me a link to the dump and I'll have a look.
I must say I'm very curious now.
Let's take an example: illiquid coins, like for new forks.
Look at the prices quoted on every exchange: you will often see huge differences. Because on some exchange, you can only buy the new coins - not sell them. So the price is high. On the exchanges where you can buy and sell, the price is low.
We think that's scammy. We don't want to list these coins or that information.
We are working on ways to do that, but extending over the top 50 is not very high in the priority list. There are even coins from the top 100 we are not comfortable showing in the API. We just hope they won't ever make it to the top 50 on our frontpage :-)
But that's a bit different from what we are doing.
We concentrate on hard numbers and privacy. You seem to focus on news and community. And it seems to me your API requires a login. Also, your homepage looks nice, but I don't find on it the information I want - cold hard number, graphs! However, I find plenty of stuff I do not want - like twits?? I don't want twitter or anyone else to track me.
Your site looks nice, but I think we have very different goals.
I don't want registration or even cookies.
Keeping it in all caps (like when it was just an acronym) puts it forward.
We want to emphasize our support of privacy.
I am not sure on how to get https:// by default while still supporting http:// for people who prefer it. It may take some advanced 302 redirect.
We will investigate and see what we can do there. Suggestions are much appreciated.
Check http://cryptomarketplot.com/accessible-index.html : the numbers are also aligned, and in less space that it would take if 5.744e-5 was to have all its leading zeroes.
I really appreciate. We will work on having the percentage change online for you in the API as soon as possible.
We are prioritizing in new features people who want to do a CMC like web display but are not comfortable with coding.
We want non programmers to get our data without depending on the JSON or other complex stuff. Something light and simple.
Can you summarize their features? What data do they show?
We offer real-time data to clients. Real time is hard to beat.
I hope we grow and replace coinmarketcap. But that will take hard work, and lots of luck.
We have algorithms to spot anomalies. We want to offer extremely reliable data.
We will show more coins when we think we can show non misleading data. It's a question of trust. We want happy visitors and happy clients. We want to earn their trust.
Thanks for a lot for using our data on coinzaa! We would appreciate a link, but only if you feel like it.
I can't
We could make an option for people who prefer regular numbers. I will add that to the feature requests.
"percent_change_1h": "XXX",
"percent_change_24h": "XX",
"percent_change_7d": "XX",
We can add that, but we want to use fixed points in times, to avoid floating periods comparison.Here is an example for the change in 1h: it is 10:45 AM, so do the average for 10AM, do the average for 9AM, see the percentage change.
A bad method is to average from 10:45AM to 9:45AM, average from 9:45AM to 8:45AM then report the percentage change, because if there was a big change at 9:30, and just one, then the coin is stable, it will have decaying effect on the percentage change. You will see it moving, while the coin has stabilized! To me, that's wrong.
Coinmarketcap was doing the latter. We can support that, but you should consider switching.
What exactly does 1.23e-4 means? Why do you use the computer form of scientific notation?
We use scientific notation to remove the leadings zeroes. What is simpler to read quickly, 0.000123 or 1.23e-4? If you trade crypto, you usually already know by heart how many zeroes are in front, and what is the approximate price range - you only care about the changes of the non zeroes. If the price goes from 0.000123 to 0.000142 we can save a lot of space on the screen by just writing 1.23e-4 and 1.42e-4. This way, the changes jump out and you read more numbers faster.
(...)
We use the computer form of scientific notation. 1.23e-4 instead of 1.23*10^-4, because this saves a lot of space of the screen. Scientific papers and traditional researchers may frown upon this "degenerate notation." But we absolutely love this concise and elegal notation! It may be a good thing we are in business, and not in the ivory tower of academia! We get more freedom to write numbers how we damn like!!
I like the idea of tracking a portfolio without logging. We must think more on how do to it without accidentally tracking users. A bookmark would be nice.
Quite literally: I posted before bed, then edited my post to say we are sorry about the PDF when I realized a new feature added last week seem to have killed the automatic PDF making. Oops moment, but I felt bad about deleting the post. And I was afraid I would see no response when I wake up.
Then had nightmare about broken features, and now I wake up and we are on the first page!! So it's a true nightmare :-)
Much honored to be talking with the CoinGecko founder, and that you like what we did!
On the FAQ, we tried to explain in more details why we did things differently. We want to focus on other things that seem neglected by other sites. Cryptomarketplot was made because there was nothing much like what we wanted.
For example, the website should to work when used with anything, and it should be very fast even if you do not have a fast internet connection. And we want to see the graphs, and the numbers, with minimal clutter. So we made the product that we wanted.
Some of the wants are technical: try to open the website with links in a Linux terminal, it still works. Try to read it on 3G, it is still fast. 1996 is very proud!
Some wants are harder to explain: we do not want people to get scammed. We do not like marketcap because it's an easy way to fool people. But it can turned into a tool to warn people that a coin which jumped from spot #1000 to say #19 in about 3 days may be suspicious!
Many of our wants are philosophical like that. We want to find clients to be profitable, but also we do not want ads or tracking visitors, now or ever. We do not want to restrict freedom of anyone, so no API key, no license. You buy the data, it's yours.
And we accept donations to people who share that spirit.
It was made to quickly answer many questions that could only be done with the tables of numbers from accessible version.
Say something happened. You want to know how many hours ago was there a big move? How is it holding after that? How does it compares to yesterday? To the week before? To the month before?
To do that, even if we have data, the resolution must lowered. Because you want to a quick eyeballing, and if the bucket size vary too much, it is much harder.
Take XRP for example, go http://cryptomarketplot.com/timeline/ripple.pdf
[actually, I must have crashed the PDF part last week, so the numbers are from Dec 2. Sorry. Let's imagine it is today. We are working on it right now]
You see that the peak was 6 days ago, it had a large jump compared to the other DAYS. And the left, you see that on the last 4 months XRP/BTC has kept growing.
If you just look at the graph very quickly, you see a patter. The shape.
You can visually correlate the pattern to the other coins, and see if they all responded in the same way or not to a market event.
We would like to offer historical API to paying customers. We have a lot of data.
But we want to retain customers. We do not want them to leave after dumping our data. At keep keep paying us :-)
So we came to the conclusion: you get data from when you start to pay us, and we add a little extra (last 2 months) but no more. It is in the FAQ.
Historical API, we must think more about that.