List all value lists on your account via GET /v1/radar/value_lists — supports standard Stripe list params: limit (max 100), starting_after, ending_before, and optional alias filter.
The response is a standard Stripe list object with data array, has_more boolean, and url; use has_more with starting_after set to the last object id to page through all lists.
For each value list of interest, retrieve its items via GET /v1/radar/value_list_items?value_list={rsl_...} — also supports limit, starting_after, and an optional value filter to search for a specific entry.
To check whether a specific value (e.g., an email address) is already on a list, use the value query param: GET /v1/radar/value_list_items?value_list={rsl_...}&value=test@example.com
Delete individual items via DELETE /v1/radar/value_list_items/{rsli_...} when a value should be removed from the list.
Known gotchas
There is no batch-add endpoint for value list items; each item must be POSTed individually — for bulk imports, loop with appropriate rate-limit handling and consider using idempotency keys.
Deleted value list items are permanently removed; there is no archive or soft-delete — if you need to temporarily disable an item, you must delete and re-add it.
The alias filter on GET /v1/radar/value_lists is a prefix match, not an exact match — be specific when filtering to avoid retrieving unintended lists.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp