Skip to main content
Allowed IPs limits inference traffic to the networks you trust, such as your office, VPN, or NAT gateway addresses. Once a list is set, a request made with any of your organization’s API keys from another address is rejected, even if the key itself is valid.
Open Compliance in the Requesty Console and select Set up (or Edit) next to Allowed IPs.
Allowed IPs is in beta. It controls traffic to Requesty. For the addresses Requesty uses to reach your systems, see Static Egress IPs.

Who can use it

Only organization admins can view and change the list. See RBAC for the full role breakdown.

Set up an allowlist

1

Find your public addresses

Collect the public IPv4 addresses your traffic leaves from. For traffic behind a VPN, proxy, or NAT gateway, that is the egress address of that network, not the private address of the machine.
2

Open the Allowed IPs editor

On the Compliance page, select Set up next to Allowed IPs.
3

Add your addresses

Choose Restricted and add each address or range. Each entry is a single IPv4 address, such as 203.0.113.5, or a CIDR range, such as 203.0.113.0/24 for 203.0.113.0 to 203.0.113.255.
4

Save and test

Save the list, then send a test request from an allowed network and one from outside it to confirm the result.
To remove the restriction, choose Unrestricted. This clears the list and accepts requests from any address again.

Address rules

  • IPv4 only. IPv6 addresses are not supported, and requests that arrive over IPv6 are rejected while a list is set.
  • A range must start on its network boundary: 203.0.113.0/24 is valid, 203.0.113.5/24 is not.
  • Duplicate entries are removed and the list is stored in sorted order.

What it covers

The list applies to the whole organization. It cannot yet be set per API key, group, or project.

Rejected requests

A request from an address outside the list fails before it reaches a model provider, so it is not billed. It returns 403 with this message:
See Error Codes for the full list of router errors.

Audit trail

Every change to the list is recorded in the organization’s audit log with the admin who made it and the full list after the change. The Compliance report shows the current list under Allowed IPs.
Last modified on November 16, 2026