LegendTrade

Legend (legend.trade) is a competitive social trading platform — it describes itself as "the esports layer for trading". Users trade perpetual contracts across 500+ crypto, equity, and commodity markets with leverage, and the platform wraps that in game mechanics: Arena head-to-head duels with ELO ratings and wagers, clans, leaderboards, a social feed, referrals, and copy trading that mirrors top traders in a single tap. Orders placed on Legend execute on Hyperliquid's on-chain order book, with Legend charging a builder-code platform fee on top of Hyperliquid's volume-tiered maker/taker fees. Legend is available on iOS, Android, web, and through a Telegram bot. Its programmable surface is a Hyperliquid-compatible read API at api.legend.trade (a multiplexed POST /info endpoint, custom sparklines, and an authenticated wallet-registration surface) plus a subscription-based WebSocket carrying market-data and account channels. Legend is backed by Electric Capital.

LegendTrade publishes 5 API contracts indexed on the APIs.io network, including Legend WebSocket API, Health API, Info API, and 2 more. Tagged areas include Company, DeFi, Trading, Cryptocurrency, and Perpetual Futures.

The LegendTrade catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

LegendTrade’s developer surface includes documentation, getting-started guide, support, engineering blog, signup flow, pricing, authentication, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.4/100 developing ▬ flat Agent 25/100 agent aware Front door AI 1/6 silent Heartbeat 38/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company DeFi Trading Cryptocurrency Perpetual Futures Social Trading Copy Trading Market Data Hyperliquid WebSocket Real-Time

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 42.4/100 · developing

Contract Quality 10.5 / 19

Developer Ergonomics 7.8 / 15

Access Clarity 6.7 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Securities & Market Data regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/legendtrade/"><img src="https://apis.io/badge/legendtrade/card.svg" alt="LegendTrade on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 0.0 — up to +13.0 composite points
Contract Quality scores 55.8 — up to +11.1 composite points
Access Clarity scores 44.7 — up to +11.1 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/legendtrade/apis.yml: open an issue on github.com/api-evangelist/legendtrade to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

WebSockets

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

AsyncAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Legend WebSocket API

Legend's Hyperliquid-compatible WebSocket at wss://api.legend.trade/ws, using subscription-based messaging. Public marketData channels stream trades, candles, and active asset c...

LegendTrade Health API

Service health and liveness.

LegendTrade Info API

Hyperliquid-compatible market and account info queries.

LegendTrade Market Data API

Legend-specific market data extensions.

LegendTrade Wallets API

Wallet registration for fill tracking (authenticated).

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Legend Info Health API

OPEN COLLECTION

Legend Health Info API

OPEN COLLECTION

Legend Info Health Market Data API

OPEN COLLECTION

Legend Info Health Wallets API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Discover Legend markets and price history

AGENT SKILL

Stream Legend market and account events

AGENT SKILL

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Legend WebSocket API

Legend's Hyperliquid-compatible WebSocket at wss://api.legend.trade/ws, using subscription-based messaging. Clients subscribe to named channels; the server streams matching even...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LegendTrade API Rules

53 rules · 51 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Legendtrade Info Overlay

7 actions · update · legendtrade-info-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Legendtrade Authentication

http · 1 scheme

SECURITY

Legendtrade Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Pricing

Pricing

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: legendtrade
name: LegendTrade
description: 'Legend (legend.trade) is a competitive social trading platform — it describes itself as "the esports layer for
  trading". Users trade perpetual contracts across 500+ crypto, equity, and commodity markets with leverage, and the platform
  wraps that in game mechanics: Arena head-to-head duels with ELO ratings and wagers, clans, leaderboards, a social feed,
  referrals, and copy trading that mirrors top traders in a single tap. Orders placed on Legend execute on Hyperliquid''s
  on-chain order book, with Legend charging a builder-code platform fee on top of Hyperliquid''s volume-tiered maker/taker
  fees. Legend is available on iOS, Android, web, and through a Telegram bot. Its programmable surface is a Hyperliquid-compatible
  read API at api.legend.trade (a multiplexed POST /info endpoint, custom sparklines, and an authenticated wallet-registration
  surface) plus a subscription-based WebSocket carrying market-data and account channels. Legend is backed by Electric Capital.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.legend.trade/images/og-image.png
url: https://raw.githubusercontent.com/api-evangelist/legendtrade/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- DeFi
- Trading
- Cryptocurrency
- Perpetual Futures
- Social Trading
- Copy Trading
- Market Data
- Hyperliquid
- WebSocket
- Real-Time
tags_raw:
- Company
- Defi
- Trading
- Cryptocurrency
- Perpetual Futures
- Social Trading
- Copy Trading
- Market Data
- Hyperliquid
- WebSocket
- Real-Time
apis:
- aid: legendtrade:websocket
  name: Legend WebSocket API
  description: Legend's Hyperliquid-compatible WebSocket at wss://api.legend.trade/ws, using subscription-based messaging.
    Public marketData channels stream trades, candles, and active asset context; account userData channels stream fills, open
    orders, order updates, clearinghouse state, funding, ledger updates, TWAP state and history, and notifications.
  humanURL: https://docs.legend.trade
  baseURL: https://api.legend.trade/ws
  tags:
  - Streaming
  - Market Data
  - WebSocket
  properties:
  - type: AsyncAPI
    url: asyncapi/legendtrade-ws-asyncapi.yml
- aid: legendtrade:legendtrade-health-api
  name: LegendTrade Health API
  description: Service health and liveness.
  humanURL: https://docs.legend.trade
  baseURL: https://api.legend.trade
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/legendtrade-health-api-openapi.yml
  - type: Documentation
    url: https://docs.legend.trade
- aid: legendtrade:legendtrade-info-api
  name: LegendTrade Info API
  description: Hyperliquid-compatible market and account info queries.
  humanURL: https://docs.legend.trade
  baseURL: https://api.legend.trade
  tags:
  - Info
  properties:
  - type: OpenAPI
    url: openapi/legendtrade-info-api-openapi.yml
  - type: Documentation
    url: https://docs.legend.trade
- aid: legendtrade:legendtrade-market-data-api
  name: LegendTrade Market Data API
  description: Legend-specific market data extensions.
  humanURL: https://docs.legend.trade
  baseURL: https://api.legend.trade
  tags:
  - Market Data
  properties:
  - type: OpenAPI
    url: openapi/legendtrade-market-data-api-openapi.yml
  - type: Documentation
    url: https://docs.legend.trade
- aid: legendtrade:legendtrade-wallets-api
  name: LegendTrade Wallets API
  description: Wallet registration for fill tracking (authenticated).
  humanURL: https://docs.legend.trade
  baseURL: https://api.legend.trade
  tags:
  - Wallets
  properties:
  - type: OpenAPI
    url: openapi/legendtrade-wallets-api-openapi.yml
  - type: Documentation
    url: https://docs.legend.trade
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/legendtrade-info-overlay.yaml
- type: Website
  url: https://www.legend.trade/
- type: DeveloperPortal
  url: https://docs.legend.trade
- type: Documentation
  url: https://docs.legend.trade
- type: GettingStarted
  url: https://docs.legend.trade/about/overview
- type: Support
  url: https://www.legend.trade/faq
- type: Blog
  url: https://www.legend.trade/blog
- type: SignUp
  url: https://app.legend.trade/login
- type: TermsOfService
  url: https://www.legend.trade/terms
- type: PrivacyPolicy
  url: https://www.legend.trade/privacy
- type: Pricing
  url: https://docs.legend.trade/about/fees
- type: LLMsTxt
  url: llms/legendtrade-llms.txt
- type: Authentication
  url: authentication/legendtrade-authentication.yml
- type: Conventions
  url: conventions/legendtrade-conventions.yml
- type: ErrorCatalog
  url: errors/legendtrade-problem-types.yml
- type: Lifecycle
  url: lifecycle/legendtrade-lifecycle.yml
- type: Conformance
  url: conformance/legendtrade-conformance.yml
- type: DataModel
  url: data-model/legendtrade-data-model.yml
- type: DomainSecurity
  url: security/legendtrade-domain-security.yml
- type: X-MCPServerCandidate
  url: mcp/legendtrade-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LegendTrade API — frequently asked questions

Does LegendTrade have an API?

Yes. APIs.io lists 5 APIs from LegendTrade, including Legend WebSocket API, LegendTrade Health API and LegendTrade Info API, and 2 more.

Is there an OpenAPI specification for the LegendTrade API?

Yes. APIs.io indexes 4 OpenAPI specifications for LegendTrade, each linked for download from this page.

How do I authenticate with the LegendTrade API?

LegendTrade uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Legendtrade Authentication.

Is the LegendTrade API ready for AI agents?

LegendTrade has a Kin Score of 42.4 out of 100 (developing) and an Agent Readiness score of 24.8 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/legendtrade"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/legendtrade/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/legendtrade/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.