Who should shortlist Castle?
Developers who want an account-risk API with a small evaluation budget and a clear path to their own response policy.
How the product fits the workflow
Castle distinguishes full Risk or Filter requests from IP intelligence lookups. Its pricing page documents Bot, Abuse and ATO scores alongside device and network fields and policy controls.
What the business receives
Bot, Abuse and ATO risk scores, device and network context, and configured policy results within the selected integration.
Strength and tradeoff
Why it belongs on the shortlist
Public metering makes the difference between an IP lookup and a fuller risk request visible.
What to check first
The shared API budget buys different numbers of each request type. Retention, request limits and querying capabilities vary across plans.
Access, pricing and the unit
5 US dollars of monthly API usage. Pro: 200 US dollars per month / 200 US dollars API usage. Billing unit: Risk call or IP entity.
Use the vendor’s current plan and product scope when estimating cost. Confirm supported platforms, included output, request counting and operational support before starting a pilot.
Editorial fit breakdown
The API workflow and evaluation access make Castle a strong fit for an engineering-led account-risk deployment.
| Category | Weight | Grade |
|---|---|---|
| Account abuse fit | 25 percent | 4.6 / 5 |
| Identity context | 15 percent | 4.6 / 5 |
| Decision output | 15 percent | 4.7 / 5 |
| Implementation | 15 percent | 4.7 / 5 |
| Commercial access | 10 percent | 4.7 / 5 |
| Operational control | 10 percent | 4.2 / 5 |
| Cross-journey coverage | 10 percent | 4.0 / 5 |
Weighted grades produce 9.1 out of 10. Read the complete methodology and 28 lenses for the definition of the scale.
Run a useful first evaluation
Run a representative event sequence and check score explanations, policy behavior and the difference between an incomplete request and a usable low-risk result.
Record the protected action, event reference, proposed response and later outcome. Include ordinary returning customers in the same cohort. Inspect unavailable results and a support-led reversal before moving from observation to enforcement.
Use the controlled rollout guide to assign owners and release gates, and the API integration checklist for event binding and safe retries.
Official sources
- Capabilities, plans and API budget · reviewed October 21, 2026
- Developer documentation · reviewed October 21, 2026
