summary: the licensing and data-rights side of the edgeful API — what you can do with the data you pull, what you're allowed to cache or retain, how multiple API keys interact with rate limits, and when a use case crosses into needing an Enterprise license. the setup guides cover how to connect; this covers what you're allowed to do with what you pull. the binding version of all of this is the edgeful terms of service.

the edgeful API is included on every plan, and most members use it to pull report data into their own dashboards, bots, and analysis. that raises a fair question: what am I actually allowed to do with the data once I've pulled it — keep it, build on it, use it commercially? this article covers the rules in plain english — the binding version is always the edgeful terms of service. if you just want to get connected, start with the edgeful API — overview + walkthrough.

personal use means pulling edgeful data for your own trading, research, and analysis — your own dashboards, your own bots, your own decisions. that's what the API is built for and what every plan includes.

commercial use means anything where edgeful's data leaves your own use — reselling or redistributing it, building it into a product or service you charge others for, publishing it, or feeding it to clients. that's a different category with different terms, covered in the terms of service. if that's the direction you're heading, talk to us first (see the Enterprise section below).

caching responses is not only allowed, it's encouraged — caching for the duration of a trading day is the simplest way to stay well under the rate limit. the open question members ask is how long they can keep the data and what they can build on top of it.

the line that matters is personal vs commercial use, above: keeping and building on the data for your own trading and analysis is what the API is for. retaining it to redistribute, resell, or fold into something you offer to others is the commercial side, and is governed by the terms of service. if your case sits anywhere near that line, check with us before you build rather than after.

a common assumption is that generating more API keys gets you more throughput. it doesn't.

the rate limit is the same on every tier — 30 requests per 60-second window (sustained) plus a burst allowance of 5 requests per 5 seconds. limits are tracked per key but aggregate at the account level, so spreading requests across several keys doesn't raise your ceiling — they all draw from the same account budget.

multiple keys are still useful for organization — a separate key per project or environment so you can rotate or revoke one without touching the others. just don't expect them to multiply your throughput. if caching and exponential backoff still aren't enough for your workload, that's a sign to talk to us about your use case rather than minting more keys. full detail is in rate limits and tier differences.

the standard API access on essential, pro, and all access is built for individual members using the data for their own trading and analysis. some use cases go beyond that and need an Enterprise arrangement.

if your use case goes beyond your own trading and analysis — redistributing or reselling the data, building it into a product or service you charge for, or needing throughput beyond the standard rate limits — reach out through the in-app chat (or email [email protected]) with a short description of what you're building, and the team will point you to the right arrangement.

data-rights and licensing questions don't always fit a tidy yes/no — if yours isn't covered above, ask through the in-app chat with the specifics of what you want to do with the data. it's always better to confirm before you build than to find out after. the binding terms are in the edgeful terms of service.