canonical: https://jentic.com/apis/nanodata.io/nanodata

# NanoData API

The NanoData API powers a crypto copy-trading and market-analytics platform. It places and manages exchange trades, copies other traders, reads open positions and market sentiment, returns leaderboard data, and creates Stripe checkout sessions for subscription payments.

## For AI agents

Place and manage crypto exchange trades, copy other traders, read open positions and market sentiment, query leaderboards, and start checkout sessions. Operations authenticate with an HTTP Bearer token (a JWT), aside from a Stripe webhook callback.

## Scope

Does not custody funds or settle exchange withdrawals. Use the NanoData API for trade placement, copy-trading, market sentiment, leaderboards, and checkout sessions only.

## Capabilities

- Place and manage exchange trades
- Copy the trades of another trader
- Read open positions on an exchange
- Query market sentiment indicators
- Retrieve leaderboard data
- Create a Stripe checkout session for a subscription

## Use cases

### Automated Exchange Trading

An AI agent connected through Jentic can act on a trading strategy. It places trades on a connected exchange and reads back the resulting open positions, so an assistant can execute a plan and confirm the position it opened.

Example prompt: Place a trade on the exchange and return the resulting open positions

### Copy Trading

Following successful traders is a core NanoData feature. The API starts copy-trading a chosen trader and exposes the leaderboard used to pick one, letting an agent shortlist top performers and set up a copy relationship.

Example prompt: Fetch the leaderboard and start copy-trading the top-ranked trader

### Market Analytics

Decisions need context. The NanoData API returns market sentiment indicators, so an agent can read the current sentiment before it recommends or places a trade and report the reading back to the user.

Example prompt: Read the current market sentiment and summarize it for the user

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/exchange` | Place an exchange trade |
| POST | `/api/exchange/copyTrade` | Copy another trader's trades |
| POST | `/api/exchange/getOpenPositions` | Get current open positions |
| GET | `/api/exchange/marketSentiments` | Get market sentiment indicators |
| POST | `/api/leaderboards/getLeaderboardsData` | Get leaderboard data |

## Key resources

- **Exchange** — Trades, copy-trades, and open positions
- **Market Data** — Market sentiment indicators
- **Leaderboards** — Trader ranking data
- **Payment** — Stripe checkout sessions for subscriptions

## Why Jentic

- **Setup:** Wiring the NanoData API by hand means obtaining a token, building trade and copy-trade payloads, and threading the token through every call yourself. Through Jentic you install once, import NanoData from the API Directory, store the token once, and your agent calls the trading and market operations directly.
- **Permission scoping:** You choose which of the operations your agent may call. You might allow market sentiment and leaderboard reads while blocking trade placement and copy-trading, so the agent can research without moving funds.
- **Credential handling:** Your NanoData token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'place a trade', and Jentic returns the matching NanoData operation with its input schema so the agent calls it with the right parameters.

## Related APIs

- **Binance** — Crypto exchange for spot and futures trading and market data
- **Coinbase** — Crypto exchange for trading, accounts, and market data
- **CoinGecko** — Crypto market data for prices, volumes, and market caps

## FAQ

### What authentication does the NanoData API use?

Its operations authenticate with an HTTP Bearer token that is a JWT, per the OpenAPI spec, aside from a Stripe webhook callback that the platform receives. Through Jentic the token is stored once, encrypted, by your own self-hosted instance and injected when the agent calls, so it never appears in the agent's prompt or logs.

### Can I limit what my agent is allowed to do with the NanoData API?

Yes. You choose which operations the agent may call. You might allow market sentiment and leaderboard reads while blocking trade placement and copy-trading, so the agent can research without moving funds, with every call logged by your own instance.

### Is there a NanoData MCP server?

You don't need an MCP server to give your agent the NanoData API. Jentic connects it directly from the API Directory: import it, store the token once, and your agent calls the trading, leaderboard, and market operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

### What are the rate limits for the NanoData API?

The OpenAPI spec does not define rate limits. Check the NanoData documentation for any current limits before running high-volume trading or market-data operations.

### What can the NanoData API do?

It places and manages exchange trades, copies other traders, reads open positions and market sentiment, returns leaderboard data, and creates Stripe checkout sessions for subscription payments.

### How do I read market sentiment through Jentic?

Search Jentic by intent, for example 'get market sentiment', and Jentic returns the matching NanoData operation with its input schema. Your agent calls it and reads back the current sentiment. To run it on your own infrastructure, install Jentic One from its GitHub repo.