UponAI provides fraud protection features to help you prevent abuse of your voice AI agents. These features complement the general abuse prevention measures and give you fine-grained control over how your agents are accessed.Documentation Index
Fetch the complete documentation index at: https://documentation.uponai.com/llms.txt
Use this file to discover all available pages before exploring further.
Rate Limiting
When using public keys to authenticate calls from your frontend, you can enable fraud protection to automatically rate limit requests based on IP address and destination phone number.Enabling Fraud Protection
How It Works
When fraud protection is enabled on a public key:- Requests are rate limited based on the combination of the caller’s IP address and the destination phone number
- This prevents bad actors from using the same IP to spam calls to premium rate numbers
- Rate limiting applies to outbound phone calls and SMS initiated via public key authentication
Geographic Restrictions
Restrict which countries are allowed to make inbound calls to your UponAI phone numbers, and which countries your numbers can call outbound. This helps prevent International Revenue Sharing Fraud (IRSF) and limits exposure to unwanted traffic.Allowed Inbound Countries
When configured, calls from countries not on the list are automatically rejected.
Allowed Outbound Countries
When configured, outbound calls to countries not on the list are blocked.
Configure via API
US, CA, GB).
Sanctioned Countries
The following countries are always blocked regardless of your configuration:| Country | Code |
|---|---|
| Cuba | CU |
| Iran | IR |
| North Korea | KP |
| Syria | SY |
| Russia | RU |
| Belarus | BY |
| Venezuela | VE |
Best Practices
- Enable fraud protection on all public keys — adds an extra layer of protection at minimal cost
- Combine with reCAPTCHA — use both fraud protection and reCAPTCHA for web-initiated calls to prevent bot abuse
- Start with restrictive country lists — begin with only the countries you need and expand as necessary
- Monitor for blocked calls — use webhooks to track when calls are blocked due to geographic restrictions
- Review regularly — periodically review your country restrictions to ensure they match your current business needs