# gonk.fun public Solana API

Use [OpenAPI](https://gonk.fun/openapi.json) for the public read-only routes. Start with GET /api/solana/v1/status for current costs and availability. Use the coin list to discover launches, the coin detail to inspect recent indexed trades, and holdings to read an address’s token balance. The v1 API does not grant wallet permissions. See the [private MCP integration guide](https://gonk.fun/mcp) for wallet-approved actions.

## Versioning and deprecation

New integrations should use /api/solana/v1/. Existing unversioned routes remain supported and are not deprecated. Breaking changes will use a new major URL version. For planned retirement, we publish a migration notice and use the [Deprecation](https://www.rfc-editor.org/rfc/rfc9745.html) header; when a removal date is set, we also use [Sunset](https://www.rfc-editor.org/rfc/rfc8594.html). There is no scheduled sunset for v1.

## Errors and rate limits

REST errors include an HTTP status and a JSON body with error, code, message and resolution. Check the status rather than interpreting the error string. A 404 means check the path or resource address; a 429 means wait for Retry-After before retrying.

The v1 service shares a quota of 60 requests per 60 seconds per client IP. RateLimit and RateLimit-Policy carry IETF draft structured fields. RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset are also provided for compatibility; Reset is seconds until the current window resets. Other protection layers can apply separate limits.
