canonical: https://jentic.com/apis/oopspam.com/oopspam # OOPSpam API 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. ## For AI 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. ## Scope Does not handle CAPTCHA challenges, bot detection on the network layer, or content moderation for image and video - use for text and email spam scoring only. ## Capabilities - 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 - Run language-specific filtering by passing the expected language code with the content ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Spam Detection** — Score content, IP, and email for spam likelihood and report false positives or negatives. - **Reputation** — Look up the reputation of a domain before accepting submissions from it. ## Why Jentic - **Setup:** Wiring the OOPSpam API by hand means sending the API-key request header on every request and shaping the content, IP, and email fields yourself. Through Jentic you install once, import the OOPSpam API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** OOPSpam takes the content to score in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as scoring content for spam or checking a domain reputation. You credit the agent only with the operations you allow, so reporting a classification stays out unless you add it. - **Credential handling:** Your OOPSpam API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'score this message for spam' or 'check a domain reputation', and Jentic returns the matching OOPSpam operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Spamcheck.ai API** — AI-driven spam scoring service with a similar single-call surface. - **Abstract IP Geolocation API** — Adds country, city, and ASN to the sender IP that OOPSpam already scores. - **Abstract API Suite** — Suite that includes email validation and disposable-email detection. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the OOPSpam API? Yes. Because you run Jentic One yourself, your own rules decide which OOPSpam operations and credentials the agent can use. OOPSpam takes the content to score in the request body rather than a resource id in the path, so you scope the agent to only the operations it needs, such as scoring content for spam with POST /spamdetection or checking a domain with POST `/reputation/domain.` Reporting a classification via POST `/spamdetection/report` stays out unless you grant it, and the API key is injected at execution time so the agent never sees it.