I guess I'm just not the target, but anyway... I think the website could communicate whatever it is you are doing better.
What pain point does your API solve? Who is your target audience? Can you show us a simple example (or a few)?
Is it closed-source? How are you planning to monetize it? This is a very important issue for any api-as-a-service project which yours seems to be. If you don't have any strategy, then I will not bet my business on you sticking around...
It basically wraps some functionalities of quantlib library into an API. Main reason of it is that I think part of the target of the library is people that not need to know about programming, and an API opens it to future user friendly interfaces (such as the google sheets addon).
Examples, the add-on uses it and you can find the source code in the repository. Close source, yes now, it's been just a side project. Not thinking about monetize it now.
What pain point does your API solve? Who is your target audience? Can you show us a simple example (or a few)?
Is it closed-source? How are you planning to monetize it? This is a very important issue for any api-as-a-service project which yours seems to be. If you don't have any strategy, then I will not bet my business on you sticking around...