AI Honeypots
Full feed trial: quickstart
AI Honeypots research team. For Full feed (Pro) trial keys. Every endpoint, header and parameter below was checked against the live service on 10 November 2026.
What the trial adds
Our decoys pose as self-hosted AI infrastructure: Ollama, vLLM, LiteLLM, OpenAI-compatible APIs, vector databases and MCP servers. Every IP in the feed sent requests to them. The public feed is cut down so it can stay free. Your key removes the cuts.
| Public feed | With your trial key | |
|---|---|---|
History (days) | 1 to 28 days | 1 to 90 days |
| IPs per pull | the top 1,000 by hits | no cap |
Minimum hits per IP (min_hits) | fixed at 5 | 2 to 100 |
CSV (/feeds/iocs.csv) | not available | available |
| Ranked lists in the API (threat actors, scanners, paths, user agents, models, campaign IPs, new actors, 0-Day Radar) | top 5 | the full list |
| 0-Day Radar window | up to 28 days | up to 90 days |
Capture-level feed (/api/v1/feed) | at least 60 minutes old; no path, user agent or model; IPs masked after the newest 20 | live, every field, IPs unmasked |
On 10 November 2026 the public 7-day feed was at its 1,000-IP cap, which cut it off at IPs with 17 or more hits. The same 7 days with your key and min_hits=2 hold about 5,500 IPs. 90 days at min_hits=2 hold about 29,000.
No plan includes prompt text, captured credential values or anything that identifies our decoys. Prompt and credential fields appear as labels only, for example a prompt category and a length bucket.
1. Store your key
- A key is
aihk_followed by 32 letters and digits. The examples here write it asaihk_XXXX. - The reveal link shows your key once. We keep only a hash of it, so we can't show it again. Put it in your secrets manager or an environment variable. The examples use
AIH_KEY:export AIH_KEY='aihk_XXXX' - If you lose the key, or the link expires before you open it, reply to our email and we'll send a new single-use link. Never send us the key itself: we don't need it.
- At https://ai-honeypots.com/keys/manage you can list your keys, create more (up to 3 on a trial) and revoke one. A revoked key stops working within a minute.
2. Send the key with each request
Use any one of these three. They're equivalent.
| Method | Example |
|---|---|
Authorization: Bearer header (recommended) | curl -H "Authorization: Bearer $AIH_KEY" ... |
| HTTP Basic, with the key as the password and any user name | curl -u "feed:$AIH_KEY" ... |
X-AIH-Key header | curl -H "X-AIH-Key: $AIH_KEY" ... |
- Never put the key in a URL. A request with
?key=is refused with HTTP 400, because URLs end up in proxy and server logs. - An unknown or revoked key gets HTTP 401.
- Any other
Authorizationheader, such as your proxy's own token, is ignored. You get the public feed, not an error.
Check that the key is being sent. A keyed response carries X-AIH-Plan: pro_trial. A response without that header is the public feed.
curl -s -o /dev/null -D - -H "Authorization: Bearer $AIH_KEY" https://ai-honeypots.com/feeds/iocs.json | grep -i '^x-aih'
Keyed responses also carry X-AIH-Data-Delay-Hours (0 on the trial), X-RateLimit-Limit (requests per second) and X-AIH-Quota-Remaining (requests left today, UTC).
3. Endpoints and formats
Base URL: https://ai-honeypots.com
| What | Path | Format | Parameters with your key |
|---|---|---|---|
| IOC feed | /feeds/iocs.json | JSON: feed metadata plus an indicators array | days 1 to 90 (default 7), min_hits 2 to 100 (default 5) |
| IP blocklist | /feeds/iocs.txt | Plain text: one IP per line, # comment lines at the top | the same |
| CSV | /feeds/iocs.csv | CSV with a header row (key required) | the same |
| STIX 2.1 bundle | /feeds/stix.json | application/stix+json | the same; the bundle carries the top 200 indicators by hits |
| MISP feed | /feeds/misp | manifest.json, hashes.csv and two events (7-day and 28-day) | none: the same for every plan. Format fix in progress: MISP can't fetch the events yet, so use STIX for now (section 7) |
| Last 24 hours, high confidence | /feeds/latest.json | JSON | none: the same for every plan |
| Capture-level feed | /api/v1/feed | JSON array, newest first | limit 1 to 200 (default 50), days 0 to 28 (0 means no window) |
How the parameters behave:
- Windows longer than 28 days are served in 30-day steps. For example
days=45returns 60 days. The JSONwindow_daysfield and the TXT# Window:line show the window you got. min_hitsrounds down to the nearest of 2, 3, 5, 10, 20, 50 and 100.- Keyed feeds are rebuilt every 15 minutes, so polling more often returns the same data. The public feed is rebuilt hourly, and
latest.jsonevery 15 minutes. - Windows longer than 28 days are built on demand, so the first pull can take a minute or two. If a build takes longer than 4 minutes you get HTTP 503 with
Retry-After: 120. Retry after that many seconds. - Big pulls are big files. With no cap, a 90-day JSON pull at
min_hits=2runs to tens of megabytes. The CSV and TXT versions of the same pull are much smaller.
JSON indicator fields include value (the attacker IP), actor_category, confidence, ttps (MITRE ATT&CK technique IDs), first_seen, last_seen, total_hits, distinct_personas, distinct_paths, prompt_count, user_agents (up to 5), models_requested (up to 10), interesting_paths, prompt_categories, prompt_length_bucket, scanner_label, mcp_probe, mcp_tool_calls and details. The feed's own taxonomy object defines every category and confidence level.
CSV columns: value, actor_category, confidence, total_hits, first_seen, last_seen, distinct_personas, distinct_paths, prompt_count, ttps (separated by ;), scanner_label (the organisation, when the IP is a verified research scanner), mcp_probe and mcp_tool_calls.
The capture-level feed (/api/v1/feed) gives one row per request our decoys received: time, attacker IP, method, path, user agent, the model asked for, the endpoint family, and prompt and credential labels.
Ranked lists with your key return in full: /api/v1/threat-actors, /api/v1/scanners, /api/v1/toppaths, /api/v1/useragents, /api/v1/models, /api/v1/campaigns (top IPs per campaign), /api/v1/new-actors, /api/v1/new-uris and /api/v1/zeroday-radar. They keep their own limit and days parameters where they have them, with days capped at 28. The 0-Day Radar takes days up to 90.
4. Rate limits
- Each key can make 5 requests a second, with bursts of up to 20, and 10,000 requests a day. The daily count resets at 00:00 UTC.
- Over the limit, you get HTTP 429 with a
Retry-Afterheader in seconds. - Polling each feed every 15 to 60 minutes stays far inside these limits.
5. Examples
Quote each URL, because & means something to your shell.
# JSON: 90 days, IPs with 2 or more hits
curl -s -H "Authorization: Bearer $AIH_KEY" "https://ai-honeypots.com/feeds/iocs.json?days=90&min_hits=2" -o iocs-90d.json
# CSV: 90 days, for a spreadsheet or a SIEM lookup
curl -s -H "Authorization: Bearer $AIH_KEY" "https://ai-honeypots.com/feeds/iocs.csv?days=90&min_hits=2" -o iocs-90d.csv
# TXT: a 28-day blocklist, IPs only
curl -s -H "Authorization: Bearer $AIH_KEY" "https://ai-honeypots.com/feeds/iocs.txt?days=28&min_hits=2" \
| grep -v '^#' | awk '{print $1}' > blocklist.txt
# STIX 2.1: 90 days (top 200 indicators)
curl -s -H "Authorization: Bearer $AIH_KEY" "https://ai-honeypots.com/feeds/stix.json?days=90" -o stix-90d.json
# The live capture-level feed: the newest 200 requests
curl -s -H "Authorization: Bearer $AIH_KEY" "https://ai-honeypots.com/api/v1/feed?limit=200" \
| jq '.[] | {timestamp, source_ip, method, path, endpoint_family}'
# The same JSON pull with HTTP Basic instead of a Bearer header
curl -s -u "feed:$AIH_KEY" "https://ai-honeypots.com/feeds/iocs.json?days=90&min_hits=2" -o iocs-90d.json
6. Three things to try first
These use fields that only decoy telemetry like ours can fill. Each runs on the 90-day JSON file from section 5.
- IPs that asked for 10 or more different model names. That is model enumeration: mapping what a server will run. On 10 November 2026, about 840 IPs in the 90-day window did this.
jq -r '.indicators[] | select((.models_requested|length) >= 10) | [.value, .actor_category, .total_hits] | @tsv' iocs-90d.json - IPs that called MCP tools, not just discovered an MCP endpoint (
mcp_tool_callscounts JSON-RPCtools/callrequests). There were 9 such IPs in the 90 days to 10 November 2026.jq -r '.indicators[] | select(.mcp_tool_calls > 0) | [.value, .mcp_tool_calls, .actor_category] | @tsv' iocs-90d.json - Leave out verified research scanners (Censys and Infrawatch) before you block or alert on anything. They stay in the feed with a
scanner_label, so you can choose.jq -r '.indicators[] | select(.scanner_label == null) | .value' iocs-90d.json
The four RELAY-* categories (operator, verifier, customer and cataloger) describe "shadow API" resellers that use exposed AI servers as backends. The feed's taxonomy object explains each one.
7. Set it up in your tools
MISP
- For now, import the STIX bundle: pull
stix-90d.json(section 5) and load it with MISP's STIX 2.x import (Import from... > STIX 2.x; menu names vary by version). - Our MISP-format feed (
/feeds/misp) has a format fix in progress: MISP rejects the event IDs in its manifest. We'll update this page when it's fixed. Then add it under Sync Actions > Feeds > Add Feed (input source Network, source format MISP Feed) with the URLhttps://ai-honeypots.com/feeds/misp, with no trailing slash, because MISP adds/manifest.jsonitself.
For every IP rather than the top 200, use the JSON, CSV or TXT feed with your key.
OpenCTI
Import the keyed STIX bundle (90 days, top 200 indicators) with pycti on a schedule. Don't point OpenCTI's MISP Feed connector at our MISP feed until its format fix is live (see MISP above).
import os
import requests
from pycti import OpenCTIApiClient
bundle = requests.get("https://ai-honeypots.com/feeds/stix.json?days=90",
headers={"Authorization": "Bearer " + os.environ["AIH_KEY"]}, timeout=300).text
api = OpenCTIApiClient("https://your-opencti.example", os.environ["OPENCTI_TOKEN"])
api.stix2.import_bundle_from_json(bundle)
For every IP rather than the top 200, map the JSON or CSV feed in your own connector: value becomes an IPv4 observable, and actor_category and ttps become labels.
This is client configuration. We haven't run it on an OpenCTI instance ourselves.
Splunk Enterprise Security
Add the TXT feed as a line-oriented threat intelligence download. Menu names differ between ES versions. In recent versions the downloads are under Configure > Data Enrichment > Threat Intelligence Management.
- URL:
https://ai-honeypots.com/feeds/iocs.txt?days=28 - Ignoring regular expression:
(^#|^\s*$) - Extracting regular expression:
^(\S+)\s+#\s+(.*)$ - Fields:
ip:$1,description:$2 - Interval: 3600 seconds
With your key: set the download's remote-site user to any name (for example feed), store the key as that user's password in ES credential management, and change the URL to https://ai-honeypots.com/feeds/iocs.txt?days=90&min_hits=2. Then open one downloaded file and check that its # Window: line says 90 days. Our server never asks for credentials, because anonymous pulls are allowed. So if your ES version only sends a password when asked, the line says 28 days and you're getting the public feed. In that case, pull the CSV on a schedule with curl (section 5) and load it as a lookup or a threat intelligence upload.
This is configuration. We haven't run it on a Splunk ES instance ourselves.
8. When the trial ends
- Your trial runs until the date in our email.
- On that date the key moves to the free Community plan and keeps working. You won't get a 401 and you don't need to change your set-up. You get the public view again: 28 days, the top 1,000 IPs, top-5 lists and the delayed capture-level feed.
- Before the end date we'll email you how to keep the Full feed. Plans and prices: https://ai-honeypots.com/?src=quickstart#pricing
9. Terms and help
- Your trial is under our Terms of Service: https://ai-honeypots.com/legal/#terms. The data licence is at https://ai-honeypots.com/legal/#data-licence and the acceptable use policy at https://ai-honeypots.com/legal/#acceptable-use.
- If something doesn't work, reply to our email or write to contact@ai-honeypots.com. Include the URL you called, the HTTP status and the response body, but never the key. We answer in writing within one business day.