Feature flag API for deterministic rollouts and user bucketing.

Rules + eval in one request

Send a subject and traits, evaluate eligibility, and apply rollout percentages in a single call. Use rules like plan in ["pro","team"] or beta == true without extra endpoints.

# 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"

# macOS / Linux
curl -X POST -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"alice","traits":{"plan":"pro","beta":true}}' \
"https://api.edge-assign.com/v1/eval/prod1/new_checkout"

Zero billing anxiety

Over-quota behavior is a production concern, not a billing footnote. EdgeAssign is designed to keep your app alive.

• Warnings at 80%, 90%, and 100% of your monthly limit.
• 7-day grace window up to 120% after you hit 100%.
• After grace, traffic is throttled (slower), not hard-stopped.
• No surprise upgrades; billing changes only with explicit opt-in.

Caching guidance

Deterministic responses work well with edge or service-layer caching. For most use cases, a 30–60 second TTL provides a practical balance between lower latency and near-real-time rollout control.

Prefer stale-while-revalidate during brief outages: serve the last-known decision while revalidating in the background. Store last-known-good decisions in a durable layer (edge KV or similar) so cache evictions do not cause sudden behavior changes.

Backend key rotation invalidates old keys immediately, but cached authorizations may linger until TTL expiry.

Warning: do not send raw PII in traits. Map sensitive data to SafeTraits (booleans or coarse labels) before it leaves your infrastructure.

# PowerShell (safe JSON)
curl.exe "https://api.edge-assign.com/health"
curl.exe -H "X-API-Key: YOUR_API_KEY" "https://api.edge-assign.com/v1/flag/prod1/new_checkout/alice"
$eval = @'
{"subject":"alice","traits":{"beta":true,"plan":"pro"}}
'@
curl.exe -X POST -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" --data-binary $eval "https://api.edge-assign.com/v1/eval/prod1/new_checkout"
$batch = @'
{"items":[{"subject":"alice","traits":{"plan":"pro"}},{"subject":"bob","traits":{"plan":"free"}}]}
'@
curl.exe -X POST -H "X-API-Key: YOUR_API_KEY" -H "Content-Type: application/json" --data-binary $batch "https://api.edge-assign.com/v1/eval-batch/prod1/new_checkout"
curl.exe -H "X-API-Key: YOUR_API_KEY" "https://api.edge-assign.com/v1/bucket/prod1/alice?mod=100"

# macOS / Linux
curl "https://api.edge-assign.com/health"
curl -H "X-API-Key: YOUR_API_KEY" \
"https://api.edge-assign.com/v1/flag/prod1/new_checkout/alice"
curl -X POST -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject":"alice","traits":{"beta":true,"plan":"pro"}}' \
"https://api.edge-assign.com/v1/eval/prod1/new_checkout"
curl -X POST -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"subject":"alice","traits":{"plan":"pro"}},{"subject":"bob","traits":{"plan":"free"}}]}' \
"https://api.edge-assign.com/v1/eval-batch/prod1/new_checkout"
curl -H "X-API-Key: YOUR_API_KEY" \
"https://api.edge-assign.com/v1/bucket/prod1/alice?mod=100"

# Learn more at https://edge-assign.com/docs.html

Why no SLA?

EdgeAssign is lean by design. The architecture removes many failure modes that force heavy support structures, so support is direct and technical rather than layered and bureaucratic.

• Deterministic, stateless evaluation means no assignment database to corrupt.
• Edge caching and short TTLs absorb traffic spikes while keeping rollouts predictable.
• Fewer moving parts means fewer incident classes and faster diagnosis.

If you do need help, you get direct access to the engineer who built the system.