Integration
Connect PhishStats to APIs.guru
When something happens in PhishStats, your agent does the next thing in APIs.guru. 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 APIs.guru 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 APIs.guru
Triggers and actions 1 trigger · 7 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
Find APIs by providerReturns all APIs listed for a given provider. GET /{provider}.json (provider input path param)
Action
Find service names by providerReturns all serviceNames registered for a given provider (providers that host multiple APIs under sub-services). GET /{provider}/services.json (provider input path param)
Action
Get API metricsReturns basic aggregate metrics about the APIs.guru directory (numSpecs, numAPIs, numEndpoints, etc). GET /metrics.json
Action
Get API specificationRetrieves one version of a particular API's OpenAPI spec by provider and api version, optionally scoped to a serviceName. GET /specs/{provider}/{api}.json or /specs/{provider}/{service}/{api}.json (provider, api, optional service input params)
Action
List APIsReturns the full catalog of all APIs indexed by APIs.guru, keyed by provider/api. GET /list.json
Action
List providersReturns the full list of API providers known to APIs.guru. GET /providers.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews