Build with Signal

Public data API

Base URL: https://signal.family. The GET endpoints below serve public indexed or cached data, with access-control-allow-origin: *. They are not a trading API, not a complete chain archive and not a latency promise. Nothing here signs or submits a transaction.

The API indexes the whole HyperEVM tape, not only tokens launched on Signal. A Signal launch is a row with born: 1. A Signal v4 launch also has launch_venue: "v4".

Rules of the road

• Follow redirects. Some reads answer 307 to another origin that serves them.
• An error can be HTTP 200. Several endpoints answer 200 with an error key: {"error": "bad address"}, {"error": "never seen it trade"}. Check for error before reading fields.
• A record can be partial. A token record that could not be built in time returns partial: true with routable: false. Absence in a partial record means "not read", not "none".
• Rate limits answer 429 with retry-after. A busy or starting server answers 503 with retry-after and busy or booting in the body. Back off; do not retry in a loop.
• ETags. Most JSON endpoints send an ETag and answer 304 to If-None-Match. Use it.
• Missing, stale, partial and unpriced values are different from zero. Do not turn a timeout into an empty wallet or a failed payout.

Endpoints

Configuration

The Signal v4 keys of /api/config are v4_lane_v42 (release 4.2), v4_lane_v4 (release 4.1), v4_lane_v2, and two with no pools. Each carries:

Tokens

A Signal v4 token's record adds:

v4_launch carries pool_id, pool_key, token_is0, creator, born_block, born_tx, contracts, and:

• terms: the hook's terms(poolId) read at the launch block. See fees and rules for every field.
• state: the hook's views as last read (buy_rate, sell_rate, prices, pool_state, stats, held, and more), with state_read_at. Amounts are raw pair-asset units as decimal strings.
• recent: the newest hook events for this pool (flushed, boughtback, potwon, legpaid, and the change events).
• destinations and module: who may re-point the fee, open proposals and when they can activate.

state is a cache. During an opening window the live rate moves every second: read the hook.

Trades and charts

A trade row has ts, tx, log_index, token, side, usd, price, pool, who (the swap's recipient, usually a router), origin (the transaction's sender), via (the contract the transaction called), suspect and leg.

• suspect above zero marks a print the site leaves out of every figure it derives: priced far from the token's own recent prints (1), a quote leg that is not a verified asset (2), a small fill through a thin side pool (3), a second copy of a print (4). The tape still lists it. Filter on suspect == 0.
• leg marks a print that is part of a route and not a position: "hop", "loop", "internal". Null is a trade.
• On a Signal v4 pool usd and price are the pool's amounts, without the hook's fee. Where the indexer paired the swap with the hook's FeeTaken, hook_fee_usd and paid_usd give the fee and what the trader paid or received. They can be null; do not rely on them for every print.

/api/live first answers 307; follow it. Every message is a bare data: line of JSON with no event name and no id, so there is no replay: after a reconnect, read /api/tape and the records you show again. A heartbeat arrives every five seconds. The stream carries the whole chain's trades, not only Signal's.

Safety

/api/safety/<address> returns Signal's reading of a token: verdict (ok, caution, danger, unknown, or pending), reasons, ts, stale, check_failed, and what was measured (sells, round_trip_cost_pct, transfer_tax_pct, static, concentration). A 503 with check_failed: true and no verdict means the check could not run and no reading stands. 60 requests a minute.

For most tokens the reading includes a simulated buy, transfer and sale. A Signal v4 pool is not simulated this way. Its reading describes the launch's fixed code and locked liquidity and says nothing about its opening fee, taxes or extras. Read those from v4_launch.terms and from the hook.

A verdict is a reading with a time, not a guarantee. See token safety for how the site uses it.

Holders, rewards and payouts

Money owed is not money paid. Figures labelled paid come from payment receipts on chain.

People

Classic and perp reads

/api/pool-fees/<token>, /api/core/markets, /api/strategies and /api/strategies/holder?token=&holder= serve Classic launches and perp rewards as described in their guides. None of them describes a Signal v4 pool.

A bounded request

curl --fail --location --max-time 20 \
  https://signal.family/api/token/0x1b67a2ac4dc5faab20554d379af5148b8b70f626

For trading, use the API for discovery and context, then read and simulate the contracts.

Fast clients without waste

Share one snapshot among everything that shows the same resource. Cache configuration and identities. Use the stream to know when to re-read, not as the data of record. Send If-None-Match. Avoid cache-busting query strings and independent rapid polling by every card.

Keep source times and block numbers where the API supplies them. Your fetch time does not make an old observation fresh. Rebuild durable history from chain logs when your product needs completeness.

Fields can be added over time. Validate what you depend on, and reject a version you do not know instead of guessing.