Jupiter Developer Platform Changelog

An organisation groups your teams, and each team has its own API keys, analytics, request logs, and firewall rules. Keep production in one team and staging in another, or one team per app. Three organisation roles (owner, admin, member), email invitations, and multiple owners are supported.

WTM (what this means) - You no longer share one undifferentiated account. Traffic, keys, and access are separated per product or environment, and you can give a teammate access to one team without giving them everything.

Organisations & Teams

By default a key can call every Jupiter API. Permissions turn a key into an allow-list of products (Swap, Tokens, Price, Trigger, Recurring, Portfolio, Lend, Send, Studio, Prediction), matched by path prefix at the gateway. A request to a disallowed endpoint returns 403 Forbidden. Key changes take effect within about 15 seconds.

WTM - A key that runs in a client app, or one that leaks, can only reach the APIs you allowed.

API Keys

Per-team rules evaluated at the gateway before requests reach the API. Conditions match on path, IP or CIDR, country, method, headers, and API key, combined with AND/OR. Four actions: Log, Deny (403), Rate limit (per IP, per key, or per team, 429 when exceeded), and Bypass for trusted traffic. Up to 50 rules per team, with deterministic precedence: Bypass beats Deny beats Rate limit beats Log, then specificity, then age.

WTM - Keys used in browsers and mobile apps are readable by anyone. The firewall limits what a copied key is worth: restrict it to the endpoints and regions you actually use, and block or rate-limit abusive traffic at the gateway.

Firewall

Every request made with a team's keys, newest first, filterable by status, method, API group, and path. Each entry records the full picture: client IP, country, status, credits consumed, a latency breakdown, and the firewall outcome with the rules that matched. Retained for 6 months.

WTM - Debugging an integration no longer requires guessing what the gateway did. The log shows what was sent, what it cost, and why it was allowed, denied, or rate-limited.

Request Logs

Per-team and per-API traffic, performance, cost, and origin: request and error rates, latency p50/p95/p99, credits over time, status-code and geographic distributions, and top paths, all with period-over-period trends. Firewall analytics show outcomes over time and rule-match counts. Covers the last 6 months.

Analytics

Two-factor authentication with an authenticator app, email codes, and backup recovery codes. An audit log records 17 event types across API keys, plan and payments, members, and firewall rules, retained for 1 year (payment events for 7).

Account Security

Live at developers.jup.ag/portal, replacing the old portal. Create an account, generate API keys, pick a plan, and watch your usage in one place. The docs were rewritten for the launch: setup, plans, rate limits, response codes, migration from lite-api.jup.ag, and an FAQ.

Get Started · Migration Guide

Free (1 RPS, no payment), Developer (10 RPS, 25M credits), Launch (50 RPS, 100M credits), and Pro (150 RPS, 500M credits), with overage billing beyond included credits. Per-endpoint credit costs vary; execute endpoints cost 0 credits. Keyless access stays available at 0.5 RPS.

Plans and Pricing

Each gets its own bucket, separate from the general API limit and from each other: Keyless 20 RPS, Free 50 RPS, Paid 100 RPS.

WTM - Heavy order-fetching no longer throttles your transaction landing.

Rate Limits