Add Sharpe API#25
Open
rishabhng wants to merge 1 commit into
Open
Conversation
Author
|
Following up on this API listing. I kept the change to a single README.rst entry and positioned Sharpe as a crypto market data API, which matches the surrounding data-provider format. The public docs cover market intelligence endpoints across derivatives, arbitrage, funding, and signals, with a free API surface available for discovery. Happy to adjust the description or category if you prefer a narrower cryptocurrency data-provider wording. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Sharpe to the Cryptocurrency general data section.
Sharpe provides REST and OpenAPI access to crypto market data including funding rates, futures, options, arbitrage, narratives, news, and exchange-listings data.
The entry uses the existing README.rst link style and points directly to the API reference page so readers can inspect the available endpoints.