> For the complete documentation index, see [llms.txt](https://docs.neglect.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neglect.trade/products/data-services.md).

# Data Services

The fastest way to build with Solana DeFi data.

Our **REST API** offers programmatic access to token-level insights across the Solana ecosystem. It powers products, bots, dashboards, and analytics tools with **real-time and historical data** across multiple dimensions.

Base URL: 

<pre><code><strong>https://api.neglect.trade
</strong></code></pre>

Developers can:

* Query token metadata (name, symbol, supply, creation time, social links, etc.)
* Track new listings, graduations, and bonding events
* Integrate directly with our token discovery and trading pipelines
* Access consistent, reliable JSON responses designed for builders
* …and much more

We also offer a [MCP (Model Context Protocol)](https://modelcontextprotocol.io/docs/getting-started/intro) server for enhanced agentic integrations. This allows AI systems and autonomous agents to query the same Solana data endpoints in real time, enabling composable workflows and in-context reasoning across Solana DeFi data.

Whether you're building automated strategies, dashboards, indexing layers, or entirely new products, our endpoints provide the foundation to move fast without parsing raw chain data.

<a href="https://neglect.trade/developers" class="button secondary">Check out our API plans & learn more</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neglect.trade/products/data-services.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.