Feature Flag API
EdgeAssign is a feature flag API for teams that want an API-first control plane and deterministic outcomes.
It is the category page: a single endpoint for eligibility and rollout, built for stable results across backend, frontend, and edge environments.
When teams reach for a feature flag API
- One control surface for rollout and eligibility logic.
- Stable decisions across services and client environments.
- Simple API integration without a heavyweight platform.
How EdgeAssign treats the category
- Single-call evaluation with optional traits.
- Deterministic bucketing derived from stable inputs.
- No per-user assignment store to maintain.
Request and response example
# PowerShell (safe JSON)
$body = @'
{"subject":"alice","traits":{"plan":"pro","beta":true}}
'@
curl.exe -X POST -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" --data-binary $body "https://api.edge-assign.com/v1/eval/prod1/new_checkout"
{
"eligible": true,
"enabled": true,
"bucket": 8,
"rollout_percent": 25
}Why this is different from typical platforms
- API-first and narrow scope instead of platform sprawl.
- Derived decisions instead of stored assignment history.
- Predictable outputs you can cache safely.
If you want a vendor comparison, see EdgeAssign vs. the usual options.
Who it is for
- Teams that need stable rollouts across many services.
- Developers who want API-first control without heavy platforms.
- Apps where caching, privacy, and speed matter.
FAQ
Does the same user always get the same answer?
Yes. The same subject and inputs produce the same decision every time.
Do you store rollout assignments?
No. Decisions are derived deterministically on demand.
Can I cache responses?
Yes. Deterministic responses are safe to cache at the edge or service layer.