Agent-ready OpenAPI document · curated by JenticSecurityThreat DetectionapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Score IP addresses for abusive behaviour, pull abuse reports, download blacklists, and submit abuse reports across 7 AbuseIPDB v2 endpoints authenticated by a Key header.
Use for: I want to check whether an IP has abuse reports, Get the abuse confidence score for a suspicious IP, Download the AbuseIPDB blacklist for our firewall, Submit an abuse report for an IP that brute-forced our SSH
Not supported: Does not handle malware sample analysis, URL reputation, or DNS data - use for IP abuse scoring, reporting, and blacklist retrieval only.
Jentic publishes the only available OpenAPI specification for AbuseIPDB API, keeping it validated and agent-ready. AbuseIPDB is a community-driven database of IP addresses reported for malicious activity such as brute-force attacks, scanners, and spam. The v2 API exposes seven endpoints covering single-IP and CIDR-block lookups, full report histories, blacklist downloads, single and bulk abuse reports, and self-clearing of submitted reports. Authentication is a Key header tied to a free or paid AbuseIPDB account, and responses include a 0-100 abuse confidence score that fits naturally into firewall, SIEM, and triage workflows.
Install Jentic One Beta
Connect the AbuseIPDB API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AbuseIPDB API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fabuseipdb.com%2Fabuseipdb-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fabuseipdb.com%2Fabuseipdb-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AbuseIPDB API.
Score a single IP for abusive behaviour with a 0-100 confidence value via /check
Pull a paginated history of abuse reports for an IP via /reports
Download the blacklist of the most-reported IPs as JSON or plaintext via /blacklist
Submit an abuse report against an IP with a category and comment via /report
Submit bulk abuse reports as a CSV upload via /bulk-report
Check an entire CIDR block for abuse reports via /check-block
Clear your own submitted reports for an IP via /clear-address
Use Cases
Patterns agents use AbuseIPDB API for, with concrete tasks.
★ Firewall blocklist refresh
A scheduled job calls GET /blacklist with a confidenceMinimum threshold to download the top reported IPs and pushes them into a perimeter firewall blocklist. Combine with a daily diff so old, decayed reports drop off and only currently active offenders are blocked.
GET /blacklist with confidenceMinimum=90&limit=10000, parse the JSON, and push each ipAddress into the firewall deny list
SSH brute-force reporting
A fail2ban-style job parses sshd auth logs, detects repeat offenders, and calls POST /report with categories=18,22 and a comment summarising the attempt. This contributes to the AbuseIPDB community feed and gets the IP scored for everyone else.
POST /report with ip=<offender>, categories='18,22', comment='SSH brute force on host X' for each detected offender
Pre-login risk score
Before allowing a login from an unfamiliar IP, an authentication service calls GET /check with verbose=true and uses the abuseConfidenceScore alongside other signals to decide whether to challenge or block. Returns within a few hundred milliseconds and caches well.
GET /check with ipAddress=<login-ip>&verbose=true; if abuseConfidenceScore >= 75 then require MFA challenge
AI agent IOC enrichment via Jentic
A SOC agent enriching IOCs from an EDR queue calls AbuseIPDB through Jentic to attach abuse score and report counts to each suspicious IP. The Key header is held by Jentic, so the agent never sees the raw credential.
For each IP from the EDR feed, GET /check with ipAddress=<ip>&maxAgeInDays=90 and append abuseConfidenceScore and totalReports to the IOC record
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for abuseipdb api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/check
Get the abuse confidence score and report summary for an IP
GET
/reports
Paginated abuse-report history for an IP
GET
/blacklist
Download the most-reported IPs above a confidence threshold
POST
/report
Submit an abuse report against an IP
POST
/bulk-report
Submit bulk abuse reports via CSV
GET
/check-block
Check a CIDR block for abuse reports
DELETE
/clear-address
Clear your own reports for an IP
GET
/check
Get the abuse confidence score and report summary for an IP
GET
/reports
Paginated abuse-report history for an IP
GET
/blacklist
Download the most-reported IPs above a confidence threshold
POST
/report
Submit an abuse report against an IP
POST
/bulk-report
Submit bulk abuse reports via CSV
GET
/check-block
Check a CIDR block for abuse reports
DELETE
/clear-address
Clear your own reports for an IP
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AbuseIPDB API
- AI-Aware (B+)68/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
58%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AbuseIPDB API by hand means attaching the Key header on every call and juggling read, report, and blacklist endpoints yourself. Through Jentic you install once, import the AbuseIPDB API from the API Directory, store the Key once, and your agent calls it.
Permission scoping
These endpoints take the target IP in the query or request body rather than a resource id in the URL, so limit the agent to the operations it needs, such as checking an IP's abuse score and reading the blacklist. You choose the operations it may call, so reporting an IP or clearing an address is not included unless you add it.
Credential isolation
Your AbuseIPDB Key is stored once, encrypted, by your own Jentic One instance and injected as the Key header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check ip abuse score' or 'download ip blacklist', and Jentic returns the matching AbuseIPDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AbuseIPDB API through Jentic.
Why is there no official OpenAPI spec for AbuseIPDB API?
AbuseIPDB documents the API in HTML at docs.abuseipdb.com but does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AbuseIPDB API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the AbuseIPDB API use?
A Key header on every request, tied to a free or paid AbuseIPDB account. The Accept: application/json header is also required for JSON responses. Through Jentic the Key is stored encrypted in the vault and injected at execution time.
Can I report an abusive IP with this API?
Yes. POST /report accepts the IP, a comma-separated list of category IDs (e.g. 18,22 for SSH brute force), and an optional comment. Use POST /bulk-report with a CSV payload to submit many reports at once.
What are the rate limits for the AbuseIPDB API?
Free accounts get 1,000 checks and 100 reports per day; paid plans (Basic Subscriber, Premium) raise these to tens of thousands per day. Limits are not encoded in the spec - the response includes X-RateLimit headers showing remaining quota.
How do I score an IP through Jentic?
Search Jentic for 'check ip abuse score', load GET /check on api.abuseipdb.com/api/v2, then execute with ipAddress and maxAgeInDays. Install with pip install jentic and use await client.search, load, execute.
Is the AbuseIPDB API free?
Yes, with a 1,000 check/day free tier. Paid plans (Basic Subscriber, Premium) raise daily quotas, add the bulk-report endpoint at higher volume, and unlock larger blacklist downloads.
Can I limit what my agent is allowed to do with the AbuseIPDB API?
Yes. Because you run Jentic One yourself, your own rules decide which of the seven AbuseIPDB operations your agent may call and which credentials it may use. You can allow only the read operations it needs, such as scoring an IP through GET /check, checking a CIDR block through GET /check-block, and reading the blacklist through GET /blacklist, while leaving out write operations. That means submitting a report through POST /report or /bulk-report and removing your own reports through DELETE /clear-address stay off limits unless you explicitly add them.
GET STARTED