Integration
Connect PhishStats to Geocode.xyz
When something happens in PhishStats, your agent does the next thing in Geocode.xyz. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PhishStats and Geocode.xyz to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with PhishStats and Geocode.xyz
Triggers and actions 1 trigger · 6 actions
Trigger
New phishing recordPolling trigger for newly added phishing URLs. GET https://api.phishstats.info/api/phishing?_sort=-date&_p=1&_size=100 (optionally filtered by _where=(countrycode|tld|asn,eq,value) etc.) — the database refreshes every ~90 minutes; poll no more often than that. Dedup/order by the id or date field (descending). Auth via X-API-Key header (psk_...) or ?apikey=psk_...; anonymous allowed at a lower quota.
Action
Find phishing recordsSearch the PhishStats phishing database. GET https://api.phishstats.info/api/phishing with _where=(field,operator,value) filters (eq/ne/gt/lt/like, combined with ~and/~or) over fields like url, ip, asn, countrycode, tld, title, score, date, id; _sort=field (-field for desc); _p=page (default 1), _size=records per page (default 20, max 100). Auth via X-API-Key header (psk_...), Authorization: Bearer psk_..., or ?apikey=psk_... query param; anonymous is allowed at a lower quota.
Action
Autocomplete addressGet street name, city, and postal code suggestions for a partial street name, city name, or postal code within a given region. GET https://geocode.xyz/?region={region}&streetname={partial}&cityname={partial}&geoit=json
Action
Geocode addressConvert a street address, postal code, landmark, or city name into latitude/longitude coordinates (forward geocoding). GET https://geocode.xyz/?locate={address}&json=1
Action
Geolocate IP addressLook up the approximate physical location of an IP address. GET https://geocode.xyz/?locate={ip_address}&json=1
Action
Geoparse textScan a block of free text and extract every place name mentioned, geocoded to coordinates and ordered by match confidence. POST https://geocode.xyz/ with scantext={text}&json=1
Action
Reverse geocode coordinatesConvert a latitude,longitude point into the nearest street address description (reverse geocoding). GET https://geocode.xyz/?locate={lat},{lng}&json=1
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.