Agent CapabilitiesOpenAPI Spec

OpenAPI Specification

All 39 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 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)

Tags

TagDescription
WalletsPerformance, trades, positions, labels, position-correct quality, profile, similarity, provenance
LeaderboardRanked wallet leaderboards by PnL, ROI, or win rate
TokensToken info, OHLCV, trades, liquidity depth/events, holders, bundles, and security signals
Coordinationcoordination-v2 follows, entities, campaigns, crowd state, and health
IntelCross-cutting coordination intelligence composites
OperationsHealth, readiness, Prometheus metrics

Operation IDs (current spec)

These operations are present in the live spec and stable:

getHealth
getReadiness
getMetrics
getWalletPerformance
getWalletTrades
getWalletPositions
getWalletLabels
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

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.