# MCP/NLP Market Intelligence

## Endpoint

<pre><code><strong>POST https://api.dapplooker.com/v1/mcp
</strong></code></pre>

***

## Intelligence Coverage

The MCP / NLP API can query across:

* Market Intelligence
* Token Market Data
* Technical Analysis & Indicators
* Smart Money & Whale Tracking
* Wallet Safety Scores
* Holding Patterns & Mindshare
* Staking Insights
* Genesis Token Alpha
* On-chain Intelligence
* ACP Insights
* Trade Recommendations & Alpha

***

## Request Body Parameters

| Parameter | Type   | Required | Description                                |
| --------- | ------ | -------- | ------------------------------------------ |
| api\_key  | string | No       | API key if not using x402                  |
| chain     | string | No       | Chain context, e.g. `base`, `solana`       |
| question  | string | Yes      | Natural-language market intelligence query |

***

## Query Tips

* Use `$` before token tickers for better entity detection, e.g. `$AIXBT`, `$COOKIE`.
* Use token contract addresses when ticker is unknown.
* Add chain context when relevant.
* Ask specific questions for better responses.

***

## Example Questions

```
Give me deep analysis of $AIXBT

What’s the alpha score on $TOKEN this week?

Which token is outperforming on Base today?

Which genesis agents have the highest staking yield and activity today?

Analyze smart money flows for $VIRTUAL over the last 7 days

Is this token showing signs of accumulation or distribution?

Analyze token address 0x6982508145454ce325ddbe47a25d4ec3d2311933
```

***

## Example Requests

### Query by Token Ticker

```bash
curl -X POST 'https://api.dapplooker.com/v1/mcp' \
--header 'Content-Type: application/json' \
--data '{
  "api_key": "<API_KEY>",
  "chain": "base",
  "question": "Give me deep analysis of $AIXBT"
}'
```

### Query by Token Address

```bash
curl -X POST 'https://api.dapplooker.com/v1/mcp' \
--header 'Content-Type: application/json' \
--data '{
  "api_key": "<API_KEY>",
  "question": "Analyze the current market performance of token address 0x6982508145454ce325ddbe47a25d4ec3d2311933"
}'
```

***

## Example Response

```json
{
  "questionId": "ffd30ded-0a72-4735-8211-7daea644906c",
  "answerId": "aad9ac4e-2025-470e-97b1-29d7b6dca864",
  "nlpResponse": "Diving into the analytics of $AIXBT:\n\n- Current Price: Trading at $0.077, down by 3% in the last 24 hours.\n- Market Cap: Approximately $65.4M, down 3.1% over the last day.\n- Volume and Liquidity: 24h volume is around $29.6M, with total liquidity near $937.6K.\n- Recent Performance: Price is up 8.5% over the past week, while volume is down 30.6%.\n- Smart Money Activity: Top wallets bought around 2.6M AIXBT and sold around 5.3M AIXBT over the last day.\n- Developer Wallet Activity: No major outgoing developer wallet transactions detected.\n- Technicals: Support near $0.075, resistance near $0.088. RSI is around 35.9, suggesting the token may be approaching oversold territory."
}
```

***

## Response Schema

| Field       | Type   | Description                                                               |
| ----------- | ------ | ------------------------------------------------------------------------- |
| questionId  | string | Unique identifier for the submitted question                              |
| answerId    | string | Unique identifier for the generated answer                                |
| nlpResponse | string | Natural-language response generated from DappLooker intelligence datasets |


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dapplooker.com/products/api-endpoints/agent-infrastructure/mcp-nlp-market-intelligence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.