AbuseIPDB: 4 reads, 1 write and 1 destructive call, one client

Reputation and abuse reports for an IP address. Free tier is 1,000 checks a day. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What AbuseIPDB can do here

The integration exposes 4 reads, 1 write and 1 destructive call, each with a declared input and output schema rather than a page of documentation you would have to translate. Reputation and abuse reports for an IP address. Free tier is 1,000 checks a day.

How it authenticates

AbuseIPDB authenticates with a apiKey, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey when we broker the call for you.

Called by name, not by capability

AbuseIPDB does not currently map onto a vendor-neutral capability, so you call its operations by name. That is the right shape when you genuinely mean this provider — which, for a service with its own model of the world, is most of the time.

• check — read: Reputation for one IP address. The connection test.
• checkBlock — read: Reputation for every reported address in a CIDR block.
• reports — read: Individual abuse reports filed against one address.
• blacklist — read: Every address above a confidence threshold — the bulk feed for a firewall or blocklist.
• report — write: File an abuse report against an address. 🔴 PUBLIC AND EFFECTIVELY PERMANENT — this contributes to a score every AbuseIPDB user sees, and a mistaken report is not quietly undone. Never wire it to an automatic trigger without a human step.
• clearAddress — destructive: Withdraw every report this account has filed against one address — the undo for report.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.