canonical: https://jentic.com/apis/spamcheck.ai/spamcheck

# Spamcheck SpamCheckAI: Spam Filter API

This SpamCheckAI API provides a comprehensive and multifaceted spam detection service designed to maintain the integrity of user-generated content across various platforms. The primary functionalities include: - **IP Spam Check:** This feature scrutinizes the originating IP address of a submission for associations with known spam activities. By leveraging our extensive spam source database, we can. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically check if json is spam, create a new spam report. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Check if json is spam
- Create a new spam report
- Retrieve all spam reports
- Delete a spam report
- Monitor SpamCheckAI: Spam Filter API operational status and events

## Use cases

### Identity and Authentication Operations

Use the SpamCheckAI: Spam Filter API to perform identity auth operations programmatically. The API provides 4 endpoints covering core functionality including check if json is spam, create a new spam report, retrieve all spam reports.

Example prompt: Call POST `/spam/check` to check if json is spam

### Automated Spam Management

Automate spam operations by combining multiple SpamCheckAI: Spam Filter API endpoints. Agents can create a new spam report and then retrieve all spam reports in a single workflow.

Example prompt: Call POST /spam_reports to create a new spam report, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SpamCheckAI: Spam Filter API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'check if json is spam', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/spam/check` | Check if json is spam |
| POST | `/spam_reports` | Create a new spam report |
| GET | `/spam_reports` | Retrieve all spam reports |
| DELETE | `/spam_reports` | Delete a spam report |

## Key resources

- **Spam** — Operations for spam
- **Spam_Reports** — Operations for spam_reports

## Why Jentic

- **Setup:** Wiring SpamCheckAI by hand means sending your key in the API-key header on every request and wiring the spam check and spam report endpoints yourself. Through Jentic you install once, import the SpamCheckAI Spam Filter API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** SpamCheckAI targets travel in the request body and query, not a resource path, so limit the agent to the operations it needs, such as checking content or listing spam reports. You choose the operations it may call, so a destructive one like deleting spam reports is not included unless you add it.
- **Credential handling:** Your SpamCheckAI 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 'check if a message is spam' or 'list spam reports', and Jentic returns the matching SpamCheckAI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the SpamCheckAI: Spam Filter API use?

The SpamCheckAI: Spam Filter API uses an API key passed in the `Api-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I check if json is spam with the SpamCheckAI: Spam Filter API?

Yes. Use the POST `/spam/check` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SpamCheckAI: Spam Filter API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I check if json is spam through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check if json is spam'. Jentic returns the matching SpamCheckAI: Spam Filter API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SpamCheckAI: Spam Filter API have?

The SpamCheckAI: Spam Filter API exposes 4 endpoints covering spam, spam_reports operations.

### Can I limit what my agent is allowed to do with the SpamCheckAI: Spam Filter API?

Yes. Because you run Jentic One yourself, you decide which SpamCheckAI operations your agent may call, so you can grant only checking content for spam and listing spam reports while leaving out creating or deleting spam reports. SpamCheckAI targets travel in the request body and query rather than in a resource path, so scoping happens at the operation level: an operation the agent has not been given is simply unavailable to it. This means a destructive call like deleting a spam report is never reachable unless you add it to the agent's allowed set.