Production WS
wss://corto.fun/data-stream
Free public stream. One IP can keep one active connection open at a time.
Public Reference
Data Stream API Overview
This page shows what the public WebSocket sends today, what can still be null or missing, and what your client should not assume.
Control messages
subscribe, unsubscribe, current_state
You change filters by sending messages, not by reconnecting every time.
Create detail
min, mid, full
You can choose how much data create messages return without opening a separate stream.
What this page covers
WebSocket endpoint
The public WebSocket endpoint is /data-stream.
Guarantee model
A field can always be present, but its value can still be optional, conditional, or null. Do not assume that every field is always filled.
System messages
Handshake, subscription acknowledgement, current state, and structured errors tell you the connection status and which filters are active.
Event messages
Launch and pool events are sent only when they match the current filter.
Create detail levels
| Level | What it keeps | Typical use |
|---|---|---|
| min | Launch identity, short token metadata, block, and timestamp. | Fast mint feeds and watchlists. |
| mid | Everything from min plus market, metadata, supply, and risk fields. | Rankers, UI cards, and alerting. |
| full | Everything from min and mid plus reserves, fees, pool mechanics, and extended create diagnostics. | Deep analytics and production parsing. |
create.detailis carried inside the same subscribe message.- If it is omitted, the server uses
full. - The current value is returned back as
effectiveFilter.createDetail.
What is actually live today
| Family | Current state | Main boundary |
|---|---|---|
| Create | Live public payloads observed. | Some economics stay family-specific and must not be universalized. |
| Trade | Live on pump-fun and letsbonk-fun paths. | Transport differs by family; nullable values stay nullable. |
| Migration | Live through lifecycle detection plus parsed transaction resolution. | No logs-only simplification. |
| CreatePool | Observed payload exists. | Lineage and some liquidity values are conditional. |
| Liquidity | Observed remove payload exists. | Real add payload is still pending capture. |
| Burn | Reserved contract only. | No observed production public payload yet. |
How clients should think about the stream
- System messages describe connection state and the current filter.
- Event messages include create, buy, sell, migration, createPool, addLiquidity, removeLiquidity, and the reserved burn event.
- Quick modes are just shortcuts for the same subscribe rules used by pro mode.
create.detailchanges only how much data create messages return.nullis valid when a field is marked as conditional.- The fastest way to inspect live messages is the Data Stream Builder.
What is not proven yet
Read this as API docs, not marketing: if a value or path is not explicitly documented as reliable here, treat it as optional or dependent on the current message path.
Burn path
Burn is already listed as a public event, but real public burn messages have not been seen yet.
Letsbonk creator fee
creatorFeeAddress can be null on a cold server or cache miss. That is a valid result.
Conditional economics
Pool-side values like lineage, LP mint, liquidity totals, or price should only be treated as strong when proven by the current transaction.
Observed examples and next pages
| Family | Signature / example source | Why it matters |
|---|---|---|
| Create | 2i4j3aNSP4y6usMHwf4k8Gf5v8Cir6TcNiS7NK8CQsfcdwAGqXkrWKRPthCw7T9JpjsNo9hhzYzqDEYS6n4cMi6n | Shows current create contract with risk and token metadata fields. |
| Trade | 5GL8LJGm6gcRFRRCd6ss5eyHLV1yipJnovh6zQWUASJTdUJVE2ZKRmJ2KpDxRwTdPmCUeZGzCmd11WwjeqfbHv8V | Shows the current public buy/sell schema and transport-specific values. |
| Migration | pump-migration-test | Shows parsed-tx migration shape and what is intentionally excluded. |
| CreatePool | 4ViJScYg612DtdnV1iZKBDc2ZVnWwX1QAfurTcHNNNGkAoR3E2FnWdXXo34MAvk3TK8ux2mXKZPs5RHnhKN9uN4d | Shows pool-side create contract with initial liquidity fields. |
| Liquidity | 29VK4NCy6Z9V4p5FfMfRkrBbAUuqohM94FFMKZyGBk3TcZMMvfTSVPAZAhjZVLwqyA9dbHxysr5zg6RAgxURjAet | Shows current observed remove payload and honest addLiquidity status. |
| Burn | Reserved contract only | Documents the intended shape without inventing a fake production example. |
Reference sections
JSON Contract
Control messages, system messages, quick modes, and error format.
Open contractCreate
Create messages, field groups, and what is currently reliable.
Open create schemaTrade
Current transport split and nullable boundaries that must be preserved by clients.
Open trade schemaMigration
Lifecycle detection plus parsed-tx migration resolution.
Open migration schemaCreatePool
The moment a target pool account is created on the public path.
Open createPool schemaLiquidity
Shared add/remove schema with the currently observed remove payload.
Open liquidity schemaBurn
Reserved schema with an explicit honesty boundary until production examples exist.
Open burn schema