AAtlas API
Reference

Pricing and Metering

Plans, usage limits, and how Atlas meters your account.

Plans

PlanPriceBest for
TrialFree for 14 daysEvaluating the API and testing your integration
BuildFrom 75,000 NGN/monthFirst production workflow: fund pages, filing monitors, internal tools
CustomContact usBrokers, PFAs, banks, or any workflow that needs custom volume, routing, or SLA

Trial includes soft usage limits across endpoints, events, and webhook delivery.

Build includes covered entities, matched events, webhook deliveries, and a small AI allowance. Atlas handles overages through plan review, not automatic charges.

What counts toward usage

UnitWhat it measures
Covered entitiesFunds or issuers your organization actively tracks through subscriptions, routing, or workflow usage
Matched eventsEvents that match one of your active subscriptions or tracked entities
DeliveriesWebhook payloads sent to your configured endpoints
AI queriesCalls to /v1/ai/query

Atlas may still apply request rate limits for infrastructure protection, but raw HTTP requests are not the primary commercial unit.

Request rate limits

Atlas enforces request rate limits separately from commercial usage metering.

Every data-plane response includes rate-limit headers:

X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4832
X-RateLimit-Reset: 1718323200

When you hit the request-rate limit, Atlas returns 429 Too Many Requests with a Retry-After header. See Errors for the response format.

PlanDaily request limit
Trial500
Build5,000
CustomAs agreed

Rate limits apply at the organization level. All keys in your organization share the same daily budget.

Health and readiness checks (/v1/health, /v1/ready) are not counted.

Sandbox usage

Sandbox requests (atl_test_ keys) are metered separately and do not count against your live allocation.

Overages

Atlas does not apply automatic overage charges. If your usage approaches your plan limit:

  1. You'll see it in the portal usage dashboard.
  2. We'll reach out to discuss an upgrade or custom arrangement.
  3. Your integration keeps working. We use soft limits, not hard cutoffs, for established accounts.

Checking your usage

The portal shows covered-entity usage, matched-event usage, delivery usage, AI usage, and webhook delivery history with success rates.

You can also query usage programmatically:

curl -s https://api.rangler.co/v1/organizations/{org_id}/usage \
  -H "Authorization: Bearer your_portal_token"

Quickstart covers your first request, Authentication explains the API key model, Environments covers sandbox and live isolation, and Errors documents rate-limit headers and error responses.

On this page