agentleFS
Liberty91LTDLiberty91LTD/cti-skills/skills/otx-api/SKILL.md

otx-api

Skill35 starsChanged 44 days agoMITView on GitHub

AlienVault OTX API reference. Community threat intelligence pulses and indicator lookups.

  • Reads credentials

The file

Files
SKILL.md

AlienVault OTX API

Base URL

https://otx.alienvault.com/api/v1

Authentication

Header: X-OTX-API-KEY: $OTX_API_KEY

Rate Limits

  • 10,000 requests/hour

Key Endpoints

IPv4 Indicator

# General info
curl -s "https://otx.alienvault.com/api/v1/indicators/IPv4/{ip}/general" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

# Reputation
curl -s "https://otx.alienvault.com/api/v1/indicators/IPv4/{ip}/reputation" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

# Passive DNS
curl -s "https://otx.alienvault.com/api/v1/indicators/IPv4/{ip}/passive_dns" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

# Associated malware
curl -s "https://otx.alienvault.com/api/v1/indicators/IPv4/{ip}/malware" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

Domain Indicator

curl -s "https://otx.alienvault.com/api/v1/indicators/domain/{domain}/general" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

Sections: /general, /geo, /malware, /url_list, /passive_dns, /whois

File Hash Indicator

curl -s "https://otx.alienvault.com/api/v1/indicators/file/{hash}/general" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

Sections: /general, /analysis

URL Indicator

curl -s "https://otx.alienvault.com/api/v1/indicators/url/{url}/general" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

Search Pulses

curl -s "https://otx.alienvault.com/api/v1/search/pulses?q={query}" \
  -H "X-OTX-API-KEY: $OTX_API_KEY"

Key Response Fields

  • pulse_info.count — number of pulses referencing this indicator
  • pulse_info.pulses[] — pulse details (name, description, tags, TLP, created)
  • reputation — community reputation score
  • validation[] — validation results from OTX
  • passive_dns[] — historical DNS resolutions

CTI Value

OTX provides community-sourced intelligence. High pulse count = widely reported indicator. Useful for:

  • Corroboration with other sources
  • Discovering related indicators via pulse associations
  • Historical passive DNS data
  • Community context (pulse descriptions explain what the indicator relates to)

Response Summary Format

indicator: <value>
type: <ip|domain|hash|url>
pulse_count: <number>
reputation: <score>
key_pulses:
  - name: <pulse name>
    tags: [<tags>]
    created: <date>
related_indicators: [<list>]
passive_dns: [<domain/IP resolutions>]
verdict: known-malicious|suspicious|clean|unknown

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.