OOPSpam API

Name: OOPSpam API API
Brand: OOPSpam API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityThreat DetectionapiKey3 EndpointsREST

For Agents

Score a piece of submitted content for spam likelihood, check whether a domain is reputable, and report false positives or negatives back to the OOPSpam classifier.

Connect the OOPSpam API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OOPSpam 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 OOPSpam API API.

Score a content submission for spam likelihood with a numeric 0-6 score and per-check breakdown

Combine content, sender IP, and sender email into a single spam-detection request

Check whether a domain has a known bad reputation before accepting a submission

Report a false-positive or false-negative classification back to OOPSpam to improve future scoring

GET STARTED

Start building with OOPSpam API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for OOPSpam API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for OOPSpam API, keeping it validated and agent-ready. OOPSpam is a privacy-focused spam and abuse detection service that scores submitted content, IPs, and email addresses against multiple checks and returns a numeric spam score plus per-check detail. The surface is intentionally small — three endpoints — so it slots neatly into form submissions, contact pages, and comment workflows where a moderation decision needs to happen in milliseconds.

Use Cases

Patterns agents use OOPSpam API API for, with concrete tasks.

★ Contact-Form Spam Filtering

Wrap a contact form with an OOPSpam check so messages that score above a threshold are quarantined or rejected before they reach the inbox. POST /spamdetection accepts the message body, sender IP, and sender email together and returns a single score the application can branch on.

Send a POST /spamdetection request with the form body, sender IP, and email and return a decision to publish or quarantine when the score is above 3.

Comment Moderation Pipeline

Score every new comment against OOPSpam before it appears on a blog or community page, then push borderline scores into a human moderation queue. The single-endpoint design lets a moderation agent process comments in batches and feed clear classifications back via POST /spamdetection/report so the model improves over time.

For each pending comment, call POST /spamdetection and route to publish, queue, or reject based on the returned score; report any incorrect decisions back via POST /spamdetection/report.

Domain Reputation Pre-Check

Before accepting a sender's email or letting a user register, look up the sender's domain against OOPSpam's reputation dataset and reject if it is flagged. POST /reputation/domain returns a structured reputation record so an agent can short-circuit obvious abuse without running the full content check.

Call POST /reputation/domain with 'example.tk' and reject the registration if the response indicates a bad reputation.

AI Agent Submission Triage

Let a Jentic-orchestrated agent screen user submissions for spam without holding the OOPSpam API key. The agent calls a single Jentic operation, OOPSpam returns a score, and the agent makes the publish-or-reject decision in one round trip.

Search Jentic for 'check whether a submission is spam', load the OOPSpam spamdetection schema, and execute it for the latest contact-form payload, returning the score and decision.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for oopspam api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/spamdetection

Score content, IP, and email for spam

POST

/spamdetection/report

Report a false-positive or false-negative classification

POST

/reputation/domain

Check the reputation of a domain

POST

/spamdetection

Score content, IP, and email for spam

POST

/spamdetection/report

Report a false-positive or false-negative classification

POST

/reputation/domain

Check the reputation of a domain

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The OOPSpam X-Api-Key is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token; the X-Api-Key header is injected at execution time so the raw key never enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'check whether a submission is spam' or 'check a domain reputation' and receive the matching OOPSpam operation with its input schema.

Time to first call

Direct OOPSpam integration: half a day to wire the X-Api-Key header, request shape, and threshold logic. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Spamcheck.ai API

AI-driven spam scoring service with a similar single-call surface.

Pick Spamcheck.ai when the agent wants an LLM-based classifier rather than OOPSpam's rule-and-reputation approach.

Complementary

Abstract IP Geolocation API

Adds country, city, and ASN to the sender IP that OOPSpam already scores.

Pair with OOPSpam when the moderation rule needs geolocation context (e.g., reject submissions from anonymising ASNs) on top of the spam score.

Complementary

Abstract API Suite

Suite that includes email validation and disposable-email detection.

Use Abstract's email validation upstream of OOPSpam to reject obviously fake emails before paying for a full spam-detection call.

FAQs

Specific to using OOPSpam API API through Jentic.

Why is there no official OpenAPI spec for OOPSpam API?

OOPSpam publishes its docs as HTML at oopspam.com/docs but does not ship a machine-readable OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call OOPSpam via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the OOPSpam API use?

OOPSpam authenticates with an API key in the X-Api-Key request header. Through Jentic the key is held in the vault and the X-Api-Key header is injected at execution time so the agent never sees the raw key.

Can I check both content and sender IP in one OOPSpam call?

Yes. POST /spamdetection accepts the message body, sender IP, and sender email together and returns a single score plus per-check detail, so a form handler does not need to make multiple round trips.

What are the rate limits for the OOPSpam API?

Rate limits depend on the OOPSpam plan and are not declared in the spec. Plan to handle 429 responses by backing off and retrying, and check oopspam.com for current per-tier limits before launching a high-volume run.

How do I score a comment for spam through Jentic?

Run pip install jentic and search for 'check whether a submission is spam'. Jentic returns the POST /spamdetection operation; load the schema and execute it with the content and sender details to receive the spam score in one call.

Can I tell OOPSpam when it gets a decision wrong?

Yes. POST /spamdetection/report accepts a previous classification and a corrected label so OOPSpam can learn from misclassifications. Wire this into a moderation queue so human overrides feed back into the model.