Integration
Connect PhishStats to Xitoring
When something happens in PhishStats, your agent does the next thing in Xitoring. 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 Xitoring 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 Xitoring
Triggers and actions 1 trigger · 17 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.
- Find phishing records
Search 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
Add checkCreate a new uptime/website/server check. POST /api/v2/check
- Add group
Store a new check/server group. POST /api/v2/groups
- Add heartbeat
Create a new heartbeat check. POST /api/v2/heartbeat/add
- Add maintenance schedule
Create a new maintenance window. POST /api/v2/maintenance-schedules/add
- Add ticket
Create a new support ticket. POST /api/v2/tickets
- Delete check
Delete a check. DELETE /api/v2/checks/{id}
- Delete server
Remove a server from monitoring. DELETE /api/v2/servers/{id}
- Get check
Retrieve a single check by id. GET /api/v2/check/{id}
- Get incident
Get a single incident's data. GET /api/v2/incidents/{id}
- Get server
Retrieve a single server by id. GET /api/v2/servers/{id}
- List checks
List all checks. GET /api/v2/check/
- List groups
List all groups. GET /api/v2/groups
- List maintenance schedules
List maintenance schedules. GET /api/v2/maintenance-schedules
- List servers
List all monitored servers. GET /api/v2/servers
- Resolve incident
Resolve an open incident. POST /api/v2/incidents/{id}/resolve
- Update check
Update an existing check. PUT /api/v2/check/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.