OpenAPI Specification

All 41 live /v1 operations are described by the OpenAPI 3.1 specification. Planned operations are excluded so generated agent clients contain only callable production routes.

Download

curl -O https://docs.conyr.ai/openapi.yaml

Spec covers the full live surface. The hosted contract includes wallet/KOL identity resolution, liquidity depth and LP events, holders, bundles, coordination v2, intel composites, funding abuse, buyer quality, profile/similar/provenance, entanglement, wash patterns, and suspicious activity. Every /v1 operation carries an x-tier extension.

Spec Details

Version: OpenAPI 3.1.0
Auth: HTTP Bearer (securitySchemes.BearerAuth)
WebSocket: Documented as component schemas (WsClientMessage, WsServerMessage, WsChannelFormat)

Tag	Description
Wallets	Performance, trades, positions, public identity, labels, position-correct quality, profile, similarity, provenance
Leaderboard	Ranked wallet leaderboards by PnL, ROI, or win rate
Tokens	Token info, OHLCV, trades, liquidity depth/events, holders, bundles, and security signals
Coordination	coordination-v2 follows, entities, campaigns, crowd state, and health
Intel	Cross-cutting coordination intelligence composites
Operations	Health, readiness, Prometheus metrics

Operation IDs (current spec)

These operations are present in the live spec and stable:

getHealth
getReadiness
getMetrics
getWalletPerformance
getWalletTrades
getWalletPositions
getWalletLabels
getWalletIdentity
getKolWallets
getWalletQuality
getWalletProfile
getWalletSimilar
getWalletProvenance
getWalletEntanglement
getWalletFollows
getWalletEntity
getLeaderboard
getTokenInfo
getTokenOhlcv
getTokenTrades
getTokenLiquidity
getTokenLiquidityEvents
getTokenHoldersSummary
getTokenHoldersTop
getTokenHolders
getBuyerQuality
getTokenBundleSummary
getTokenBundles
getBundleDetail
getWashTrades
getFundingAbuse
getSuspiciousActivity
getTokenCampaigns
getTokenCrowd
getEntityDetail
getEntityMembers
getCoordinationHealth
getFormingCoordinatedPushes
getFollowerCascade
getEmergingEntities
getTokenEarlyBuyers
getTokenCopyOriginator
getTokenEntityConcentration
getTokenLateRetail

Public identity operation selection

Start with getKolWallets when the input is an X or Telegram handle. Pass the platform when known; a successful no-match is wallets: [], not a 404.
Start with getWalletIdentity when the input is a Solana wallet. A successful no-match is primary: null with aliases: [].
Use getWalletLabels for behavioral classification, not as the canonical identity lookup. It can return literal null for a wallet that still has a direct identity.

See KOL Identity Workflows for platform filtering, freshness, and safe interpretation of source_asserted.

Contract boundary

If an operation is absent from this spec, it is not part of the public REST contract. Agents should not synthesize endpoint names from roadmap discussions or older integrations.

MCP Server Endpoint Reference