Synthwav Portal API
Signal strength, not investment quality. TIP measures the strength of the specific signals defined in its published methodology. It is based on measurable token fundamentals and available on-chain data and is not an investment rating.
The Synthwav Portal API gives approved protocols direct access to the same canonical token profiles used by Synthwav. It combines registry metadata, provenance, authority and Steward information, market data, the Token Score and TIP Grade, stored Token Analysis, timestamps, and stale-state indicators into one versioned response.
Base URL
https://api.synthwav.io/api/v1/tip
All Portal API requests require an API key in the x-api-key header. Contact SynthwavLabs to request partner access.
Existing integrations using https://synthwav.io/api/v1/tip remain supported for compatibility. New integrations should use the canonical api.synthwav.io hostname.
Available endpoints
| Method | Endpoint | Purpose |
|---|---|---|
GET | /tokens/search | Find canonical token identities by ticker, name, address, or Coin type. |
GET | /tokens/{assetType}/{id} | Retrieve one complete canonical TIP profile. |
POST | /tokens/batch | Retrieve up to 20 profiles in one ordered request. |
Canonical token identity
Every profile represents one canonical token family. A family may contain an original Coin, its framework-paired FA, and verified wrapper FAs:
- Fungible Asset tokens use
assetType: faand their metadata address. - Coin tokens use
assetType: coinand their complete Coin type. - Symbols such as
SUPRAWRare search terms, not canonical IDs. - Search by any verified family member returns the canonical family identity.
- FA-only assets with no verified relationship remain unchanged as one-member families.
The response family object exposes only the canonical root, stable tipProfileId, and conflict state. Verified member identities remain internal. Metadata edits and authority checks resolve through the canonical root; wrapper ownership does not grant TIP edit authority.
Search results include additive authority and Steward fields for list views: verification.authorityVerified, verification.authorityVerifiedAt, and verification.stewardActive. Authority verification means the current canonical authority or an active Steward signed Synthwav's challenge, or a Synthwav registry administrator manually verified the family; the timestamp is null when no active verification exists. Manual profile verification reports authority.method as admin-manual. These additions remain within API v1, so existing integrations can ignore them.
Canonical family metrics follow strict rules: market cap is calculated once from the canonical price and verified supply pair; TVL sums distinct positions across Atmos, Spikey, LeoEx, Dexlyn, and supported Solido deposits; and 7-day activity is a unique transaction union across the indexed DEXs. Missing verified inputs produce score.status: unavailable instead of a guessed score.
Token Score methodology version 4 expands canonical TVL to include indexed DEX liquidity and supported protocol deposits such as Solido. Depth remains TVL / Market Cap * 100, using that same canonical total. The API path and profile version remain v1; partners require no response-shape changes.
The canonical SUPRAWR identity is:
fa:0x82ed1f483b5fc4ad105cef5330e480136d58156c30dc70cd2b9c342981997cee
Quick start
curl "https://api.synthwav.io/api/v1/tip/tokens/search?query=SUPRAWR" \
--header "x-api-key: ${TIP_API_KEY}"
The full machine-readable contract is available at:
https://api.synthwav.io/openapi.jsonhttps://api.synthwav.io/api/openapi
Contract changes
1.8.0 — September 21, 2026
Token search responses now include the required additive fields verification.authorityVerified and verification.authorityVerifiedAt. The existing verification.stewardActive field is now explicitly required by the OpenAPI schema, matching the response already returned by the service. The endpoint path and response meta.apiVersion remain v1.
Authority verification can also be assigned manually by a Synthwav registry administrator. An active Steward can verify the token family they steward. Response shapes are unchanged; profiles identify these sources with authority.method: "admin-manual" or "steward-signature-v1".
Clients should tolerate additive response properties. Strict validators generated from an older OpenAPI document must update to the 1.8.0 contract before validating token search responses.
TIP data is informational. A TIP Grade or Token Analysis is not a smart-contract audit, endorsement, or guarantee of token safety.