Logo for SentXLogo for SentX
Logo for SentX
HBAR
For developers

The SentX API

Every listing, sale, floor and trait on SentX is reachable over REST. Four ways in, from anonymous market data to earning commission on trades you route.

Read the docs Get a key

OpenAPI 3 spec at api.sentx.io/openapi.json. Agents start at api.sentx.io/llms.txt.

Pick your lane

Four ways in

Same API underneath. The key you hold decides what it will do for you.

Public data

Listings, sales activity, collection stats, floor prices, trait rarity and wallet holdings over plain GET requests. A free key from your settings page unlocks it.

Your account, scripted

The same key can act for your wallet, one permission at a time. Collection offers are live today: place, top up and cancel collection offers from a script while your NFTs and HBAR never leave your wallet. Each capability is a switch in your settings, off until you flip it.

Affiliate

List, buy and mint for your users from your own app and earn a share of the marketplace fee on every trade you route. Commission settles on chain, straight to your wallet, at the moment of sale. One rule: trading goes through the API end to end.

AI agents

Built for Claude and any MCP client. A key costs nothing and takes one request, no account needed. The MCP server exposes eight market tools and is read-only by design: an agent can research the whole market and never spend a tinybar.

Three steps

Connect an agent

1

Create a key

One request. The sxagent- key is shown once, so store it. Unused keys expire after 7 days; the first call makes a key permanent. Prefer one you can see and revoke later? Create it from the agent keys card in your settings instead. 

curl -X POST https://api.sentx.io/v1/agent/keys \
  -H "content-type: application/json" \
  -d '{"label": "my research agent"}'
2

Point your client at the MCP server

Works with Claude Desktop, Claude Code and anything that speaks MCP over Streamable HTTP. 

{
  "mcpServers": {
    "sentx": {
      "url": "https://mcp.sentx.io/mcp",
      "headers": { "x-api-key": "sxagent-..." }
    }
  }
}
3

Ask it something real

The tools cover collections, floors, listings, trait rarity, sales activity, single NFTs, wallet holdings and open offers. "What is the cheapest Laser Eyes on the floor" is now a one-liner. Plain REST is always there too, documented for machines at api.sentx.io/llms.txt.

Rate limits answer 429 with a retryAfter you should honor. Stuck? Ask on Discord.

Working with the data

Add marketplace context to your NFT application

Use SentX's public API reference to find the data and request formats available for your integration. Start with one question your application needs to answer, then check the documented fields and limits for that endpoint.

Open the API reference.

Match collections by token ID

Keep the Hedera token ID with collection data in your application. A display name is useful to people but is not a reliable join key between services.

When working with individual NFTs, keep the serial and network too. Read an NFT through a mirror node to see the ledger side of the same identifier.

Keep market events distinct from transfers

A marketplace sale and a network transfer answer different questions. Use the documented market-event fields when showing sales or prices, and use ledger data when checking token movement or ownership.

For collection statistics, label the currency, time window and calculation represented. An unavailable response should not become a zero-volume or zero-price claim.

Build for the documented service

Read the current authentication, pagination and limit requirements before integrating an endpoint. Cache appropriate public data and handle errors explicitly.

Do not place private credentials in browser code. Avoid running write or trading operations as part of a documentation preview. A read-only display is a useful first integration to validate. New to the network? Start with the Hedera developer guide.