FullHunt evaluates access from the API key and its associated account. Use GET /api/v1/auth/status as the runtime source for plan and credit context.

​
Access classes

This table describes API gates, not a pricing comparison. Account packaging can change independently of endpoint behavior.

​
Credits

  • Credits and rate limits are separate controls.
  • Current Nexus operations deduct one credit after a validated successful request.
  • OEM routes marked as credited deduct one OEM credit on their success path.
  • OEM credit balance and audit-log operations do not deduct OEM credits.
  • A non-deduplicated queued OEM scan consumes a credit; status checks do not.
  • Global Search accepts authenticated users with available credits and returns up to 10 records per page.
  • Result limits can also depend on the account and endpoint.

​
Verify access

Read user.plan and user_credits from the response. Do not hard-code a marketing plan name as proof that a module is enabled; handle 403 Forbidden from the requested operation.

​
Production controls

  1. Check credit context before high-volume jobs.
  2. Set a per-run request and credit budget in your application.
  3. Tag OEM requests with stable tenant and request identifiers.
  4. Stop retrying when the account returns an entitlement or credit failure.
  5. Reconcile usage from response metadata and OEM audit logs where available.
See Rate Limiting for route frequency limits.