A production KyberSwap integration should follow the current gateway guidance and obtain the access terms that apply to its workload. An old example using a public endpoint is not sufficient evidence of today's commercial access policy.
The EVM swap specification, checked September 24, 2026, announces a gateway migration, requests an API-key header and directs integrators to the Business Development team for keys. It says the previous base URL remains available with rate limits. The document also discusses client identifiers, which should not be confused with a secret API credential.
There is an explicit documentation conflict: the general overview still says public APIs require no key, while the endpoint-specific migration notice requires one for the new EVM gateway. Both were checked on September 24, 2026. Apply the key requirement to that gateway; do not claim every KyberSwap API universally requires authentication. The older rate-limited base is separately documented as available.
What remains a commercial question
The retrieved specification does not provide a complete public subscription price table or a universal production request allowance. This guide therefore does not assign an invented “free tier” price or borrow numbers from KyberSwap's separate zap service.
Ask the provider to confirm:
- The gateway and API version covered by the account.
- Allowed request rate, burst behavior and any monthly ceiling.
- Quote polling versus transaction-build expectations.
- Support and incident escalation.
- Permitted partner monetization and fee disclosure.
Capacity should follow intended use
A comparison website requesting many indicative routes has a different workload from a wallet building transactions only when users confirm. Communicate that difference when requesting access. The specification includes conditions on some transaction-building paths, so technical endpoint availability should not be interpreted as unrestricted commercial use.
Keep migration separate from rewriting the product
First establish the required account, key and agreement. Engineering can then adapt authentication and endpoint usage under a known target. Without that sequence, a team may spend time optimizing a legacy path that the provider already recommends replacing.
Save the confirmed limits and contact details alongside the integration's release notes. Those facts are operational dependencies, not merely procurement paperwork.
Sources & verification (2)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- EVM Swaps
The new EVM Swap gateway requires an API key obtained through Business Development. The older base remains rate limited. Client identifiers, partner fees and surplus rules are separate.
https://docs.kyberswap.com/developer-guide/aggregator-api/aggregator-api-specification/evm-swaps - Introduction to KyberSwap
The general overview still describes public APIs without required keys, while the newer EVM gateway notice requires a key. Claims must preserve that endpoint-specific distinction.
https://docs.kyberswap.com/