Create a value list via POST /v1/radar/value_lists with params: alias (unique string), name (display name), and item_type (one of: card_fingerprint, ip_address, email, card_bin, customer_id, string; card_fingerprint is the default if omitted). Authenticate with your secret key.
Note the id field (rsl_...) in the response — you will need it for adding items and referencing in rules.
Add items to the list via POST /v1/radar/value_list_items with body fields value_list (the rsl_... id) and value (the actual string to block, e.g. a card fingerprint or IP address).
Verify item creation by listing items: GET /v1/radar/value_list_items?value_list=rsl_... and confirm your values appear.
Reference the list in a Radar rule in the Dashboard or via POST /v1/radar/rules using syntax like: block if ::card_fingerprint:: in @your-list-alias.
Known gotchas
The field is item_type, not list_type — using the wrong field name silently omits it and the list defaults to string type, which will not match card fingerprints in rules.
Each item must match the declared item_type exactly; for example, you cannot add an IP address string to a card_fingerprint list — the API will return a validation error.
Value list aliases must be unique per account and cannot be changed after creation; plan your naming convention before creating lists.
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?