Integration
Connect PhishStats to UUID Generator
When something happens in PhishStats, your agent does the next thing in UUID Generator. 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 UUID Generator 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 UUID Generator
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.
- 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
Decode UUIDDecode an existing UUID string to extract its version, variant, and (for time-based versions) the embedded timestamp. GET https://www.uuidtools.com/api/decode/{uuid} (endpoint inferred from the site's Decode UUID tool at /decode; confirm exact path when implementing).
- Generate timestamp-first UUID
Generate one or more timestamp-first (ordered) UUIDs, where the current timestamp is embedded at the start so values sort in creation order when stored/indexed. GET https://www.uuidtools.com/api/generate/timestamp-first (endpoint path per the /generate/timestamp-first docs page).
- Generate v1 UUID
Generate one or more (up to 100) time-based version-1 UUIDs. GET https://www.uuidtools.com/api/generate/v1 or /v1/count/{n}.
- Generate v3 UUID
Generate a deterministic version-3 (MD5-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v3/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
- Generate v4 UUID
Generate one or more (up to 100) random version-4 UUIDs. GET https://www.uuidtools.com/api/generate/v4 or /v4/count/{n}.
- Generate v5 UUID
Generate a deterministic version-5 (SHA-1-based) UUID from a namespace + name. GET https://www.uuidtools.com/api/generate/v5/namespace/{namespace}/name/{name}; namespace is ns:url|ns:dns|ns:OID|ns:X500 or a UUID; name may be base64-encoded with a base64: prefix.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.