Reply to comment:

Ricky Beam
> good use case for this functionality SPAM hunting. Spammer do everything possible to make themselves hard to find. (i.e. they use different handles for anything that's indexed / searchable) The "descr" field is not searchable via any API at RIPE. The full-text search interface is the only way (short of mirroring the entire whois db), but that output is formatted for humans and thus a pain in the ass to process. If 'http://rest.db.ripe.net/search?source=ripe&inverse-attribute=descr&type-filter=route&query-string=...' worked, it wouldn't take HOURS to track a spammer.